Skip to main content
Back to blog

October 12, 2026

OBS 33 RC1: check your browser source before you update

OBS published OBS Studio 33.0 Release Candidate 1 on October 9, 2026. Check your browser source overlays before you update or go live.

On October 9, 2026, the OBS project published OBS Studio 33.0 Release Candidate 1 (opens in a new tab), a test build ahead of the stable 33.0 release. This build fixes three browser source bugs that appeared in the betas in the same cycle. For those who stream with overlays loaded by URL in OBS, the news is not the bug itself but the reminder it brings: the piece that draws your overlays is the same one that has just changed engines.

Streaming desk with two monitors and a glowing frame for an overlay

Before we go on, one distinction that avoids a scare: a Release Candidate is not a stable version. The project publishes it so that the community can test it and report problems, not to replace the setup you stream with every week. An independent version tracker, OBS Versions (opens in a new tab), dates the release to October 9, 2026 and recommends reserving this build for testing while keeping a stable installer for production work.

What changed in Release Candidate 1

The notes include three browser source fixes compared with the earlier betas: audio monitoring was briefly enabled, some sources went blank on refresh, and local network requests failed. These are issues from the testing cycle; they do not mean that people using a stable version are affected.

The engine change arrived earlier in this cycle. OBS Studio 33.0 updates CEF from version 127 to 150, moving from an engine dated July 2024 to one dated September 2026. OBS describes the work as internal and says it should be invisible to users.

Plugin organization also changes: first-party plugins move into a folder called core, while third-party plugins adopt a new structure. The notes keep loading from legacy locations until OBS Studio 34.0; the help article (opens in a new tab) explains the transition. If you depend on plugins, test them separately.

Why it matters if you stream with browser sources

A browser source is a browser inside OBS: you give it a web address and a display area. The official documentation (opens in a new tab) describes its properties, including the width and height of the area, shutting the source down temporarily while it is not visible, and refreshing it when the scene becomes active. That is where an overlay's URL lives, so a version cycle that replaces the browser engine touches the piece that many scenes depend on.

It is worth separating two ideas. The fact that OBS updates its engine does not mean that your overlay is going to fail: the notes say the work is internal and that it should go unnoticed. What changes is the burden of proof. Instead of assuming that everything will look the same as before, you check it in a test session and decide with your own data.

There is also a calendar reason. If you stream regularly, updating the program on the same afternoon as an important live stream is an unnecessary gamble, and that is true whether the version is a candidate or has just reached stable. The check is done in good time, not with the audience waiting.

Check your overlays before you risk a stream

You can repeat this procedure when OBS changes major version. Before testing, distinguish settings from the program: OBS profiles (opens in a new tab) mainly save output settings, while scene collections (opens in a new tab) hold scenes and sources. Creating another profile does not install a different version or isolate the one you use to stream. These are the recommended checks:

  • Back up your profiles and scene collections before changing the installation.
  • Test the candidate on another computer or in a test environment with a separate installation and configuration, without replacing or sharing the configuration of your stable streaming environment.
  • Open the scene and look at the real output in the program monitor, not the thumbnail in the sources panel.
  • Review the two options that alter a browser source's behavior: shutting it down when it is not visible and refreshing it when the scene becomes active. Check what happens when you return to the scene, because those two checkboxes determine whether the page stays loaded or reloads.
  • Match the size to the canvas. For Full HD, the source area is set to 1920 × 1080.
  • Leave the source visible for a while and do not judge by the first frame.
  • Repeat the test with every overlay you use regularly, not just one.

If you find a problem, return to the stable environment before going live. Then report it to the OBS project with the version, the steps to reproduce it, and the observed result. Keeping a reference of how the scene worked before the test helps explain the change without attributing every issue to the new engine.

Check movement without confusing it with compatibility

A screenshot helps you review composition and readability, but it does not confirm that a page is still updating. A static overlay can look the same in a working source and in a frozen image. Combine visual inspection with an element whose expected behavior you understand.

For this test, you can use an active countdown with an end date that is still in the future. Watch its seconds change, hide the source, and return to the scene to check its behavior after reloading. Movement is a sign that this element is updating, not proof that the entire broadcast is compatible.

If the countdown stops moving, first check whether it has finished, is paused, or has a configuration different from what you expected. Do not immediately conclude that the page has frozen. A changing number does not confirm audio, other widgets’ connections, or the output your audience receives either: each part needs its own test.

If your show already includes a wait until the next stream or event, that same countdown can be part of the rehearsal. In OverlayOn, choose a template, set the end date, and copy the URL to add it as a browser source in OBS. Test the scene you will actually use, not just a sample overlay.

The benefit is preparing and rehearsing that visible wait. OverlayOn does not change the OBS engine or guarantee compatibility with future versions. To apply this workflow, configure your countdown in OverlayOn and review movement, reloads, and the rest of the scene before going live.

Sources