What OBS Studio 33 Changed Before Your Next Playtest Capture - 2026
If you searched obs studio 33 after October 23, 2026, you do not need another paste of the GitHub changelog into Discord. You need a Monday upgrade order for the machine that records playtests.
OBS Project shipped OBS Studio 33.0.0 that day. The release overhauls plugin loading (first-party plugins move into a core folder; third-party paths change; legacy locations keep loading through OBS 34), bumps CEF for browser sources, improves Game Capture detection, changes Safe Mode so it does not start the WebSocket server, and removes Ubuntu 24.04 support. The companion Legacy Plugin Locations article is explicit: right now you do not have to move plugins, but authors should update installers before the 34 cutover (OBS frames that roughly around August 2027).
This URL owns the playtest-rig read: which machine can take 33 tonight, which Ubuntu box must stay on 32, what to smoke before the next Discord playtest, and what not to confuse with Replay Buffer or Whisper pipeline posts.
It is not the Replay Buffer → ffmpeg concat beginner pipeline. It is not the OneDrive KFM empty-inbox case study. It is not the OBS Studio guide hub. Those own merge nights, path recovery, and chapter checklists. This page owns what 33 changed before you touch the capture PC.
Why this matters now
Hacker News item 50218430 and the GitHub release reaction count pushed 33 into every “should we update tonight?” thread. Facilitators face three bad defaults:
- Update the only playtest laptop mid-session.
- Assume every third-party plugin dies on 33.
- Assume Ubuntu 24.04 still gets packages because “LTS.”
Direct answer: Treat 33 as a planned capture-tool bump with a clear plugin-legacy runway and a hard Linux packaging cut. Clone the scene collection, inventory plugins, decide UPDATE_33 / STAY_32 / LAB_CLONE per machine, then smoke Game Capture + Replay Buffer + any WebSocket companion before inviting players.
Who this explainer is for
| Audience | Use it to… |
|---|---|
| Beginners | Know plugin Legacy ≠ broken, and Ubuntu 24.04 ≠ 33 |
| Developers | Order the upgrade, smoke list, and Safe Mode WebSocket trap |
| Creators | Paste a one-screen “what 33 changed for our rig” note |
| Companies | Diligence — version pin on the capture fleet |
Time: 25 minutes to read; 45–90 minutes to lab on a clone.
Honest limit: The 33.0.0 release notes and legacy plugin KB are authorities. This page maps them to playtest ops. It is not a plugin-author porting guide beyond the KB pointer.
Non-repetition
| URL | Job |
|---|---|
| OBS 33.0.0 release | Primary changelog |
| Legacy Plugin Locations | Legacy → new path policy |
| Replay Buffer concat evening | Merge pipeline |
| OneDrive KFM case study | Empty inbox recovery |
| Local Whisper triage | ASR after capture |
| OBS Studio guide | Hub / preflights |
| Help hub | Symptom-specific fixes |
| This URL | What changed in OBS Studio 33 for playtest capture |
Pair community paste with 25 free game development Discord servers.
The one-paragraph version
OBS Studio 33.0.0 (October 23, 2026) is a real version bump for capture fleets: plugin loading is restructured, browser CEF jumps years ahead, Game Capture detection improves, Safe Mode no longer brings up the WebSocket server, and Ubuntu 24.04 is dropped. Third-party plugins in legacy folders still load through OBS 34; do not panic-reinstall everything tonight. Do inventory the rig, keep 24.04 machines on 32 (or move distros), lab 33 on a disposable profile, and smoke the sources you actually use in playtests before the next Discord night.
What actually changed (playtest-relevant map)
1. Plugin loading overhaul
From the release and KB:
| Fact | Playtest meaning |
|---|---|
| First-party plugins live under a new core folder | Official modules move; do not hand-edit core |
| Third-party install location / folder structure updated | New installs should follow author + KB guidance |
| Legacy third-party paths still load until OBS 34 | Your current plugins should still appear on 33 |
| Plugin manager shows a Legacy indicator | Signal to authors — not an instant red X for facilitators |
| New location wins if both exist | Updating an installer avoids double-load surprises |
Monday rule: On 33, open the plugin manager, screenshot Legacy vs current, and file author update links. Do not delete legacy folders “to clean up” before you prove the new install path.
2. CEF browser framework bump
CEF moves from the July 2024-era line to a September 2026-era line (release cites 127/6533 → 150/7871). Browser sources and docks are the blast radius. Backend work should be invisible — the project asks users to report weirdness.
Monday rule: If your playtest overlay uses Browser Source (donation tickers, custom HUD, Form viewers), smoke those scenes on a lab profile before the live night.
3. Capture and preview quality-of-life
Relevant release bullets for facilitators:
- Improved fullscreen game detection for Game Capture
- Preview source snapping improvements
- Spinbox typing fixes (settings less cursed)
- Window Capture method naming adjustments on Windows
- NVENC enabled on Arm64
- Newer NVIDIA Broadcast SDK hooks for audio/video effects
- Audio monitoring hotkeys per source
- Studio Mode group glitch fixes
Monday rule: Re-test Game Capture on your actual title (borderless vs exclusive fullscreen). Do not assume last month’s source still hooks after a GPU driver + OBS double bump.
4. Safe Mode no longer starts WebSocket Server
Companion tools that expect obs-websocket during a “safe” boot will fail closed.
Monday rule: If your Discord bot, Streamer.bot-style bridge, or custom overlay talks to OBS over WebSocket, document: Safe Mode ≠ remote control. Normal profile smoke must include the websocket path you rely on.
5. Ubuntu 24.04 support removed
This is the sharpest fleet cut in 33 for Linux facilitators.
| Machine | Default this week |
|---|---|
| Ubuntu 24.04 capture PC | STAY_32 (or migrate distro first) |
| Ubuntu newer / supported per OBS packages | Candidate for UPDATE_33 after lab |
| Windows / macOS playtest laptops | UPDATE_33 after plugin + browser smoke |
Do not invent package support OBS removed. Check current download / package notes when you pin.
6. Encoder missing check on profile load
33 adds a check when encoders referenced by a profile are missing. That surfaces “why is recording grey” earlier — good for loaner laptops that lost NVENC drivers.
Monday rule: After upgrade, load the playtest profile once and read any encoder warning before inviting ten players.
Decision table — UPDATE_33 / STAY_32 / LAB_CLONE
| Situation | Decision | Why |
|---|---|---|
| Windows rig, plugins all first-party + two well-maintained thirds | LAB_CLONE then UPDATE_33 | Legacy path covers thirds; still smoke |
| Only playtest PC, fest night tomorrow | STAY current until after session | Never dual-wield upgrade + live night |
| Ubuntu 24.04 | STAY_32 | Support removed in 33 |
| Heavy Browser Source overlays | LAB_CLONE mandatory | CEF blast radius |
| WebSocket-driven scene switching | LAB_CLONE + document Safe Mode trap | Remote control assumptions |
| Arm64 Windows with NVENC hopes | LAB_CLONE | NVENC-on-Arm64 is new — prove encode |
Beginner path — first hour on a lab profile
Prerequisites: admin rights, export of scene collection, list of third-party plugins, 20 minutes without players in voice.
- Export scene collection + profile from current OBS.
- Read the 33.0.0 notes and legacy plugin KB — ten minutes.
- Install 33 on a spare user profile or VM, not by nuking the live install first if you only have one machine — or accept rollback time.
- Import scenes; open plugin manager; note Legacy flags.
- Smoke list (below) — write PASS/FAIL in a sheet.
- Only then schedule the live machine bump.
Common beginner mistakes: deleting “legacy” plugin folders; updating mid-playtest; assuming Safe Mode is for “testing websocket safely.”
Developer smoke list (O1–O10)
| ID | Check | Pass if… |
|---|---|---|
| O1 | Version string | Help → About shows 33.0.x |
| O2 | Scene import | Playtest collection loads without missing-source cascade |
| O3 | Plugin manager | Critical thirds present (Legacy OK on 33) |
| O4 | Game Capture | Target build hooks; 30 s recording proves frames |
| O5 | Mic + desktop audio | Levels move; monitoring hotkey behaves if you use it |
| O6 | Replay Buffer | 10 s save lands in the configured folder (see KFM post if empty) |
| O7 | Browser Source | Overlay URL renders; no blank CEF panel |
| O8 | WebSocket path | Companion connects on normal launch |
| O9 | Safe Mode expectation | Documented that websocket does not start |
| O10 | Encoder warning | Profile load shows no surprise missing encoder — or you fixed drivers |
File the sheet next to your facilitator README. If you already use receipts for replay paths, keep that culture — version bumps deserve the same PASS row.
Linux fleet note (companies and labs)
| Risk | Mitigation |
|---|---|
| Silent “apt upgrade” onto unsupported combo | Pin OBS package; announce 24.04 stay |
| Mixed fleet (some 24.04, some newer) | Label machines UPDATE_33 vs STAY_32 in inventory |
| CI recording agents | Rebuild image deliberately; do not surprise merge week |
Diligence language: “Capture fleet pin is OBS 32.x on Ubuntu 24.04 hosts; Windows facilitators labbed 33.0.0 on DATE with smoke O1–O10 PASS.”
What not to confuse with 33
| Topic | Wrong merge | Right URL |
|---|---|---|
| Empty replay inbox after OneDrive KFM | “33 broke saving” | KFM case study |
| ffmpeg concat / Whisper batch | “33 changed Whisper” | Concat evening · Whisper triage |
| Plugin author porting | Facilitator deletes legacy folders | Legacy KB |
| Steam AI filter discourse | Unrelated store politics | Steam AI filter week list |
Plugin inventory worksheet (fill before UPDATE_33)
Copy into the facilitator README. One row per third-party plugin.
| Plugin | Author update URL | Installed path (legacy / new) | Legacy flag on 33? | Critical for playtest? Y/N | Action |
|---|---|---|---|---|---|
| KEEP_LEGACY / UPDATE_INSTALLER / DROP |
Rules:
- If Critical = Y and the author has no 33-aware installer yet, KEEP_LEGACY is fine on 33 — that is what the runway is for.
- If Critical = Y and the plugin fails to load on the lab profile, STAY on the previous OBS build for the live machine until you have a replacement source.
- Never mark DROP because Discord said “legacy means dead.” Legacy means flagged, not unloaded, through the stated window.
Rollback plan (one machine, one hour budget)
Assume Windows for the most common facilitator laptop:
- Before upgrade: Export scene collection + profile; zip
%AppData%\obs-studio(or your portable folder); note exact previous version string. - Install 33 via the official installer you trust; do not mix random portable forks on the live box.
- If O2–O4 fail hard: uninstall 33, reinstall the previous version from your archived installer, restore the zip, prove Game Capture + Replay Buffer again.
- Do not “fix forward” into a playtest voice channel with half-missing filters.
macOS facilitators: keep the previous .dmg / app backup on an external volume the same day. Linux facilitators on supported distros: know which package version you can downgrade to before you upgrade.
Windows / macOS / Linux differences that bite playtests
| OS | 33-specific watchout | Facilitator action |
|---|---|---|
| Windows | Window Capture method names adjusted; Game Capture fullscreen detection improved | Re-select capture methods after upgrade; do not assume old properties labels |
| Windows Arm64 | NVENC enabled in 33 | Lab bitrate + stability; loaner Arm laptops are not automatically VOD-ready |
| macOS | Screen Capture transparency handling improved | Smoke any HUD-over-game scenes you rely on |
| Linux (non-24.04) | Follow current OBS package channels | Still lab; do not skip O1–O10 |
| Ubuntu 24.04 | Support removed | STAY_32 or migrate OS — no “maybe the PPA still works” heroics on live night |
Encoder and NVIDIA Broadcast notes
33 adds a missing encoder check when a profile loads and hooks newer NVIDIA Broadcast SDKs for audio/video effects. Playtest meaning:
- Loaner laptops that lost GPU drivers will fail earlier and louder — good.
- If you depended on older Broadcast effect plugins, smoke noise removal / virtual background on the lab profile before you promise “same mic chain as last week.”
- Simple Output recording audio bitrate now scales by channel count — if you record multi-channel loops for triage, spot-check file sizes and loudness once so Whisper batch nights are not surprised.
None of that replaces the Whisper triage article. It only says: prove the capture side still feeds the inbox.
Studio Mode and groups
33 fixes Studio Mode group glitches where moving sources inside a group could glitch or leak into Program. If your playtest layout uses groups heavily (facecam docked under a game group, alert stack grouped), run one Studio Mode rehearsal: move a grouped source, confirm Program stays clean. That five-minute check prevents “why is the WIP transform on stream” moments when someone thought they were only tweaking Preview.
Creator paste — Discord one-screen
OBS 33.0.0 shipped Oct 23. Plugin folders moved, but legacy third-party paths still load through OBS 34. Ubuntu 24.04 support is removed — those boxes stay on 32. Safe Mode no longer starts the WebSocket server. We are labbing 33 on a clone with Game Capture + Replay Buffer + browser overlay smoke before we touch the live playtest PC.
Monday schedule (print)
| Block | Owner | Outcome |
|---|---|---|
| 0:00–0:15 | Facilitator | Read release + legacy KB |
| 0:15–0:30 | Facilitator | Inventory plugins + Ubuntu versions |
| 0:30–1:15 | Facilitator | LAB_CLONE install + O1–O10 |
| 1:15–1:25 | Lead | UPDATE_33 / STAY_32 decision per machine |
| Next playtest −1 day | Facilitator | Live bump only if lab PASS |
| After first live night | Facilitator | Note CEF/browser weirdness upstream if any |
Failure modes
| Failure | Symptom | Fix |
|---|---|---|
| Live-night upgrade | Mid-session missing sources | Roll back; reschedule bump |
| Legacy deletion | Plugins vanish | Restore folders; re-read KB |
| 24.04 force-install | Broken packages / unsupported | Return to 32; plan distro move |
| Safe Mode websocket myth | Bots dead during “safe” test | Use normal profile for remote tests |
| Blame 33 for KFM paths | Empty inbox | Check Output path — KFM article |
| Double install path | Two copies of a plugin fighting | Prefer new path; remove only after lab PASS |
| Profile encoder scare | Grey record button after bump | Fix drivers / re-pick encoder; re-load profile |
| Browser blank panel | Overlay URL dead after CEF bump | Isolate Browser Source; report upstream if new |
Opinion spine (quotable)
Stop updating the only playtest capture PC during a live Discord session.
Stop deleting legacy plugin folders on OBS 33 because the manager said Legacy.
Stop forcing OBS 33 onto Ubuntu 24.04 after support was removed.
Do lab on a clone, run O1–O10, and keep a rollback zip before the fleet bump.
Key takeaways
- OBS Studio 33.0.0 shipped October 23, 2026 — real capture-fleet event.
- Plugin loading was overhauled; legacy third-party paths still work through OBS 34.
- Read Legacy Plugin Locations before moving folders.
- Ubuntu 24.04 support is removed — default STAY_32 on those hosts.
- CEF browser bump means smoke Browser Sources on a lab profile.
- Safe Mode does not start the WebSocket server in 33.
- Game Capture detection improved — re-hook your actual build.
- Never upgrade the only playtest PC during a live Discord session.
- Run smoke O1–O10 and keep a dated PASS sheet.
- Do not merge 33 into Replay Buffer path or Whisper pipeline incidents without evidence.
- Plugin authors — not facilitators — own the long-term folder migration.
- This URL is the what-changed upgrade order, not a full OBS tutorial.
FAQ
What is new in OBS Studio 33 for playtest capture?
Plugin loading restructure with a legacy runway through 34, CEF browser update, Game Capture detection improvements, Safe Mode without WebSocket server, Ubuntu 24.04 support removal, plus assorted encoder and Studio Mode fixes. See the release notes.
Do my old plugins break on OBS 33?
OBS says existing third-party plugins continue to load from legacy locations until at least OBS 34, with a Legacy indicator in the plugin manager. Details: legacy plugin KB.
Should Ubuntu 24.04 machines install OBS 33?
No as a default — 33 removes support for Ubuntu 24.04. Stay on 32 or migrate the OS first, then reassess.
Why did my websocket tool fail in Safe Mode after updating?
33 changed Safe Mode so it does not start the WebSocket server. Test companions on a normal launch.
Is this the same as the Replay Buffer OneDrive case study?
No. That article owns empty inbox after Known Folder Move. This article owns the 33 version bump decisions.
How long do I have before legacy plugin paths die?
OBS points at OBS 34 (roughly around August 2027 in the KB framing). Treat that as author runway — still prefer updated installers when available.
Should I update during tomorrow’s playtest?
No. Lab first; bump on a quiet day; keep a rollback plan.
Where is the OBS guide on this site?
Does Arm64 NVENC mean my Snapdragon laptop is production-ready for playtests?
It means NVENC is enabled on Arm64 in 33 — still lab encode quality and driver stability before you promise VODs.
What should companies write in a capture-fleet pin note?
OBS version per OS image, 24.04 stay decision, lab smoke date, and owner of the facilitator README.
Sources
- OBS Studio 33.0.0 release (Oct 23, 2026)
- OBS Knowledge Base — Legacy Plugin Locations
- Hacker News — OBS Studio 33 (demand signal)