Video Won't Play? How to Fix Corrupted Video Files

Few things are more frustrating than trying to open a video file only to be met with an error message, a black screen, or a player that refuses to cooperate. Whether it is a family vacation clip, a critical work recording, or footage from your latest creative project, a video that won't play can feel like lost data.

The good news is that in most cases, the video file itself is not truly gone. The footage is still sitting on your drive, but something in the file's internal structure has gone wrong. Understanding what causes these failures and knowing how to fix them can save you hours of frustration and potentially recover footage you thought was lost forever.

If you want the low-level explanation first, our guide to how video repair works breaks down the MP4 structure behind these failures. If the broken file came from a specific device, jump to the iPhone repair guide, the GoPro repair guide, or the dashcam repair guide for more targeted steps.

This guide walks you through the most common reasons videos stop playing, quick checks you can perform before attempting a repair, and a step-by-step process for fixing corrupted video files using VideoRepair.

The Real-World Scenarios This Guide Covers#

This page is most useful when your situation looks like one of these real patterns:

• a GoPro or action-camera clip became unreadable after the battery died, the camera overheated, or the recording was interrupted
• a dashcam saved every file except the one clip you actually needed, often after the car lost power or the camera's internal battery failed
• a DJI drone or action-camera file shows a normal size on the SD card but will not open after a crash, forced shutdown, or interrupted recording
• an iPhone or camera transfer completed with errors, and the copied file will not open even though the original device still seems fine
• the video has audio but no picture, shows a black screen, freezes on one frame, or scrubs oddly even though the file is not empty

These scenarios often look different on the surface, but they usually fall into one of two buckets:

1. the file structure is damaged and needs repair
2. the file is intact, but your device or player cannot decode it correctly

The rest of this guide is about telling those two cases apart quickly.

Common Reasons Why Videos Won't Play#

Video files are more complex than they appear on the surface. A single MP4 or MOV file contains multiple data streams (video, audio, subtitles) along with a metadata structure that tells the player how to read everything. When any part of this structure breaks down, the entire file can become unplayable.

Here are the most frequent causes:

File Corruption During Recording#

This is by far the most common scenario. When a camera, phone, or screen recorder is interrupted mid-recording, the file often ends up without its critical metadata. In MP4 files, this metadata lives in a structure called the "moov atom," which is typically written at the very end of the recording. If the recording stops unexpectedly due to a battery dying, a power outage, an app crash, or the storage running out of space, the moov atom never gets written. The result is a file that contains all the actual video and audio data but lacks the index the player needs to read it.

This is the classic "file has a believable size, but nothing will open it" case. It shows up often with GoPro clips after battery loss, with dashcam files after the ignition cuts power, and with drone footage after a crash or forced shutdown.

Incomplete Downloads or Transfers#

Downloading a video from the internet or transferring it between devices can introduce corruption if the process is interrupted. A dropped network connection, a USB cable being unplugged too early, or a cloud sync error can all leave you with a partial file. These files may have the correct file extension but are missing chunks of data, making them unplayable.

This also happens in more subtle ways. A file may play on the original phone, camera, or SD card, but the copied version on your laptop or external drive fails because the transfer was interrupted or the destination disk had a write issue.

Storage Media Failures#

Hard drives develop bad sectors over time. SD cards and USB drives can suffer from wear-leveling issues. Even SSDs are not immune to data degradation. When a video file happens to sit on a damaged portion of your storage, parts of the file become unreadable. The file might open but show visual artifacts, freeze partway through, or refuse to play entirely.

Codec and Container Mismatches#

Sometimes the video file itself is perfectly fine, but your media player does not have the right codec to decode it. This is especially common with newer codecs like HEVC (H.265) or AV1, or with less common container formats. The player may show an error suggesting the file is corrupted when it simply cannot understand the encoding.

DJI and newer iPhone workflows create this confusion all the time. A file may look "broken" on an older Mac, Windows laptop, or default player when the real issue is codec support, unfinished on-device processing, or a player that cannot handle the recording format smoothly.

Software Bugs and Encoding Errors#

Video editing software, screen recorders, and encoding tools can occasionally produce malformed files. A bug in the encoder might write incorrect header information, create misaligned data streams, or produce a file that technically violates the format specification. These files might play in some players but fail in others.

Quick Checks Before Repairing#

Before diving into file repair, it is worth ruling out simpler explanations. A few minutes of troubleshooting can save you time.

Try a Different Media Player#

Not all media players handle video formats equally. If your video won't play in one player, try another. VLC Media Player is an excellent first choice because it supports virtually every video and audio format and has built-in error resilience. If VLC can play the file (even partially), the issue is likely with your original player rather than the file itself.

Use this as your first branching test:

• if the file plays correctly in VLC but not in QuickTime, Windows Media Player, Photos, or your editor, the file may be intact and your playback stack is the problem
• if the file fails everywhere, including VLC, the file structure is more likely damaged
• if it opens but freezes, stays black, or only plays audio, the media may be present but the metadata or video stream is damaged

Check the File Size#

Compare the file size to what you would expect. A one-hour 1080p video recorded on a phone typically ranges from 2 to 6 GB depending on the bitrate. If your file is only a few kilobytes or significantly smaller than expected, it may be severely truncated and harder to recover. On the other hand, if the file size looks reasonable, there is a good chance the video data is intact and only the metadata needs repair.

This is why users often say things like "the file is 3.6 GB, so something has to be there." They are usually right. A realistic file size is one of the strongest signs that repair is still worth trying.

Verify the File Extension#

Occasionally, files get renamed with the wrong extension. A file named video.mp4 that is actually an MKV or AVI container will confuse most players. On macOS, you can check the true file type by right-clicking and selecting "Get Info." On Windows, ensure file extensions are visible in File Explorer settings.

Confirm Your System Has the Right Codecs#

If you see an error about unsupported formats or missing codecs, the fix might be as simple as installing a codec pack. For Windows, the K-Lite Codec Pack covers most formats. On macOS, installing VLC or IINA usually resolves codec issues. If the video plays fine after installing codecs, the file was never corrupted in the first place.

This matters especially for newer DJI or iPhone recordings that may use HEVC. In those cases, "won't play" can mean "this machine cannot decode it smoothly" rather than "the file is broken."

Check Whether the Original Device Can Still Finalize the File#

Before you run repair, try putting the original SD card or storage back into the recording device and powering it on normally.

• Some GoPro and DJI devices attempt to repair or finalize interrupted files when they boot again.
• If the file is still on the original card, this can sometimes restore playback without any extra work.
• If you copied the broken file off the card and deleted or moved the original, that chance may be gone.

If the file is already lost at the device level, or the device's own repair step fails, a dedicated repair workflow is the next step.

A Fast Way to Tell Codec Problems From Real Corruption#

Use this rule of thumb:

• Likely codec/playback issue

  • the file plays on one device but not another
  • the file opens in VLC but not in your default player
  • the file came from a newer DJI, iPhone, or camera using HEVC/H.265
  • the file only fails after transfer to an older machine or editor

• Likely structural corruption

  • the recording ended abruptly because of battery loss, crash, app failure, or sudden shutdown
  • the file has a normal size but will not open anywhere
  • the file has audio but no video, black screen, or frozen frames
  • only the last clip from a session is broken
  • the camera or drone showed a repair message, but the clip still does not play

If your case falls into the second group, a repair tool is usually the right next step.

How to Fix Corrupted Video Files#

If the quick checks above did not solve the problem, the file likely has structural damage that needs repair. VideoRepair is designed specifically for this scenario. It analyzes the internal structure of your video file, identifies what is broken, and reconstructs the missing or damaged metadata so the file becomes playable again.

Here is how to fix your corrupted video file step by step:

1. Open VideoRepair in your browser. There is nothing to install. The tool runs locally with WebAssembly, so your files stay on your device.

2. Upload the file that will not play. VideoRepair supports MP4, MOV, M4V, M4A, and 3GP formats, which cover common files from phones, action cameras, drones, dashcams, and camera transfers. If your file is specifically 3GP, use our dedicated page to repair 3GP files online for a faster, format-specific workflow.

The current browser-based workflow accepts video files up to 4GB per file. Because processing happens locally, you are not limited by upload bandwidth or server-side file size restrictions.

3. Add a reference file if you have one. This is especially useful for GoPro, dashcam, drone, and dedicated camera files when the corruption is severe or the metadata is missing completely.

4. Start the repair. VideoRepair analyzes the file in chunks, identifies whether the issue is damaged metadata, missing indexes, or incomplete finalization, and applies the repair strategy automatically.

During this process, VideoRepair performs several operations:

• Scans the file structure to identify the container format and locate existing metadata
• Detects whether critical structures like the moov atom are present, damaged, or missing entirely
• If metadata exists but is damaged, it repairs chunk offsets and rebuilds the index
• If metadata is missing completely, it scans the raw video data frame by frame to reconstruct the entire metadata structure from scratch

5. Preview and download. When the repair is complete, preview the repaired result in your browser. If playback looks correct, download the fixed file.

What If the Repair Does Not Work?#

In some cases, the standard repair process may not fully recover the file, especially if the video uses unusual codec parameters or if the corruption is severe. This is where the reference file feature comes in.

If your case already looks like a classic structural-damage case, you can go directly to the repair workspace and test the file before paying.

When to Use a Reference File#

A reference file is a healthy, playable video that was recorded with the same device and settings as the corrupted file. VideoRepair can extract codec parameters, frame rates, resolution, and other technical details from the reference file and use them to reconstruct the damaged file's metadata more accurately.

You should consider using a reference file when:

• The corrupted file was recorded on a GoPro, drone, dashcam, or other dedicated recording device
• The standard repair produces a file that plays but has audio/video sync issues
• The repair process reports that it could not determine codec parameters automatically
• You have other recordings from the same session or the same device

How to Choose a Good Reference File#

The ideal reference file should match the corrupted file as closely as possible:

• Same device: A video from the same camera, phone, or recorder
• Same settings: Matching resolution, frame rate, and quality settings
• Same format: If the corrupted file is MP4, the reference should also be MP4

The reference file does not need to be from the same recording session, but it should be from the same device with the same configuration. For example, if your GoPro was set to 4K at 60fps when the corrupted file was recorded, use another 4K 60fps clip from that same GoPro. If you are working with iPhone footage, the same principle applies — use a clip recorded with the same iPhone model and camera settings. For dashcam footage, use a healthy clip from the same camera and driving mode so the codec and bitrate profile match.

Using a Reference File in VideoRepair#

After uploading your corrupted file, you will see an option to add a reference file. Upload the healthy video, and VideoRepair will extract the necessary codec parameters before performing the repair. This two-file approach significantly improves repair success rates for files where the metadata is completely missing.

Prevention Tips#

While knowing how to fix a corrupted video file is valuable, preventing corruption in the first place is even better:

• Keep devices charged: Most recording corruption happens when batteries die mid-recording
• Use reliable storage: Invest in quality SD cards from reputable brands and replace them periodically
• Eject drives properly: Always use "Safely Remove Hardware" on Windows or "Eject" on macOS before unplugging external drives
• Avoid filling storage completely: Leave at least 10-15% free space on your recording media
• Back up promptly: Copy recordings to a second location as soon as possible after shooting

---

Device-Specific Cases Worth Checking#

If you already know where the file came from, these are the most common real-world patterns:

GoPro and Other Action Cameras#

The last clip often breaks after battery loss, overheating, or a sudden shutdown. These files may still have a realistic size but fail in every player because the recording never finished writing its metadata. Start with our GoPro repair guide if that sounds familiar.

Dashcams#

Dashcam failures often show up as "every file works except the one I actually needed." The most common patterns are the last clip missing after ignition-off, files that play only on the dashcam itself, and cards wearing out after heavy loop recording. If that matches your case, start with our focused guide to a dashcam file that won't play, then use the broader dashcam repair guide if you need more context.

DJI Drones and DJI Action Cameras#

With DJI footage, there are two common branches:

• the file is actually damaged because recording stopped during a crash or forced shutdown
• the file is intact, but the playback problem comes from codec support, proxy playback, or how the footage was transferred

If the file has a believable size but will not open anywhere, treat it as a repair case. If it only fails on one machine, rule out codec support first. If the recording became unreadable right after an impact or emergency shutdown, use our dedicated DJI crash recovery guide.

iPhone and Camera Transfers#

Some iPhone and camera files fail only after import or transfer. Before assuming corruption, check whether the recording finished processing on the source device and whether the copied file truly matches the original. If the source file works but the copied one does not, you may be dealing with transfer damage rather than recording-time corruption.