OBS Studio 33.0 ships CEF 150 and a new plugin loader

OBS Studio 33.0 came out on October 23, 2026, with the biggest change under the hood in years. The free streaming and recording app updated its built-in browser engine from version 127 to 150. It also moved plugins to new folders, and plugins left in the old folders will stop loading in OBS Studio 34.0.

The release went up on the project's GitHub page at 22:19 UTC. It followed three release candidates, test builds published on October 9, 16 and 20.

What changed in the browser engine

OBS uses the Chromium Embedded Framework (CEF), a packaged copy of the engine inside Google Chrome. CEF draws browser sources, the web pages streamers place over a stream, such as chat boxes and alert pop-ups. It also draws docks, the web panels inside the OBS window.

Version 33.0 jumps from CEF 127 (build 6533) to CEF 150 (build 7871). The release notes say that covers CEF builds from July 2024 through September 2026. They call it "a massive update to the underlying framework used for browser sources and docks." Phoronix describes it as more than two years of changes.

The notes describe the change as backend-only. Nothing in the interface moves. The project still asks users to report any browser source that stops working.

Plugins move to new folders

Plugins are add-ons that give OBS new sources, filters and tools. Version 33.0 rewrites how OBS finds and loads them.

OBS's own plugins now live in a new folder called "core." Third-party plugins get a new install location and folder layout. The release notes say existing third-party plugins "will continue to load from the legacy locations until OBS Studio 34.0." Warp2Search reported that 33.0 flags plugins in old folders as "Legacy."

New features and fixes

The headline features are small changes to everyday editing, plus one hardware addition.

Change	What it does
Source snapping	Shows a visual guide, snaps along the whole axis and ignores hidden sources
Number boxes	Values apply on Enter without closing the window; Shift+Up/Down jumps several steps
NVENC on Arm64	NVIDIA's hardware video encoder now works on Arm-based PCs with NVIDIA GPUs
Game Capture	Better detection of full-screen games, per Phoronix
AMD AMF fix	Fixes a B-frame timing bug that could disconnect streams
macOS fix	Fixes a crash at startup on macOS 27.2

NVENC is the video encoder built into NVIDIA graphics cards. It takes the work of compressing video off the main processor. Phoronix also notes support for the newest NVIDIA Broadcast software kits.

What 33.0 drops

The release removes support for several older platforms and libraries.

• Ubuntu 24.04: official packages now target Ubuntu 26.04 on x86_64 only.
• FFmpeg 6.x and 7.x: the video library versions are no longer supported.
• Qt 6.4 through 6.9: older versions of the interface toolkit are gone.
• Build tools: Windows builds move to Visual Studio 2026 and Windows SDK 26100. Older versions "may continue to work, but will no longer be tested/supported."
• Safe Mode: it no longer starts the WebSocket server, the remote-control link that tools such as stream decks use.

What this means for developers

For plugin authors, the clock is now running. Your users can keep the old install paths through the 33.x series, but 34.0 ends that. Update your installer to the new layout now, and test it on a clean 33.0 install. The release notes point to a knowledge base article that describes the new folders.

For anyone who builds browser sources, test them on 33.0 before your next live show. A jump of 23 CEF versions can change how CSS, fonts or video autoplay behave. Alert boxes and chat widgets are the most likely to break, because they rely on web code running inside OBS.

If you run OBS on Ubuntu 24.04, you no longer get official packages for this release. Plan the move to 26.04, or stay on the 32.x series until you can.

Windows on Arm users with an NVIDIA card gain hardware encoding for the first time. That should cut processor load while streaming. Check it against your own settings before a long broadcast.

If your setup uses remote tools over WebSocket, remember they will not connect in Safe Mode. That is useful when you are troubleshooting, and confusing if you forget it.