Screen Recording Repair: Fix Corrupted OBS, Zoom, Teams & Game Captures

Screen recordings fail at the worst possible moments. You finish a two-hour tutorial, a critical Zoom meeting, or an epic gaming session — and the file is corrupted, won't play, or shows as 0 bytes. The frustration is real, but the situation is almost always recoverable.

Screen recording corruption follows predictable patterns depending on the software used. OBS Studio, Zoom, Microsoft Teams, NVIDIA ShadowPlay, AMD ReLive, and Xbox Game Bar each have their own failure modes and corresponding repair strategies. This guide covers all of them, from quick one-click fixes to advanced command-line recovery.

The golden rule: always work on a copy of the corrupted file before attempting any repair.

Why Screen Recordings Get Corrupted

The MP4 MOOV Atom Problem

Most screen recording software outputs MP4 files by default. MP4 is a great playback format, but it has a critical weakness: the MOOV atom — the metadata index containing frame locations, duration, and codec info — is written only when recording stops cleanly.

If the recording is interrupted (crash, freeze, power loss), the MOOV atom is never written. The result: a file full of valid video data that no player can read. This is the single most common cause of screen recording corruption.

If your recorder now throws a literal moov atom not found error after an OBS crash or forced shutdown, jump to moov atom not found after OBS crash for the shorter exact-error path before trying broader recovery tactics.

Software-Specific Causes

Software	Common Failure	Root Cause
OBS Studio (MP4)	0-byte file or unplayable	Crash before MOOV atom written
OBS Studio (MKV)	Last few seconds missing	Crash during final buffer flush
Zoom	.zoom file won't convert	Interrupted meeting or app crash
Microsoft Teams	Recording unavailable	OneDrive/SharePoint processing failure
NVIDIA ShadowPlay	Corrupted MP4	Game crash or system freeze during capture
AMD ReLive	Broken replay clip	Driver crash or GPU reset during recording
Xbox Game Bar	Empty or short recording	Background recording limit hit or app conflict
General	Audio/video desync	Encoder overload, dropped frames

Method 1: Use the Recording Software's Built-in Recovery

Before reaching for external tools, check whether your recording software has a built-in fix.

OBS Studio — Remux Recordings

OBS has a dedicated remux tool that converts MKV recordings to MP4. If you recorded in MKV (which you should — more on that later), this is your first stop.

1. Open OBS Studio
2. Go to File > Remux Recordings
3. Select your .mkv file
4. Click Remux
5. OBS creates a .mp4 file in the same directory — no re-encoding, no quality loss

This takes seconds even for multi-hour recordings. If the MKV file plays but you need MP4 for sharing or editing, this is the cleanest conversion path.

Zoom — Built-in Recording Converter

Zoom local recordings are saved as .zoom files that need conversion to MP4.

1. Navigate to your Zoom recording folder (default: Documents/Zoom/[meeting name])
2. Double-click the .zoom file — Zoom's converter launches automatically
3. If the converter doesn't appear, open Zoom, go to Settings > Recording, and click Open next to the local recording path
4. Zoom processes the file into separate video.mp4 and audio.m4a files

If the double-click method fails, the .zoom file may be too damaged for Zoom's converter. Skip to Method 3 (FFmpeg) for manual recovery.

Xbox Game Bar — Check Known Folders

Xbox Game Bar saves recordings to C:\Users\[username]\Videos\Captures by default. If a recording appears missing:

1. Open Xbox Game Bar (Win + G)
2. Click the Gallery widget
3. Check if the recording appears there but with an error indicator
4. Try opening the file directly with VLC Media Player

Method 2: VLC Media Player Repair

VLC can handle many types of screen recording corruption through its built-in repair and transcoding capabilities.

Direct playback attempt:

VLC is more tolerant of corruption than most players. Simply try opening the file — VLC may play it even if Windows Media Player or QuickTime refuse.

Re-mux through VLC:

1. Open VLC, go to Media > Convert / Save
2. Click Add and select the corrupted file
3. Click Convert / Save
4. Choose profile "Video - H.264 + MP3 (MP4)"
5. Set a destination filename and click Start

This re-wraps the video data in a fresh container, fixing index and header issues without re-encoding the actual video content.

Method 3: FFmpeg Command-Line Repair

FFmpeg is the most versatile tool for screen recording repair. These commands cover the most common scenarios.

Basic container repair (fixes metadata/index issues):

ffmpeg -i corrupted_recording.mp4 -c copy repaired.mp4

MKV to MP4 remux (alternative to OBS Remux):

ffmpeg -i recording.mkv -c copy -movflags +faststart output.mp4

The -movflags +faststart flag places the MOOV atom at the beginning of the file, which enables streaming playback and is generally more robust.

Repair a truncated recording (generate missing timestamps):

ffmpeg -fflags +genpts -i corrupted.mp4 -c copy repaired.mp4

Skip corrupted sections and salvage what's possible:

ffmpeg -err_detect ignore_err -i corrupted.mp4 -c copy repaired.mp4

Extract audio from a corrupted video (save the meeting audio at least):

# Extract audio as MP3
ffmpeg -i corrupted_recording.mp4 -vn -acodec libmp3lame -q:a 2 audio_only.mp3

# Extract audio as original codec (no re-encoding)
ffmpeg -i corrupted_recording.mkv -vn -c:a copy audio_only.m4a

Fix audio/video desync (common with overloaded encoders):

# Shift audio forward by 0.5 seconds
ffmpeg -i desync_recording.mp4 -itsoffset 0.5 -i desync_recording.mp4 -map 0:v -map 1:a -c copy synced.mp4

Not comfortable with command-line tools? Magic Leopard™ Video Repair handles corrupted screen recordings automatically — just upload the file and let the AI figure out the repair strategy. No commands, no technical knowledge required.

Method 4: Reference-Based Recovery (Untrunc)

When FFmpeg's basic repair fails with "moov atom not found," you need a reference file to rebuild the metadata structure.

1. Create a reference file: Make a short (10-30 second) recording using the exact same software and settings as the corrupted file
2. Prepare the reference:

   ffmpeg -i reference.mp4 -c copy -movflags faststart reference_fixed.mp4

3. Run untrunc:

   untrunc reference_fixed.mp4 corrupted_recording.mp4

Untrunc is open-source and works well with screen recordings because the encoding parameters are consistent throughout the file.

Method 5: Magic Leopard™ Video Repair (Automated)

For users who want a no-hassle solution, Magic Leopard™ Video Repair provides automated recovery:

• Upload the corrupted screen recording
• The AI identifies the recording software, codec, and corruption type automatically
• Preview the repaired video before downloading
• Supports MP4, MKV, AVI, and WebM from all major screen recording tools
• Works entirely in your browser — no software installation needed

Software-Specific Repair Guides

OBS Studio

OBS is the most popular screen recording and streaming tool, and its recordings have specific recovery paths.

Recovering from OBS crashes (MKV recordings):

If you recorded in MKV and OBS crashed, the file is almost certainly recoverable. MKV writes metadata continuously, so the recording is playable up to the moment of the crash. Simply use File > Remux Recordings in OBS or the FFmpeg remux command above.

Recovering 0-byte OBS recordings:

A true 0-byte file means no data was written. This happens when:

• The output path doesn't exist or lacks write permissions
• The disk was full before recording started
• OBS crashed immediately on record start

Unfortunately, 0-byte files cannot be recovered — there's no data to repair. Check OBS's log file (Help > Log Files > Show Current Log) for error details.

OBS crash recovery for MP4 recordings:

If you recorded in MP4 and OBS crashed, the file may have data but no MOOV atom. Check the file size — if it's larger than a few KB, the video data is likely present. Use the FFmpeg or untrunc methods above to rebuild the metadata.

If the file exists but every player or tool reports a missing moov atom, follow the dedicated moov atom not found after OBS crash workflow. That page is tuned for the exact "recording has size, but final metadata never closed" scenario.

Why OBS recommends MKV over MP4:

OBS explicitly recommends MKV as the default recording format. The reason is simple: MKV is crash-resilient. Unlike MP4, MKV writes its metadata index throughout the recording process. If OBS crashes, the system freezes, or you lose power, everything recorded up to that point is preserved. You can always remux MKV to MP4 afterward with zero quality loss. There is no downside to this workflow.

Zoom Recordings

Local recording repair:

Zoom local recordings go through a conversion step after the meeting ends. If this conversion fails:

1. Check Documents/Zoom/[meeting date and name]/ for .zoom files
2. Double-click the .zoom file to retry conversion
3. If conversion fails, rename the .zoom file to .mp4 and try FFmpeg:

   ffmpeg -i meeting_recording.mp4 -c copy repaired_meeting.mp4

4. If the file contains only audio, extract it:

   ffmpeg -i meeting_recording.mp4 -vn -c:a copy meeting_audio.m4a

Cloud recording issues:

Zoom cloud recordings are processed on Zoom's servers. If a cloud recording shows "Processing" for more than 24 hours or fails entirely, the issue is server-side. Contact Zoom Support — the raw recording data may still be recoverable from their infrastructure.

Microsoft Teams

Teams recordings work differently from other screen recording tools because they're stored in the cloud.

Where Teams recordings are stored:

• Personal/ad-hoc meetings: OneDrive for Business (Recordings folder)
• Channel meetings: SharePoint (in the channel's Recordings folder)

Common Teams recording issues and fixes:

• "Recording not available": Check the meeting chat — the recording link is posted there. If the link is broken, check OneDrive/SharePoint directly
• Download fails: Clear browser cache, try a different browser, or use the OneDrive desktop app to sync the file
• Recording stuck on "Processing": Wait up to 24 hours. If it persists, contact your Microsoft 365 administrator
• Recording is incomplete: Teams has a maximum recording length of 4 hours. Longer meetings require restarting the recording. Check if multiple recording files exist

Game Recording Software

NVIDIA ShadowPlay (GeForce Experience)

ShadowPlay records in MP4 with H.264 or H.265 encoding. Corruption typically occurs when:

• The game crashes during recording
• The system freezes (GPU driver crash)
• Instant Replay buffer is interrupted

Repair steps:

1. Check C:\Users\[username]\Videos\ for the recording
2. Try FFmpeg basic repair:

   ffmpeg -i shadowplay_clip.mp4 -c copy repaired.mp4

3. If that fails, create a short reference clip with the same ShadowPlay settings and use untrunc
4. For Instant Replay clips that are partially corrupted, FFmpeg with error detection disabled often recovers most of the footage

AMD ReLive (Adrenalin Software)

AMD ReLive saves recordings to C:\Users\[username]\Videos\Radeon ReLive\ by default. AMD driver crashes are the primary cause of corruption.

Repair steps:

1. Locate the file in the ReLive output folder
2. Try VLC playback first — ReLive corruption is often minor
3. Use FFmpeg container repair if VLC fails
4. If the AMD driver crashed mid-recording, the file may be truncated but the existing data is usually intact

Xbox Game Bar

Xbox Game Bar recordings are saved as MP4 in C:\Users\[username]\Videos\Captures\.

Common issues:

• Recording stops unexpectedly: Background recording has a default limit (check Settings > Gaming > Captures for the max recording length)
• No audio in recording: Ensure "Record game audio" is enabled in Game Bar settings. Some games' audio engines conflict with Game Bar's capture
• File won't play: Use FFmpeg to re-mux: ffmpeg -i gamebar_clip.mp4 -c copy repaired.mp4

Preventing Screen Recording Corruption

Recording Settings

• Use MKV format in OBS — Always. Record in MKV, remux to MP4 when done. This single change eliminates 90% of OBS recording corruption
• Enable auto-remux in OBS — In Settings > Advanced, check "Automatically remux to MP4" to streamline the MKV-to-MP4 workflow
• Avoid recording to your system drive — Use a separate SSD for recordings to prevent I/O contention
• Match encoder to hardware — Use NVENC (NVIDIA), AMF (AMD), or QuickSync (Intel) hardware encoders to reduce CPU load and dropped frames

System Stability

• Close unnecessary applications during recording to free RAM and CPU
• Update GPU drivers — Outdated drivers are a leading cause of ShadowPlay and ReLive crashes
• Monitor disk space — Ensure at least 10-20 GB free on the recording drive. Screen recordings at 1080p consume roughly 1-2 GB per hour; 4K recordings consume 4-8 GB per hour
• Use a UPS (uninterruptible power supply) if power outages are common in your area

Backup Practices

• Don't rely on a single recording — For critical content, run a backup recording (e.g., OBS + Game Bar simultaneously)
• Upload important recordings to cloud storage promptly after the session
• For Zoom meetings, enable both local and cloud recording as redundancy

Conclusion

Screen recording corruption is common but highly recoverable. The repair approach depends on the recording software: OBS users should switch to MKV format and use the built-in remux tool, Zoom users can retry the .zoom file conversion, and game capture users can lean on FFmpeg for MP4 container repair. For any screen recording that resists these methods, reference-based recovery with untrunc or automated repair with Magic Leopard™ handles the rest. The best fix, though, is prevention — record in MKV, keep your system stable, and always have a backup plan.

---

📚 Related Resources

• Video Repair Center — Complete video restoration solutions for all formats
• MP4 Repair Guide — In-depth MP4 repair techniques for any source
• AVI & WMV Repair Guide — Fix corrupted AVI and WMV video files
• Professional Video Repair Guide — Advanced techniques for complex corruption
• File Corruption Causes — Understand why files get corrupted
• Best File Repair Tools 2026 — Compare top video and file repair software

🙋 Frequently Asked Questions

Q: Why is my OBS recording 0 bytes or won't play?

A 0-byte OBS recording typically means the application crashed before any data was flushed to disk, or the output path was invalid. If the file has some size but won't play, it's likely an incomplete MP4 missing its MOOV atom. OBS recommends recording in MKV format specifically to avoid this — MKV files write metadata continuously, so even crash-interrupted recordings remain playable. If you already have a broken MP4, try FFmpeg: ffmpeg -i broken.mp4 -c copy repaired.mp4 or use Magic Leopard™ Video Repair.

Q: How do I use OBS Remux Recordings to fix my video?

Open OBS Studio, go to File > Remux Recordings. Select your MKV file and click Remux. OBS will convert it to a playable MP4 without re-encoding, preserving full quality. This is the recommended workflow: record in MKV for crash safety, then remux to MP4 when the recording is complete. The process takes only seconds regardless of file size.

Q: Can I recover a corrupted Zoom local recording?

Yes. First, try double-clicking the .zoom file in your Zoom recording folder — Zoom's built-in converter will attempt to process it into a usable MP4. If that fails, rename the file to .mp4 and try playing it in VLC or repairing it with FFmpeg. For Zoom cloud recordings that failed to process, contact Zoom support as the raw data may still exist on their servers.

Q: Why can't I download my Microsoft Teams recording?

Teams recordings are stored in OneDrive (personal meetings) or SharePoint (channel meetings). Download failures usually stem from expired sharing links, insufficient permissions, or OneDrive storage quota issues. Check the meeting chat for the recording link, verify your access permissions, and ensure your OneDrive isn't full. If the recording shows as "processing" for more than 24 hours, contact your IT administrator.

Q: How do I fix a corrupted NVIDIA ShadowPlay recording?

ShadowPlay records in MP4 format, which is vulnerable to corruption if the game crashes or the system freezes during recording. Try ffmpeg -i corrupted.mp4 -c copy repaired.mp4 first. If FFmpeg reports "moov atom not found," the file needs a MOOV atom rebuild — record a short reference clip with the same ShadowPlay settings and use untrunc or Magic Leopard™ Video Repair to reconstruct the metadata.

Q: Why does OBS recommend MKV over MP4 for recording?

MP4 files write their metadata index (MOOV atom) only when recording stops cleanly. If OBS crashes, the system freezes, or power is lost, the MOOV atom is never written and the entire recording becomes unplayable. MKV (Matroska) writes metadata continuously throughout the recording, so even if a crash occurs, everything recorded up to that point is preserved and playable. OBS's official recommendation is to record in MKV and remux to MP4 afterward.

---

📖 More resources: How Video Repair Works | Fix Video Won't Play

Fix Your Screen Recording Now

Corrupted OBS, Zoom, or game capture file? Try our video repair tool — it automatically detects the recording software and applies the right fix.

Try Magic Leopard™ Video RepairBrowse Video Guides