OBS Studio · Practical guide

OBS Opens Only in Safe Mode: Isolate a Plugin Crash

Compare normal and safe-mode launches, preserve your setup, and narrow a startup failure to a reproducible extension or scene.

START HERE

Safe mode removes third-party plugins, scripts and WebSocket activity from the launch. A successful safe-mode start narrows the investigation; it does not identify one plugin or prove the complete show is ready.

Compare normal and safe-mode launches, preserve your setup, and narrow a startup failure to a reproducible extension or scene.

In this guide
Before you start
  • A saved copy or export of your OBS profile and scene collection, if OBS can open.
  • The OBS version, operating system, and a list of recently changed plugins.

Use safe mode as a controlled comparison

A crash after installing a plugin and a crash caused by opening one particular scene can look identical at startup. Write down the last successful session, the first failed launch, and what changed between them. Include a graphics-driver update or a new media file if it happened at the same time; a recent plugin is a lead, not a verdict.

OBS documents --safe-mode as a launch option that disables third-party plugins, scripts and websockets. This makes it useful for comparison with the same installation. Sources supplied by those extensions may be absent or unusable during the check, so do not judge the finished layout from that run.

Preserve the evidence before changing extensions

Keep the working settings and the failing session log before making changes. If OBS cannot open normally, avoid wiping its configuration folder simply to get a blank window. That would remove the scene and settings needed to reproduce the fault and make a later comparison much less useful.

Make a short inventory with plugin name, installed version, installation method and the scene that uses it. Record the last action before the crash: launch, opening a filter, changing scenes, starting an output, or closing OBS. These are different reproduction paths and should not be mixed into one test.

Compare the two launch conditions

  1. Start an explicit safe-mode run

    Close OBS. On Windows, copy its shortcut and append --safe-mode after the executable path in Target. Keep the existing working directory. On macOS, launch with open -a "OBS" --args --safe-mode.

    Look for: OBS either opens under the reduced extension set or reproduces the startup failure.

  2. Recreate only the triggering action

    Open the implicated collection and perform the smallest action associated with the crash. Do not start a real broadcast. Note any missing plugin sources instead of replacing them.

    Look for: You know whether that same action can be evaluated in safe mode and whether it still fails.

  3. Compare normal mode after one change

    Use the ordinary shortcut for the next launch. Update, disable or uninstall only the suspected extension through its documented method, preserving its settings first. Repeat the recorded action.

    Look for: One identifiable change either removes the failure or leaves it reproducible.

A successful launch is only the first checkpoint

If safe mode works but normal mode fails, focus on extension-dependent behavior. Reintroduce the components needed for the affected scene one at a time, where their installation method allows that. Keep the other scene content and output settings fixed; otherwise the next successful run will not tell you which change mattered.

Once a likely extension is isolated, run a local recording using its actual sources and filters. Visit every scene that depends on it and stop the output cleanly. A plugin can load successfully yet fail when it starts processing audio or video. Keep the old and new reproduction notes together.

Report the smallest failure you can still reproduce

If safe mode also fails, broaden the investigation to the installation, device, driver, source or media involved. Do not label that result a confirmed plugin bug. A short failing collection containing only the necessary sources is more useful than an account of dozens of unrelated settings changes.

Use the official log analyzer for common configuration findings, then give support the OBS version, OS, relevant plugin versions and precise trigger. Review logs before sharing them publicly. State whether the crash happened before a window appeared or after the reproduction action; that distinction helps someone follow the same path.

Still stuck?

Safe mode starts but the scene is incomplete.

Check which missing sources depend on disabled plugins; this is a diagnostic session, not a replacement production layout.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — Launch Parameters ↗Checked 2026-11-04
  2. OBS — Log Analyzer ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Support Report Builder: Explain the Failure Before Sharing the Log

Draft a focused OBS help request with your setup, reproduction steps, expected result and checks already tried. Export it before sharing.

OBS Profile vs Scene Collection: What's the Difference?

Profiles hold your stream and recording settings, scene collections hold your scenes and sources. Know which one to duplicate before you test something.