OBS Crashed and Sunday's Recording Won't Play. Can We Save It?

The short answer: probably not — and here’s how it never happens again

Let’s start with the honest part, because you may be reading this on a Sunday afternoon with a 4 GB file that won’t open: a standard MP4 interrupted mid-recording is usually unrecoverable. The MP4 format writes its index — the map that tells a player what’s in the file — when recording finishes cleanly. If OBS crashed, the power blinked, or the disk filled, the map was never written. The video data is in there; almost nothing can read it. Repair tools exist and occasionally succeed, but the OBS community’s long, sad archive of these threads mostly ends the same way.

If the sermon also went out live, check the stream platform — YouTube and Facebook keep the broadcast, and that copy may save your week. Then take the next ten minutes to make sure this particular heartbreak is structurally impossible from now on. Three layers do it.

Layer 1: a recording format that survives interruption

This is the single most valuable settings change in church OBS, and it takes thirty seconds. In Settings → Output, set the recording format to MKV — a format that stays playable up to the moment of interruption. A crash costs you the final seconds, not the service. When you need MP4 for editing or upload, OBS converts losslessly in one click: File → Remux Recordings. Recent OBS versions also offer a hybrid MP4 designed to survive interruptions — either choice is fine; plain MP4 is the only wrong one.

While you’re in the settings: recordings fail for boring reasons too. A disk quietly filling is the classic — local recordings eat gigabytes per hour, and a drive that runs dry mid-service can take the recording down with it. Which brings us to the second layer.

Layer 2: automation that notices before Monday

The cruelest property of recording failures is their silence. The stream looks fine, the room sounds fine, and the loss is discovered after — when the file someone needed doesn’t exist. Machines are better at this vigil than humans: Tech Manager checks continuously whether a recording that should be rolling actually is, and the moment a recording stops unexpectedly, it tells you and offers a one-tap restart — on the booth and on your phone. That’s Self Healing, with every offer and answer logged. Disk pressure gets caught early too: an alert fires before free space becomes a Sunday problem.

One deliberate boundary worth knowing: if OBS itself crashes outright, Tech Manager reports it and alerts a human rather than silently relaunching — a crash can mean a corrupted scene collection or failing hardware, and blind restarts can compound the damage. Routine failures get a one-tap fix; ambiguous ones get a phone that buzzes.

Layer 3: a second copy that doesn’t live on the booth PC

Formats and automation protect the local recording. The final layer removes the single point of failure entirely: churches that stream through WorshipMetrics live streaming get every service recorded automatically in the cloud — no button, no booth-PC dependency, finished recordings landing in the library where Monday’s sermon clips start. The local MKV becomes your high-quality master; the cloud copy is the one that exists no matter what happened at the desk.

Three layers, and the arithmetic changes completely: for a crash to cost you a sermon now, the format, the automation, and an independent recording all have to fail at once.

The part that isn’t about software

A closing observation from the support desk: “the recording didn’t record” is rarely a solo-software story. It’s usually a solo-operator story — one person running everything, with no attention left for the silent failures. The booths where this never happens twice have a second set of eyes, a recording/archivist seat that owns exactly this (a wonderful first role for a detail-loving student), and the habit of reading the health report on Monday instead of discovering things.

If this is the third different failure in a month, the recording was never really the problem — read a different OBS problem every Sunday for the pattern underneath.