How to Stop Screen Recording in OBS and Save It

OBS has no Save button, and that is not an oversight. The file is written continuously while you record, so by the time you click Stop Recording most of it is already on disk. Stopping is not "saving" in the way a document editor saves. It is closing the file properly.

That distinction is the whole reason this page exists. Everything that goes wrong at the end of an OBS recording goes wrong in the two or three seconds between clicking stop and OBS finishing the close, and the fix is almost always a setting you changed before you ever hit record.

Stopping the Recording

There are three ways to end a take, and they are not identical.

1. The Controls dock. Bottom right of the main window, click Stop Recording. If the button says Stop Streaming instead, you are looking at the wrong control: streaming and recording are separate outputs and stopping one does not stop the other.
2. A hotkey. Settings → Hotkeys → Stop Recording. Bind something you cannot hit by accident, and note that OBS hotkeys fire globally, so they work while another application is focused. This is the only sensible option if you are recording the whole desktop, since walking back to the OBS window puts the OBS window in your video.
3. The system tray icon. Right click the OBS tray icon (Windows) or menu bar icon (macOS) and choose Stop Recording. Useful when OBS is minimised and you do not want to raise it.

If you have both a stream and a recording running, stop the recording first. It is the output that can be damaged by an abrupt shutdown.

What Happens in the Two Seconds After You Click Stop

This is the part nobody explains, and it is worth understanding because it tells you exactly what a stuck stop means.

When you click stop, OBS stops feeding frames to the encoder, waits for the encoder to flush whatever it is still holding, then writes the container's index: the table that tells a player how long the video is and where each frame lives. In a standard MP4 that index is called the moov atom, and it is written at the very end.

So a standard MP4 has a hard property: until that final write completes, the file contains all your video data and no map to it. Players will refuse to open it. That is why a force quit at the wrong moment turns a 4 GB recording into an unplayable 4 GB file, and why the recovery guides all talk about rebuilding an index rather than recovering lost footage. The footage was never lost. The map was never written.

When It Sticks on "Stopping Recording..."

The button greys out, the label reads Stopping Recording..., and nothing happens for what feels like a very long time.

First, wait. Thirty seconds is normal on a long recording, and on a heavily loaded machine it can be a minute or more. OBS is draining an encoder queue that built up during the session. Killing it here is the single most common way people destroy a take.

While you are waiting, the cause is usually one of these:

• The encoder was behind for the whole recording. If View → Docks → Stats showed frames missed due to encoding lag climbing during the session, there was a backlog to flush at the end. That is encoder overload, and it shows up at the stop as much as during the take.
• The drive cannot keep up. A slow external disk, a nearly full drive, or network storage will hold the final write open. Recording to an internal SSD removes this entirely.
• You are writing to a remote or synced folder. OneDrive, Dropbox and Google Drive folders can lock the file mid write. Record locally, move it afterwards.

If OBS has genuinely hung and you have to force quit, whether you keep the recording depends entirely on the container format, which brings us to the setting that matters most.

Pick a Format That Survives a Bad Stop

Settings → Output → Recording → Recording Format.

Hybrid MP4 is the answer for most people now. It was added in OBS 30.2 specifically to combine MKV's crash resistance with a container everything can open, and it removes the old trade off where you had to choose between a safe file and a convenient one. If you are on an older OBS build, record MKV instead. On macOS, recent OBS versions default to fragmented MOV, which is also safe.

There is one more setting worth turning on in the same place. Settings → Advanced → Recording → Automatically remux to mp4 takes the safe container you just recorded and rewrites it as an MP4 the moment the recording ends, without re-encoding. You get crash safety during the take and a normal MP4 on disk afterwards, with no manual step. If you would rather do it after the fact, File → Remux Recordings does the same job in batch, and converting OBS MKV files to MP4 covers the edge cases.

Do not use a video converter for this. Remuxing repackages the existing stream in seconds and changes nothing about the picture. Re-encoding costs quality and time for no reason.

Confirm the File Actually Closed

Three checks, in order of how much they tell you:

1. File → Show Recordings opens the output folder with the newest file selected. If the file is there and the size is plausible, the write finished.
2. Play the last ten seconds, not the first ten. Corruption from a bad close shows up at the end. A file that opens and scrubs to the end is a file that closed cleanly.
3. Help → Log Files → View Current Log, then search for Writing file. OBS logs the literal path it wrote, which is the definitive answer when the folder you expected is empty.

A file whose duration reads as 00:00 or whose size is 0 KB never got its index. For that case, recovering a corrupted OBS recording walks through the repair options. For "the file saved fine but I have no idea where OBS put it", where OBS recordings go on Windows and Mac is the reference, including the separate paths Simple and Advanced modes keep.

The Habits That Prevent All of This

• Record to an internal drive with real free space. OBS will happily record until the disk fills and then fail at the worst possible moment.
• Use Hybrid MP4 or MKV, with automatic remux on.
• Stop with a hotkey rather than clicking, so the end of your video is not a shot of you moving the mouse toward OBS.
• Give it a few extra seconds before closing OBS or shutting down. The recording is not finished when the button changes, it is finished when the file stops growing.
• If a take really matters, check it before you tear down the setup, not the next morning.

The Part That Comes After Stopping

Worth naming, because it is the actual reason people are looking for a save button.

Almost nobody wants the file. They want the thing the file is for: a link in a Slack thread, an answer attached to a support ticket, a walkthrough sent to a customer. OBS ends its job at "a large local file exists", and everything after that is manual. Find it, check it, compress it because it is 3 GB, upload it somewhere, wait, copy the link.

Cubix Capture closes that gap. Recordings are already framed and zoomed toward wherever you were working, and when you stop you get a finished video and a shareable link rather than a raw file to process. It runs on Windows and macOS, and the free Starter plan is enough to record a real walkthrough and see where the two workflows actually differ.

If you are streaming, building scenes, or need frame-level control over your encoder, OBS remains the right tool. Just record it in a container that forgives a bad stop.

Keep Reading

• How to Pause and Resume Recording in OBS for the mid-take equivalent of this page, including why the pause button goes missing.
• Where Do OBS Recordings Go on Windows and Mac for the default paths and how to change them.
• OBS MKV vs MP4: Which Should You Use for the format decision in full.
• How to Convert OBS MKV to MP4 for remuxing after the fact, in batch.
• OBS Crashed Mid Recording: Is the File Recoverable for when the stop never completed.