OBS Studio 33.0.0 is out, and its biggest changes are the ones you will never see on screen. The free and open source app for video recording and live streaming, released on October 24, 2026, replaces the browser engine behind its browser sources and docks, and it rebuilds how plugins are loaded. The release notes describe the browser work as backend-only and intended to be invisible to users, while the plugin overhaul sets up a cleaner install layout that becomes mandatory in the next major version (obsproject/obs-studio, GitHub, retrieved 2026-10-24). For streamers, the practical news is simpler: browser overlays now run on a browser that is two years newer, and plugin authors have one release cycle to move to the new locations.
Key Takeaways
OBS Studio 33.0.0, released on October 24, 2026, is a major update to the free and open source recording and live streaming app for Windows, macOS, and Linux.
The Chromium Embedded Framework behind browser sources jumps from version 127 to 150, moving the embedded browser from July 2024 code to September 2026 code.
Plugin loading is fully overhauled: built-in plugins move to a new core folder and third-party plugins get new install locations, with legacy locations supported only until OBS Studio 34.0.
Everyday editing improves: sources snap along a whole axis, number fields behave properly, and NVIDIA NVENC encoding arrives on Arm64 systems.
The release also drops older foundations: FFmpeg 6.x and 7.x, Qt 6.4 through 6.9, and official support for Ubuntu 24.04.
The 33.0 cycle was a long one. Beta builds ran from late September 2026, followed by release candidates through October, the last on October 20, before the stable build landed on October 24. The previous stable release, 32.2.2, dated from August 14, 2026. That timeline explains the character of this release: most of the work went into foundations that had been waiting for a major version bump, not into new buttons for the main window.
What Is OBS Studio?
OBS Studio is a free and open source program for recording video and streaming it live to platforms such as YouTube and Twitch. You build a scene from sources, such as a camera, a game capture, a microphone, or a web page, and OBS Studio composites them into one video feed. Streamers, educators, podcasters, and event teams use it because it costs nothing and runs on Windows, macOS, and Linux. If the open source model itself is new to you, our What Is Open Source? explainer covers what it means in plain language.
Two terms matter for understanding this release. A browser source is a scene element that renders a web page inside OBS Studio, which is how streamers show alerts, chat overlays, tickers, and donation widgets without a second app. A plugin is an add-on that extends OBS Studio, for example with new transitions, audio filters, or remote control features. Both depend on the plumbing this release replaces, which is why a release with few visible features still matters to almost every user. The same scene system also hosts talking avatars for virtual streamers, as in our Mesh Avatar Studio article.
What Changed in OBS Studio 33.0
The release notes group the changes into new features, general changes, bug fixes, and developer notes. The table below summarizes the items most users will feel, and the sections after it explain each one.
Area | What changed in OBS Studio 33.0 |
|---|---|
Browser engine | Chromium Embedded Framework updated from 127 to 150, from July 2024 to September 2026 code |
Plugin loading | Built-in plugins move to a core folder; third-party plugins get new locations; legacy locations work until 34.0 |
Source snapping | Sources snap along a whole axis, with a new visual indicator, and no longer snap to hidden sources |
Number fields | Typing is no longer blocked, values are no longer cut off, and changes apply after pressing Enter |
Hardware | NVIDIA NVENC encoding enabled on Arm64, plus support for newer NVIDIA Broadcast SDKs |
Dropped support | FFmpeg 6.x and 7.x, Qt 6.4 through 6.9, and official support for Ubuntu 24.04 |
A Two Year Newer Browser Inside Your Scenes
Chromium Embedded Framework (CEF) is the embedded web browser that powers browser sources and browser docks in OBS Studio. Version 33.0 updates it from 127/6533 to 150/7871, which the release notes describe as a massive update from the July 2024 release to September 2026. In practice, that closes roughly two years of Chromium development in one jump. The release notes put it this way:
"This is a massive update to the underlying framework used for browser sources and docks from the July 2024 release to September 2026. All of this work is on the backend and should be invisible to users."
Why should a streamer care about a browser version? Because a large share of a modern stream is a web page: the alert box that pops when someone subscribes, the chat overlay, the event list, the countdown timer. Those pages run inside OBS Studio on CEF, so an old CEF means missing web features, older security patches, and web content that renders differently from a current browser. The update should be invisible, as the release notes say, and that is the point: overlays keep working, but on a current engine. The project does ask users to report any new odd behavior with browser sources, which is sensible advice after a jump this large.
The Plugin Overhaul, and What to Do Before 34.0
The second structural change is a complete overhaul of plugin loading. First-party plugins, the ones shipped with OBS Studio, now live in a new folder named core. Third-party plugins have an updated installation location and folder structure. Existing third-party plugins installed in the old locations will continue to load for now, but that compatibility ends with OBS Studio 34.0. The project documents the new layout in its knowledge base article on legacy plugin locations.
The practical advice follows from that deadline. If you stream with third-party plugins, check whether each plugin author has published an update for the new locations, and test the new install before a show that matters. One release cycle sounds generous until a plugin you depend on is maintained by one person in their spare time. Plugin authors, meanwhile, should move now rather than during the 34.0 cycle, when the old paths stop working entirely. The overhaul is also meant to make installing and updating plugins more stable and consistent over time, which is a real pain point today, when plugin installs differ across platforms and installers.
Small Editing Fixes That Add Up
Not everything in 33.0 is plumbing. Source snapping in the preview gets a visible upgrade: sources now snap along an entire axis instead of only when their edges directly touch, a new visual indicator shows the alignment, and sources no longer snap to hidden sources, which previously made precise layouts frustrating. Number fields, known as spinboxes, get a similar cleanup: typing is no longer mysteriously blocked in some situations, numbers are no longer cut off, values update only after pressing Enter, and holding Shift while pressing Up or Down moves in larger steps. These are the fixes you notice at 11 pm while rearranging a scene before a stream, and they remove a steady drip of annoyance.
On the hardware side, 33.0 enables NVIDIA NVENC encoding on Arm64 systems and adds support for the newest NVIDIA Broadcast SDKs for audio and video effects. NVENC is NVIDIA's dedicated hardware video encoder, which encodes the stream without loading the main processor the way software encoding does. Arm64 support matters because it brings hardware encoding to the growing number of Arm-based Windows machines and single-board setups used for portable streaming rigs. New hotkeys for controlling audio monitoring of individual sources round out the workflow changes, so you can mute or monitor a source without opening its settings.
Fixes That Make Streams More Reliable
The bug fix list is long, and several entries address failures that interrupt a live show. On Linux, 33.0 fixes a potential crash when a USB microphone is disconnected and fixes PipeWire screencast sources appearing duplicated in Studio Mode. In Studio Mode generally, it fixes grouped sources glitching or leaking into the live Program output when moved. Recording reliability improves with better splitting of Hybrid MP4/MOV files, and a potential deadlock during video and audio processing is fixed. On the encoder side, it fixes an AMD AMF issue with B-frame offsets that could disconnect a stream. The stable build also fixes a crash on macOS 27.2 at startup. Independent coverage from Linuxiac highlights the same set of fixes and notes the compatibility changes below.
One change deserves a note for remote production setups: Safe Mode no longer starts the WebSocket server. If you control OBS Studio remotely through a WebSocket-based tool, a Safe Mode session will not expose that control channel, which is a sensible safety default, but it can surprise you if you troubleshoot a broken setup in Safe Mode and expect remote control to keep working.
What 33.0 Drops, and Why It Matters
Major versions are also when projects cut old weight, and 33.0 cuts three things. It removes support for FFmpeg 6.x and 7.x, the multimedia libraries OBS Studio builds on, and for Qt 6.4 through 6.9, the interface toolkit behind its windows and dialogs. It also removes official support for Ubuntu 24.04. For most users on current installers, none of this changes anything: the official builds carry their own current libraries. It matters most to people who build OBS Studio themselves or maintain distribution packages, who must now build against newer FFmpeg and Qt. If you run Ubuntu 24.04, check your distribution's OBS Studio package or use the project's official builds and Flatpak instead of assuming the old package will track new releases.
Who Should Upgrade, and Who Should Wait
Most streamers should upgrade, after one precaution: back up your scene collections and profiles first, then check your third-party plugins against the new locations. The browser engine update alone is worth it, since it brings two years of web platform and security work into every overlay you run. Users with heavy plugin setups should upgrade on a quiet day, not an hour before a scheduled show, and confirm each plugin loads and behaves. Users who build from source or package OBS Studio for a distribution should plan for the FFmpeg and Qt changes before moving. And if your entire show depends on a plugin whose author has gone quiet, keep your current install until you have a tested replacement, because the legacy locations disappear in 34.0 either way.
Frequently Asked Questions
Is OBS Studio free? Yes. OBS Studio is free and open source software for video recording and live streaming, available for Windows, macOS, and Linux. There is no paid tier for the core program.
What is new in OBS Studio 33.0? The headline changes are a Chromium Embedded Framework update from version 127 to 150 for browser sources, a complete overhaul of plugin loading with a new core folder and new third-party locations, improved source snapping and number fields, and NVIDIA NVENC encoding on Arm64 systems.
Will my plugins still work after upgrading? Yes, for now. Third-party plugins installed in legacy locations continue to load in OBS Studio 33.0, but that compatibility ends with OBS Studio 34.0. Check with each plugin author for an update that installs to the new locations, and test before a show that matters.
What does the browser engine update change for viewers? Nothing visible, by design. Overlays, alerts, and chat widgets keep working, but they now run on a browser engine from September 2026 instead of July 2024, which brings newer web features and security patches to everything rendered inside OBS Studio.
Which systems and libraries lose support in 33.0? OBS Studio 33.0 removes official support for Ubuntu 24.04 and drops FFmpeg 6.x and 7.x and Qt 6.4 through 6.9 for builds. Most users on official installers are unaffected, but people who build from source or maintain packages should update their toolchains.
The Bottom Line
OBS Studio 33.0 is a maintenance release in the best sense: it pays down two years of browser engine debt, gives plugins a cleaner home, and fixes a list of show-interrupting bugs, all without asking streamers to relearn anything. The one deadline to respect is the plugin move, because legacy locations end in 34.0. Download it from the OBS Studio 33.0.0 release notes, read the legacy plugin locations guide before you upgrade a plugin-heavy setup, or read the Indonesian version of this article.