The GitHub release page for OBS Studio 33.0.0 lists the massive CEF upgrade and plugin overhaul.
OBS STUDIO 33.0.0 RELEASE OVERHAULS PLUGIN SYSTEM AND CEF
*OBS Studio 33.0.0 lands on 23 Oct, pushing the browser engine two years forward and reshaping plugin loading. The upgrade promises silent user impact while demanding developers adapt to new folders, APIs, and toolchain requirements.*
OBS Studio 33.0.0 dropped on GitHub on 23 Oct at 22:20, marking the most extensive codebase shift since the July 2024 release. The update pushes the Chromium Embedded Framework two years forward, revamps plugin loading, and sprinkles UI refinements across the board. Streamers will notice little on the surface, but developers face a new folder hierarchy, deprecated APIs, and stricter build‑tool requirements. The release also removes support for Ubuntu 24.04, older FFmpeg streams, and Qt 6.4‑6.9, signaling a clean‑up of legacy dependencies while laying groundwork for upcoming features.
What does the OBS Studio 33.0.0 update change?
The release upgrades Chromium Embedded Framework from version 127/6533 to 150/7871, moving the browser core from a July 2024 baseline to September 2026. The change is backend‑only; users should see no visual shift but are urged to report any new oddities in browser sources. A complete overhaul of plugin loading relocates first‑party plugins to a new "core" folder and revises third‑party installation paths, though legacy locations remain functional until OBS 34.0. UI tweaks include a new visual indicator for source snapping, full‑axis snapping, and removal of hidden‑source snapping. Spinbox inputs now accept typing, stop cutting numbers, and only commit on Enter, with Shift + Up/Down stepping multiple values. NVENC encoding is finally enabled on Arm64 devices.
How does the new plugin architecture affect developers?
First‑party plugins now reside in a folder named "core," separating them from third‑party extensions that have a refreshed directory structure. Existing third‑party plugins continue to load from legacy locations, but will be phased out by OBS 34.0. Safe Mode now disables the WebSocket server and prevents any third‑party plugins from loading, while a new obs_frontend_is_safe_mode flag lets developers detect this state. Documentation updates add guidance on the theme system and introduce a file‑extension filter for OBS_PATH_FILE_SAVE types. Deprecations include hidden source APIs and audio source monitoring_type APIs, signaling a clean‑up of unused code paths.
Which bugs were finally fixed in this release?
The 33.0.0 build addresses a startup error when obs‑transitions fail, improves Hybrid MP4/MOV file splitting, and stops outputs from hanging on bad rescale resolutions. Crashes on macOS 27.2 at launch, shader cache invalidation, and Linux USB‑mic removal are all resolved. Source‑toolbar crashes, profile import failures on trailing‑slash paths, and deadlocks during video/audio tasks have been patched. Game Capture now better detects fullscreen games, and PipeWire screencast sources no longer duplicate in studio mode. Monitoring icon desynchronisation with third‑party tools or websockets is fixed, and repeated preview enable/disable toggles work correctly.
What developer toolchain updates accompany OBS 33?
OBS now requires Visual Studio 2026 and Windows SDK 26100, with older versions no longer tested. The clang‑format toolchain moves to version 22.1.3. libnsgif is upgraded to 1.0.0, a breaking change for plugins using gs_image_file. MbedTLS 3 is mandated, explicitly excluding version 4 or later. Support for FFmpeg 6.x and 7.x, as well as Qt 6.4‑6.9, has been dropped. Flatpak plugin extension points receive version tags, and new API calls like obs_canvas_video_active() and obs_canvas_reset_video() expand canvas control. These shifts push developers toward up‑to‑date build environments and prepare the codebase for future extensions.
Frequently asked questions
When was OBS Studio 33.0.0 released?
OBS Studio 33.0.0 was released on 23 Oct at 22:20, according to the GitHub tag.
What is the new location for first‑party plugins in OBS 33?
First‑party plugins are now placed in a new folder named "core".
Does OBS 33 support NVENC on Arm64?
Yes, NVENC encoding is enabled on Arm64 in the 33.0.0 release.
OBS 33.0.0 sets a high bar for stability and forward compatibility, yet it also forces developers to re‑engineer plugin layouts and update toolchains. With OBS 34.0 looming, the community will watch how the new core folder and deprecations shape third‑party ecosystems. The silent user experience masks a substantial internal overhaul that could dictate the next wave of streaming innovation.
Sources: [GitHub OBS Studio 33.0.0 release page]