OBS Studio 33
- ID
- 39079
- Status
- summarized
- Published
- 24 Oct 2026, 12:49 PM
- Fetched
- 24 Oct 2026, 11:34 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/obsproject/obs-studio/releases/tag/33.0.0
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.5
- Created
- 24 Oct 2026, 11:35 PM
- Tags
- Audience
- developersvibe_coders
What happened
OBS Studio 33.0.0 ships a complete overhaul of plugin loading: first-party plugins move into a new `core` folder and third-party plugins get a new install location and folder structure, but existing third-party plugins keep loading from the legacy paths only until OBS 34.0. The release also jumps CEF from 127/6533 to 150/7871 (roughly July 2024 to September 2026), enables NVENC on Arm64, and reworks source snapping, spinbox input, Studio Mode groups, and Game Capture fullscreen detection.
Why it matters
If you maintain or ship an OBS plugin, the legacy install path is now on a deprecation clock that expires at 34.0 — you have one release cycle to move to the new folder structure or your plugin stops loading. If you only use OBS, the CEF 127-to-150 jump is the thing to watch: browser sources and docks run on a framework two years newer, and the release notes explicitly ask for bug reports on browser-source weirdness.
Discussion angle
Is a single release cycle (33 to 34) enough notice for a plugin ecosystem migration, or does this repeat the classic open-source breakage pattern where the tool maintainers move faster than the plugin authors can ship?