Skip to content
TroubleGrid

OBS 33 Crashes on Startup or When Adding a Browser Source (libcef.dll)

Last verified November 2026Tested against OBS Studio 33.0.1 (29 October 2026) - latest release as of 18 November 2026; still affected, OBS Studio 33.0.0 (23 October 2026) - also affected by the service-integration startup crash fixed in 33.0.1, OBS Studio 33.0.2 - hotfix with the env-variable fix, not released as of 18 November 2026, OBS Studio 32.1.2 and 32.2.2 - reported working by affected users, Windows 10 and Windows 11 (including 26H2)Good evidence

OBS 33 swapped in a much newer browser engine (CEF 150), and at least three different bugs now crash it with libcef.dll or obs-browser.dll. First make sure you are on 33.0.1, which fixed the crash for people logged into Twitch or YouTube. Then start in Safe Mode: if that works, a third-party plugin is involved. If it crashes even in Safe Mode, check Windows for GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET - an OBS developer confirmed deleting them stops the crash, and the fix is queued for 33.0.2. Rolling back to 32.x is the fallback.

The crash report usually names libcef.dll with exception 80000003, sometimes obs-browser.dll with c0000005, or a crashed CrBrowserMain thread. All of these sit in OBS's embedded browser, which runs browser sources, chat docks and custom browser docks. That is why the crash tends to follow people who use overlays or docks. The tricky part is that the same crash line has different causes, and the fix for one does nothing for another. The steps below are ordered so each one also tells you which cause you have.

Symptoms

  • OBS 33.0.0 or 33.0.1 closes at launch, or as soon as a scene collection with browser sources or docks loads
  • The crash log shows Unhandled exception: 80000003 in libcef.dll
  • The crash log shows Unhandled exception: c0000005 in obs-browser.dll, with QCefWidgetInternal::Init on the stack
  • The crash log shows a CrBrowserMain thread marked (Crashed)
  • OBS crashes as soon as you add a new Browser Source, even after a clean install
  • The crash started right after updating from OBS 32 and goes away if you reinstall 32.x

Why this happens

Startup crash with service integration docks (fixed in 33.0.1)

On 33.0.0, OBS could crash at launch if you had connected a Twitch or YouTube account and docked its panels, because the browser engine was torn down while the saved dock layout was restored. OBS fixed this in 33.0.1 by initializing browser docks later in startup.

Make sure you are on 33.0.1, not 33.0.0

GOOGLE_DEFAULT_CLIENT_ID / GOOGLE_DEFAULT_CLIENT_SECRET set in Windows

If these two Windows environment variables exist with any value other than "no", the new browser engine trips an internal consistency check when OBS turns off browser sign-in, and OBS crashes. Because it happens before plugins matter, it crashes even in Safe Mode and even after a clean reinstall. An OBS developer confirmed the cause on the issue tracker, and the fix (obs-browser #562) was merged on 17 November 2026 for the 33.0.2 hotfix.

Check for GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET, and delete them · Install 33.0.2 when it ships

A third-party plugin that creates browser docks

One confirmed-reproducible report on 33.0.1 crashes in obs-browser.dll while a browser dock is created, and only with a specific plugin loaded (Aitum Vertical 1.6.7). Disabling third-party plugins stops it. This report is still open and OBS has not identified a cause.

Start in Safe Mode to see whether a plugin is involved · Roll back to OBS 32.x if you need it working now

Fixes

Make sure you are on 33.0.1, not 33.0.0

about 5 min

33.0.1 fixed a startup crash for anyone logged into a service integration such as Twitch or YouTube, plus a Twitch login crash and a YouTube login deadlock. If you are still on 33.0.0, this alone may be the fix.

Applies to: OBS Studio 33.0.0 on Windows

  1. If OBS opens long enough, check the version in Help > About. Otherwise check the OBS entry under Apps > Installed apps in Windows Settings.
  2. If it says 33.0.0, download 33.0.1 from obsproject.com or the OBS GitHub releases page and run the installer over your existing install.
  3. Start OBS again. If it still crashes on 33.0.1, the cause is one of the others below.

Confirmed by the vendor.

Source: OBS Project (GitHub), OBS Project (GitHub)

Start in Safe Mode to see whether a plugin is involved

about 15 min

Safe Mode runs OBS without third-party plugins, scripts and websockets, so it splits the causes. Stable in Safe Mode means a plugin is involved; still crashing means it is not, and the environment-variable check below is the next thing to look at.

Applies to: OBS Studio 33.0.1 on Windows

  1. After a crash, OBS offers to launch in Safe Mode the next time it starts - accept. If OBS is already open, Safe Mode can also be started from the Help menu.
  2. If OBS now opens and loads your scenes, a third-party plugin is involved. Reports so far point at plugins that create their own browser docks, such as Aitum Vertical 1.6.7.
  3. Quit OBS, then turn third-party plugins back on one at a time (in OBS's Plugin Manager, or by moving the plugin files back into place) and restart after each, until the crash returns. Leave that plugin off and check its developer's page for an update built for OBS 33.
  4. If OBS crashes even in Safe Mode, a plugin is not the cause. Go to the environment-variable check below before rolling back.

Reported to work by 2 users; not confirmed by the vendor. 2 report it did not help.

Source: OBS Project (GitHub), OBS Project (GitHub), OBS Project (GitHub), OBS Project (GitHub), OBS Project Forums

Install 33.0.2 when it ships

The environment-variable fix is merged and listed in the 33.0.2 hotfix as "Fixed a browser-related startup crash on Windows". It was not released as of 18 November 2026.

Applies to: OBS Studio 33.0.1 on Windows

  1. Watch for 33.0.2 in OBS's update prompt or on the OBS GitHub releases page.
  2. Install it over 33.0.1. If you deleted the GOOGLE_ variables only for OBS, you can then restore them.

Confirmed by the vendor.

Source: OBS Project (GitHub), OBS Project (GitHub)

Check for GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET, and delete them

Check before applyingabout 5 min

This is the cause an OBS developer confirmed for crashes that survive Safe Mode and clean reinstalls. Deleting the two variables stops the crash until 33.0.2 makes OBS immune to them.

Applies to: OBS Studio 33.0.0 and 33.0.1 on Windows 10 and 11

Before you do this

Something on your PC set these variables, and deleting them may change how that program behaves. Record the values before deleting them so you can put them back if another app breaks. Once OBS 33.0.2 is out it should no longer crash with them present.

  1. Open Start, type environment variables, and open "Edit the system environment variables". Select the Environment Variables button.
  2. Look in both lists - User variables at the top and System variables at the bottom - for GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET.
  3. If neither exists, this is not your cause; move on to the next step.
  4. If they exist, write down their names and values first, in case another program on your PC was relying on them. Then select each one, choose Delete, and press OK to close both windows.
  5. Close OBS completely and start it again. Programs read environment variables when they start, so an already-open OBS or launcher will not see the change; sign out and back in if OBS still crashes.

Confirmed by the vendor.

Source: OBS Project (GitHub), OBS Project (GitHub), The Chromium Project

Roll back to OBS 32.x if you need it working now

Check before applyingabout 15 min

Both affected Windows reporters who went back to 32.x - one on 32.2.2, one on 32.1.2 - say it runs with the same scenes, plugins and profile. It is the fallback when you cannot tell which cause you have.

Applies to: OBS Studio 33.0.0 and 33.0.1 on Windows

Before you do this

Settings saved by OBS 33 are not guaranteed to load correctly in an older version. Back up the obs-studio settings folder first so you can restore it if a scene or profile looks wrong after the rollback.

First:

  • A copy of the %APPDATA%\obs-studio folder
  1. Back up your setup first. Open File Explorer, type %appdata% in the address bar, and copy the obs-studio folder somewhere safe - it holds your scene collections and profiles. If OBS opens in Safe Mode, you can also use Export in the Profile and Scene Collection menus.
    %APPDATA%\obs-studio
  2. Download the OBS 32 installer for Windows from the OBS GitHub releases page (32.2.2 or 32.1.2 were both reported working).
  3. Run it over your existing install, then start OBS and check that your scenes and browser sources load.
  4. Decline the update to 33.0.1 when OBS offers it, until 33.0.2 is out.

Reported to work by 2 users; not confirmed by the vendor.

Source: OBS Project (GitHub), OBS Project (GitHub), OBS Project Forums, OBS Project

Known issues

  • Startup crash for users logged into a service integration (Twitch, YouTube) with docked panels. Fixed in OBS 33.0.1 on 29 October 2026.

    Affects OBS Studio 33.0.0 · Status: fixed

  • Crash in libcef.dll (80000003) when GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET are set. Fix merged 17 November 2026 (obs-browser #562) and queued for 33.0.2, which is not released yet. Deleting the variables works around it.

    Affects OBS Studio 33.0.1, OBS Studio 33.0.0 · Status: workaround only

  • Crash in obs-browser.dll (c0000005, QCefWidgetInternal::Init) while creating a browser dock with a third-party plugin loaded. Open, no cause identified by OBS.

    Affects OBS Studio 33.0.1 · Status: open

If none of this worked

On Linux, including Flatpak builds on Bazzite and CachyOS, OBS 33 has a different libcef crash (SIGILL in libcef.so on the MemoryInfra thread) that tends to hit after running a while with browser-heavy scenes. That one is fixed by an updated CEF build (PR #14181) listed for 33.0.2; until then, Linux users have reported 32.x as stable. On Windows, if your crash log names neither libcef.dll nor obs-browser.dll, this page is probably not your problem - post your log URL on the OBS forums, where volunteers read the full log rather than just the crash line.

Common questions

Why did OBS 33 start crashing when 32 was fine?
OBS 33.0.0 updated its embedded browser engine (CEF) from version 127 to 150. Browser sources, chat docks and custom browser docks all run on it, so setups with overlays and docks are the ones exposed to the new crashes.
Does turning off browser source hardware acceleration help?
Not for these crashes. One reporter on 33.0.0 disabled browser source hardware acceleration and even removed all 18 browser sources, and OBS still crashed at startup.
What sets GOOGLE_DEFAULT_CLIENT_ID on a PC?
OBS has not said, and the affected user simply found both set to random-looking values. These are the variable names Chromium-based software reads for Google API credentials and browser sign-in, so another program or a developer setup guide may have added them. Write them down before deleting them in case something else needs them.
Will a clean reinstall of OBS fix it?
Not if the cause is the environment variables: one user crashed again as soon as they added a Browser Source after a clean install. A full clean reinstall of OBS and StreamElements did fix one forum user's 33.0.1 crash, but it is the slowest option and does not address the confirmed causes.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • A Windows 10 user on OBS 33.0.1, upgraded from 32 through the built-in updater, crashes with Unhandled exception 80000003 in libcef.dll, even in Safe Mode
    • The reporter has multiple custom browser docks and browser sources, and says downgrading to 32.2.2 solves the issue
    • A second user crashed as soon as they added a Browser Source after a clean install and rebuilding their scenes
    • An OBS member (prgmitchell) asked the reporter to check Windows environment variables via Start > 'environment variables' > Environment Variables
    • The reporter found GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET set to random values (not "no")
    • The OBS member said deleting those variables will stop the crash and that the next hotfix should include obs-browser PR #562 to prevent it entirely
    • The issue was closed as completed on 17 November 2026 via obs-browser #562
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • PR #562 disables browser sign-in before profile creation to prevent a consistency-check crash in CEF
    • PR #562 was merged on 17 November 2026 and fixes obs-studio issue #14155
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • An open PR collects fixes for a 33.0.2 hotfix release targeting the release/33.0 branch
    • Its list includes "Fixed a browser-related startup crash on Windows" (obs-browser #562)
    • Its list includes "Fixed a crash related to browser source memory allocation on Linux" (#14181)
    • As of 18 November 2026 the PR is open and the branch has not been deployed, so 33.0.2 is not yet released
  • OBS Project (GitHub) · Release notes · checked Nov 18, 2026

    • OBS Studio 33.0.1 was released on 29 October 2026 and is the latest release as of 18 November 2026
    • 33.0.1 "Fixed a crash on startup when logged into a service integration"
    • 33.0.1 fixed a crash when logging into the Twitch integration and a deadlock when logging into the YouTube integration
    • 33.0.0 updated CEF, the browser engine behind browser sources and docks, from 127 to 150
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • PR #554 delays CEF and browser dock initialization at startup to avoid a crash in specific configurations
    • The reproduction is on Windows: connect a Twitch account, dock the service integration docks, close the Chat dock, then restart OBS
    • PR #554 was merged on 27 October 2026 and is linked to obs-studio issue #14088
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • OBS 33.0.0 on Windows 11 26H2 crashes on startup with an existing scene collection, exception 80000003 in libcef.dll, as a regression from 32.1.2
    • The issue carries the issue/confirmed label and is linked to obs-browser PR #554
    • The reporter's collection loads in Safe Mode and OBS starts with an empty collection
    • Removing third-party plugin DLLs, disabling browser source hardware acceleration and removing all 18 browser sources did not stop the reporter's crash
    • A second user reported the same crash
  • OBS Project (GitHub) · Release notes · checked Nov 18, 2026

    • Safe Mode runs OBS without third-party plugins, scripting, and websockets
    • When OBS detects it was not shut down properly it offers to launch in Safe Mode
    • Safe Mode can also be activated manually from the Help menu
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • A separate libcef crash (SIGILL in libcef.so, MemoryInfra thread) affects OBS 33 on Linux, is labelled platform/linux and kind/regression, and is not the Windows crash
    • It was closed on 17 November 2026 via PR #14181, which updates the bundled CEF build, and an OBS contributor said the fix was not yet released
  • The Chromium Project · Documentation · checked Nov 18, 2026

    • Chromium reads GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET as runtime environment variables
    • The page ties GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET to browser sign-in and tells users to remove them from their environment settings to avoid sign-in errors
  • OBS Project · Documentation · checked Nov 18, 2026

    • The Profile menu's Import/Export can export the current profile's settings to a JSON file for backup
    • Profiles do not store scenes; scene collections do
  • OBS Project (GitHub) · GitHub issue · checked Nov 18, 2026

    • OBS 33.0.1 on Windows 11 26H2 crashes on startup with Unhandled exception c0000005 in obs-browser.dll (QCefWidgetInternal::Init) when a browser dock is initialized
    • Disabling all third-party plugins stops the crash, and re-enabling Aitum Vertical 1.6.7 brings it back
    • Installing 32.1.2 over the top with the same plugins and profile works without crashes
    • As of 18 November 2026 the issue is open with no linked fix; an OBS member noted the crash happens while browser docks are prepared
  • OBS Project Forums · Forum · checked Nov 18, 2026

    • A user on OBS 33.0.1 with StreamElements crashed after opening with CrBrowserMain (Crashed), and Safe Mode still crashed
    • Reinstalling StreamElements alone, clearing caches and resetting docks did not help that user
  • OBS Project Forums · Forum · checked Nov 18, 2026

    • OBS Studio stores its settings on Windows in C:\Users\<name>\AppData\Roaming\obs-studio, reachable by typing %appdata% in File Explorer
    • The File menu has a Show Settings Folder shortcut, and Scene Collection and Profile menus have Export/Import