“This video is corrupted”: what it means

When it’s not actually corruption

Codec missing: iPhones and many Androids record HEVC (H.265) by default. Older Windows PCs, some TVs, and some editors can’t play it and report the file as corrupt. Test in VLC. If it plays, it’s a codec issue. The 0xc00d36c4 error page covers the Windows side.

File still downloading or syncing: Google Photos, iCloud and WhatsApp may show a placeholder that “won’t play” until the full file arrives. Wait, or download it properly.

Wrong app: some apps only accept certain formats. Try another player before assuming the worst.

When it really is corruption

VLC also fails, or plays only part of it. The file size is wrong for its length. Recording was interrupted. These are real corruption, and the fix depends on the cause. See how to repair corrupted video files for the full walkthrough.

What not to do

Don’t keep re-downloading over the same filename, and don’t run “repair” apps that save over the original. Don’t format the SD card if the file came from one, because a recovery tool may still find a better copy there. And don’t pay for software before you’ve seen it produce a working result.

Fastest way to know

Open the file in our repair tool. The diagnosis is free and tells you whether it’s a codec problem or real damage, and if it can be fixed you’ll see a 15-second preview first.

What the error message is telling you

Different apps word the same problem differently, and the exact message is a useful clue.

“This file isn’t playable. That might be because the file type is unsupported, the file extension is incorrect, or the file is corrupt” (Windows, error 0xc00d36c4): Windows can’t read the container. Often the index is missing, but sometimes Windows just lacks the codec. Try VLC first.

“The file isn’t compatible with QuickTime Player” (macOS): QuickTime is strict. It refuses MKV and AVI outright and refuses MP4s with minor index errors. Try VLC or IINA before assuming damage.

“Can’t play video” or “Video cannot be played” (Android gallery): usually an interrupted recording with no index, or a format the gallery doesn’t support.

“An error occurred while loading a higher quality version of this video” (iPhone Photos): typically an iCloud sync issue, not corruption. The full-quality original hasn’t downloaded yet. Check your connection and storage.

“moov atom not found” (FFmpeg, VLC logs, editors): the index is missing. This needs a rebuild.

“0xc10100be” (Windows): unsupported codec or a damaged container. Try another player, then repair.

Why videos become corrupted

Video files are written in a particular order. The camera streams video and audio data to storage as it records, and when you press stop it writes a summary at the end describing everything it just recorded. Players need that summary to make sense of the file.

Anything that stops the camera before it writes the summary leaves a corrupted file: dead batteries, full storage, an overheating shutdown, an app crash, a dropped phone, pulling a memory card out too early. That is why so many corrupted videos are the last clip on a card, or the one recorded when something went wrong.

The other big cause is copying. A transfer that stops partway through, from a card, a phone, a cloud service, or a chat app, leaves a copy missing its end. Since the summary is usually at the end, the copy won’t play even though the original might.

First steps when a video is corrupted

Don’t panic and don’t start deleting. Make a copy of the file onto a different drive. All repair attempts should use the copy.

Find out whether the original still exists somewhere. Check the camera card, the phone, the cloud, the sender. If the original plays, you don’t have a corrupted video; you have a bad copy.

Look at the file size. A size in line with the recording length means the data is probably all there. A tiny or zero size means most of the video wasn’t saved.

Try VLC. If it plays, the video is fine and you need a different player or a quick conversion. If it doesn’t, the file needs a repair.

Repairing a corrupted video

For most corrupted videos, repair means rebuilding the missing summary from the video data. It is a lossless process: the video itself isn’t re-encoded, so quality stays exactly the same.

Free tools can do this if you’re comfortable with a command line; our guides on fixing corrupted MP4 files and fixing corrupted video in other formats walk through them.

The faster route is the repair page. Open the video there, see a free 15-second preview of the repaired version, and unlock the full file for $9/month or $29/year if it’s what you need.

When a video is only partly corrupted

Some videos play but stop early, skip, freeze, or show blocky colours. These are partial corruptions. Stopping early usually means the summary only covers part of the data, and a rebuild recovers the rest. Freezing and blocky colours usually mean some of the video data itself was damaged, typically by a failing memory card.

Damaged data can’t be restored, but it can be worked around. Cut out the bad section, or re-export the video so the player smooths over it. Then replace the memory card, because a card that damaged one video will likely damage others.

Corrupted videos on social media and messaging apps

If a video won’t upload to Instagram, TikTok, YouTube, or WhatsApp, it isn’t always corrupted. These services reject files with unusual formats, very high frame rates, HDR, or sizes over their limits.

A quick test is to play the file in VLC and check its properties. If it plays and the codec is H.264 or HEVC, the issue is the platform’s requirements, and converting to a standard 1080p H.264 MP4 fixes it. If VLC can’t play it either, repair it first.

Videos received through messaging apps are compressed copies. If one arrives broken, ask the sender to resend it, ideally as a document or through a cloud link, which preserves the original.

Making sure it doesn’t happen again

Charge batteries before long recordings, and stop recording before you switch a camera off. Keep enough free space on phones to finish a recording comfortably. Eject cards properly from computers, and only remove them from cameras when the activity light is off.

Copy footage off devices soon after recording and keep at least two copies. Replace memory cards that have produced corrupted files, even if they seem to work now.

For screen recording and streaming software, choose a crash-safe format such as MKV or fragmented MP4, and convert to standard MP4 afterwards.

Is the video corrupted, or is the player the problem?

A large share of “corrupted” videos are healthy files the current app can’t play. Ruling that out first saves time and avoids running repairs on files that don’t need them.

Try VLC on the same computer. VLC carries its own decoders and plays almost every format. If it plays the video smoothly, the file is fine.

Check the codec. In VLC, open Tools, Codec Information. HEVC, AV1, VP9, and ProRes are common reasons for other players to fail. Installing codecs or converting the video solves those cases.

Check HDR. Videos recorded in HDR on recent iPhones and Android phones can look washed out or dark on non-HDR screens and in some editors. That is a display issue, not corruption.

Check the frame rate. Slow-motion clips at 120 or 240 fps play oddly in some players and fail on some TVs and websites. Again, not corruption.

Corrupted videos from specific apps

WhatsApp, Telegram, and Messenger: videos are re-compressed on sending. A broken received video is usually an incomplete download. Delete it from the chat and download again, or ask the sender to resend as a document.

Google Photos and iCloud Photos: broken playback is usually a sync or download issue. Check that the original has finished uploading from the source device and downloading to yours.

Snapchat and Instagram drafts: drafts are stored in app-specific formats. Saved exports to your camera roll are normal MP4s and can be repaired if broken.

Zoom and Teams recordings: an interrupted conversion leaves files that need the app’s own converter to finish. Zoom’s double_click_to_convert files are the classic example.

OBS and other screen recorders: a crash during MP4 recording loses the index. Rebuild it, and switch to MKV or hybrid MP4 for future recordings.

What happens during a repair

Repair tools don’t magically re-create video. They read what is in the file and rebuild the parts that tell players how to use it. For the common case of a missing index, the process looks like this:

The tool reads the start of the file to identify the format and codec, or takes that information from a reference clip. It then scans the raw data from beginning to end, recognising each compressed video frame by its structure and each audio packet by its position. It records each frame’s position, size, and timing, marks which frames are keyframes, and writes a new index. Finally, it writes a new file containing the original data plus the new index.

Because the video data is copied as-is, quality is unchanged. The whole process usually takes seconds to a few minutes depending on file size.

What to do if repair doesn’t work

Try another copy. If the video exists in several places (card, phone, cloud), each copy may be damaged differently. The original on the recording device is usually the best.

Try a reference clip. Record a short new video on the same device with the same settings and use it to guide the repair.

Try recovering from the storage. If the video was on a memory card, recovery tools may find a more complete version than the file you have.

Accept a partial result. Sometimes only part of a video survives. A partial clip of an important moment is still worth keeping.

The repair page shows a free 15-second preview, so you can see whether a repair works before paying $9/month or $29/year. See also how to uncorrupt a video file.

Corrupted video on a TV, console, or streaming stick

TVs and media players are much stricter than computers. A file that plays perfectly in VLC may show “unsupported file” or “corrupted” on a Samsung or LG TV, a PlayStation, or a Fire TV stick. Typical reasons are 10-bit HEVC, HDR metadata the TV doesn’t accept, high frame rates, very high bitrates, or an index at the end of the file when the TV streams from USB.

Fixes in order of effort: remux with -movflags +faststart so the index sits at the start; convert to 8-bit H.264 at 1080p if the TV is older; use a media server such as Plex or Jellyfin that converts on the fly. None of these involve repair, because the file isn’t corrupted.

Corrupted video in Premiere, Resolve, or Final Cut

Editors report “file is damaged or unsupported”, “media offline”, or “unsupported format” for files that are merely unusual. Variable frame rate phone footage, HEVC 10-bit, and MKV containers are common triggers. Test the file in VLC first.

If VLC plays it, remux to MP4 or transcode to an editing codec such as ProRes or DNxHR. If VLC also fails, repair the file, then import the repaired version and relink.

Editors also cache conformed audio and thumbnails. If a repaired file still behaves strangely, clear the media cache so the editor reads the new file from scratch.

How quickly you should act

The file itself won’t get worse, but the storage it lives on might. If the video is on a memory card or a phone close to full, copy it off today. Once you have a safe copy, there is no hurry. A careful repair next week beats a rushed one now.

For more help, see fix a corrupted video and corrupted MP4 files, or open the repair page for a free 15-second preview ($9/month or $29/year to unlock).

First steps the moment you notice

When a video turns out to be corrupted, the first few minutes matter. Stop recording on that device so new footage does not overwrite anything. Do not format the card, even if the camera suggests it. Copy the file, and ideally the entire card, to a computer or cloud drive. Then try opening the copy in VLC to see how much of it is readable.

Taking these steps before experimenting with fixes keeps every option open. Most failed recoveries are caused not by the original damage but by a later action, such as formatting, saving over the file, or running a tool that modified the only copy.