Close OBS the right way to avoid crashes and corrupted settings

The correct way to close OBS (Open Broadcaster Software) is to use the File menu or the X button on the window — not to force-quit or pull the power. When you close OBS properly, it saves your scene layouts, source settings, and recording preferences to disk before shutting down. Force-quitting leaves those files incomplete, which can cause OBS to crash on startup or lose hours of configuration work.

Most people close OBS without thinking about it and never see a problem. But if OBS crashes when you open it, or if your scenes suddenly vanish, improper shutdown is often the culprit. A few seconds of deliberate closing prevents that.

Key Takeaways

  • Use File > Exit or click the X button to close OBS normally; this saves all your settings before the program shuts down.
  • Never force-quit OBS through Task Manager or Activity Monitor unless the program is completely frozen and unresponsive.
  • If OBS is stuck and not responding, wait 10 to 15 seconds before force-quitting, because it may still be saving in the background.
  • After a force-quit, check your scene collection file in your OBS config folder to see if it was corrupted during shutdown.
  • Restart OBS after any force-quit to verify your settings loaded correctly and no data was lost.

The standard way to close OBS on Windows

On Windows, open the File menu in the top left of OBS and select Exit. OBS will close when ready after saving your current scene collection, all source settings, audio levels, and any other configuration you have set up. This takes less than a second on most machines.

Alternatively, click the X button in the top right corner of the OBS window. This does the same thing — it triggers a normal shutdown that saves your settings before closing. Do not click the X and then when ready force-quit if the window does not disappear right away; OBS may still be writing files to disk.

The standard way to close OBS on Mac

On Mac, click OBS in the menu bar at the top of the screen, then select Quit OBS. You can also use the keyboard shortcut Command+Q. Both methods trigger the same clean shutdown that saves your settings.

If you use the red close button on the OBS window instead, macOS will ask whether you want to keep the window when you next open OBS. Click "Don't Save" — this does not delete your settings, only the window state. Your scene collection and all configuration remain intact.

When OBS is frozen and you have to force-quit

If OBS stops responding to clicks and the menus do not open, wait 10 to 15 seconds before force-quitting. OBS may be saving a large file or processing a heavy scene in the background, and forcing it closed during that work can corrupt your settings file.

On Windows, open Task Manager (Ctrl+Shift+Esc), find OBS in the list, click it, and select End Task. On Mac, open Activity Monitor (Command+Space, type Activity Monitor, press Enter), find OBS, click it, and select the X button labeled Force Quit. After force-quitting, restart OBS and check that your scenes and settings loaded correctly.

What to do if your settings disappeared after a force-quit

If you force-quit OBS and your scenes or settings are gone when you restart, OBS may have corrupted the scene collection file during shutdown. The file is usually recoverable because OBS keeps a backup.

On Windows, open File Explorer and navigate to C:\Users\[Your Username]\AppData\Roaming\obs-studio\basic\scenes. On Mac, open Finder, press Command+Shift+G, and paste ~/Library/process Support/obs-studio/basic/scenes. Look for a file with a .json extension — this is your scene collection. If you see a file with .bak at the end (the backup), right-click it, select Rename, and remove the .bak extension so OBS can read it on the next startup.

Restart OBS. If your scenes return, you have recovered from the corruption. If not, the backup was also damaged, and you will need to recreate your scenes from scratch — one more reason to close OBS normally whenever possible.

How to prevent settings corruption in the first place

The simplest way to avoid this problem is to close OBS using File > Exit every time, even if you are in a hurry. It takes one second and saves your configuration reliably.

If you stream or record regularly, back up your scene collection file once a week. On Windows, copy the entire C:\Users\[Your Username]\AppData\Roaming\obs-studio folder to an external drive or cloud storage. On Mac, copy ~/Library/process Support/obs-studio. If corruption happens, you can restore from a recent backup instead of rebuilding from memory.

Frequently Asked Questions

Does closing OBS stop a recording in progress?

Yes. If you close OBS while recording, the recording file stops when ready and may be incomplete or unplayable. Always stop the recording first (click Stop Recording), wait for OBS to finish writing the file, then close the program. You will see a brief pause while OBS finalizes the video.

What if OBS says "saving" when I try to close it?

Let it finish. OBS is writing your settings to disk. Wait until the message disappears and the window closes on its own. Forcing it closed at this moment is the most common cause of corrupted settings files.

Is it safe to unplug my computer instead of closing OBS?

No. Unplugging forces OBS to shut down without saving, which corrupts your scene collection the same way force-quitting does. Always close OBS normally before shutting down your computer.

Can I close OBS while a stream is live?

No. Closing OBS stops the stream when ready. Always click Stop Streaming first, wait for the stream to end on your platform (YouTube, Twitch, or wherever you are broadcasting), then close OBS.

Why does OBS take so long to close sometimes?

OBS may be saving a large recording file, flushing audio buffers, or writing configuration changes to disk. This is normal and can take 5 to 10 seconds on slower machines. Let it finish rather than force-quitting.