OBS Crashed Mid Recording - Is the File Recoverable?

Your recording was forty minutes deep when OBS died. The window vanished, or Windows greyed it out and stopped repainting it, and now you are staring at your recordings folder trying to work out whether the last hour still exists.

Here is the short version: the file is almost certainly still on your drive, and whether it plays depends on a setting you chose before you hit record, not on anything you do now. What you do in the next five minutes still matters though, because a few common reflexes will destroy footage that was otherwise perfectly recoverable.

This is the triage guide. Work through it in order, and do not open a repair tool until you reach the step that tells you to.

Before Anything Else: Three Reflexes That Destroy Recoverable Footage

1. Do not reopen OBS and hit record again yet. OBS timestamps filenames by default, so a collision is unlikely, but if you set a fixed filename and ticked Overwrite if file exists under Settings > Advanced > Recording, your next take will write straight over the footage you are trying to save.
2. Work on a copy. Before you touch any repair tool, copy the broken file to a second folder. Most repair utilities rewrite in place, and a failed pass on the original leaves you with nothing to retry.
3. Do not delete it because Explorer says 0 KB. Explorer caches file sizes and frequently reports a stale figure for a file that was open when the process died. Check the real size properly in the next step before you write the take off.

Step 1: Find the File and Check Its Real Size

Your recordings are wherever Settings > Output > Recording Path points. If you never changed it, that is C:\Users\<you>\Videos on Windows and ~/Movies on macOS.

Right-click the file and open Properties to read the true size on disk:

• Several hundred MB or more: the encoder was flushing to disk normally. Your footage is there. Continue to Step 2.
• Genuinely 0 bytes: OBS opened the container but never wrote a frame, which usually means it died in the first second or two of the take. There is nothing on the drive to rebuild, and no tool can recover it.

Step 2: Read the Extension. It Decides Everything.

The container format you recorded into determines whether this is a thirty-second fix or a salvage operation.

The reason is structural, and it is worth thirty seconds of your attention because it is exactly what you will configure around in Step 5.

MKV, TS and FLV are streaming containers. They write each packet with enough local information to be read back on its own. If the process dies, the file simply ends at that millisecond and everything before it is intact.

MP4 and MOV are indexed containers. They rely on a metadata block called the moov atom, which maps where every frame lives and how audio aligns to it. OBS can only compile that map once it knows the full length of the recording, so it writes it the moment you press Stop Recording. Crash before that and you are left with a large pile of valid video packets and nothing that tells a player how to read them.

Step 3: The MKV Path. Remux and Get On With Your Day.

If you recorded to MKV, TS or FLV, you do not need recovery software at all. Your file is complete, it just is not in an editor-friendly wrapper yet.

1. Open OBS Studio.
2. Click File > Remux Recordings in the top menu bar.
3. Drop your file into the OBS Recording field. The target field fills in automatically with a matching .mp4 path.
4. Click Remux.

Remuxing rewraps the existing packets into an MP4 container without re-encoding, so it takes seconds and costs you nothing in quality. Keep the original MKV until you have played the MP4 all the way to the end, including a scrub to the final minute, and only then delete it.

If OBS refuses to remux the file, that is a real signal rather than a quirk. It means the stream itself is damaged rather than merely unwrapped, and you should treat it as a salvage job using the repair bench in OBS Crashed and Recording Corrupted: Can You Recover It?.

Step 4: The MP4 Path. What Salvage Actually Looks Like.

If you recorded straight to MP4 or MOV and OBS never reached a clean stop, no converter will open the file. Handbrake and VLC both fail immediately, because they are looking for an index that was never written.

The footage is not necessarily gone. The fix is to rebuild the missing index by borrowing the structure of a healthy recording made with identical settings, using an open-source tool called Untrunc. It works often enough to be worth trying and it is free.

That process, the exact reference-file requirements that make or break it, the ffmpeg fallback, and how to read the specific symptom your file is showing are all covered step by step in the companion guide: OBS Crashed and Recording Corrupted: Can You Recover It?

Set expectations honestly before you start: a rebuilt MP4 usually comes back with audio drift in the final seconds, and takes ended by a hard power cut or a bluescreen recover far less reliably than ones ended by OBS alone quitting.

Step 5: Make the Next Crash a Non-Event

This is the part that actually matters, and it takes about forty seconds. You do not have to choose between MKV's crash safety and MP4's editor compatibility. OBS will give you both.

1. Open Settings > Output and switch to the Recording tab.
2. Set Recording Format to MKV (or hybrid MP4, if you are on OBS 30.2 or newer, which writes an MP4 that survives a crash).
3. Open the Advanced tab in the left sidebar.
4. Under Recording, tick Automatically remux to mp4.

With this configured, OBS records into a crash-safe container the whole way through, then quietly hands you a clean MP4 the instant you stop normally. If the power drops or OBS dies at minute fifty-nine, you keep all fifty-nine minutes. There is no downside and no extra step in your workflow, which is why it should have been the default all along.

The Real Lesson: Your Recorder Should Not Have a Failure Mode This Expensive

Every fix above is damage control for one design decision: OBS treats your recording as a live broadcast stream, and a broadcast that ends abruptly is simply a broadcast that ended. That assumption is correct for streaming. It is a terrible fit for someone recording a product walkthrough who assumed the file was being saved as they went.

If your work is tutorials, onboarding videos, demos or course modules, you are carrying a broadcast tool's risk profile for no benefit. Cubix Capture writes recoverable video continuously rather than assembling an index at the end, so a crash costs you the last second rather than the whole take. There is no format decision to get wrong, and no salvage procedure to learn at the worst possible moment.

Ask yourself what that lost hour was worth. That is the real price of the setting you did not know you had to change.

Keep Reading

• OBS Crashed and Recording Corrupted: Can You Recover It? covers the repair bench in full, including Untrunc and ffmpeg.
• OBS Keeps Crashing: How to Fix It stops the crashes that put you here.
• OBS Not Responding: What to Do explains how to force-kill a hung OBS without losing the take.
• OBS Recording Stuttering: Fix Choppy Video if the salvaged footage plays back rough.