how-to · 6 min read
Why won't my video play?
Most videos that will not play are not damaged. The file is usually fine, but the player lacks a decoder for the video or audio stream inside it, or it does not understand the container at all.
Diagnose in order: find out what is actually inside the file, identify where it has to play, then test a second player. That sequence separates a compatibility problem from a corrupt download before you convert anything.
The extension names the container, not the codec
An extension such as MP4, MOV, MKV, WebM or AVI describes the container: the envelope that stores the tracks, their timing and an index of where the media data lives. The codec is the compression method used inside a track, for example H.264, HEVC, VP9 or AV1 for video and AAC, AC-3, Opus or MP3 for audio. A player has to understand the container and have decoders for each track, and it only takes one unsupported track to produce an error.
This is why a message like unsupported MP4 can be misleading, and why renaming a file changes nothing. You can read the real contents with a media-info utility, or from a terminal with ffmpeg -i file.mp4, which prints the container, the codecs, the resolution, the bit depth and the colour information. That output turns a vague playback failure into a specific mismatch you can act on.
The mismatches that cause most failures
The common case is a modern phone recording in HEVC, sometimes at 10-bit with HDR. The phone plays it, Apple devices play it, and then a Windows PC without the HEVC extension, an older Android app or a five-year-old television refuses. A second family of failures comes from Matroska files produced by screen recorders and download tools: desktop players are comfortable with MKV, while many phones, TVs and social upload forms do not index it at all.
Apple MOV files hit a similar wall outside the Apple ecosystem, especially when they contain ProRes or 10-bit HEVC. WebM is the mirror image: browsers handle it well, televisions and editors often do not. Audio can also be the blocker, because a video with a DTS or AC-3 soundtrack may open and then stay silent on a device that only decodes AAC.
- The file is MOV or MKV and it needs to play on a TV, a games console or a Windows PC.
- The video came from an iPhone and was recorded in HEVC, HDR or 10-bit colour.
- It opens but has no sound, which points at an unsupported audio codec.
- Only browsers refuse it: check whether the container is one browsers accept and the codec is widely supported.
- Every player refuses it, which suggests the file itself is incomplete or broken.
Where you are playing it changes the answer
Browsers have the narrowest rules. They support a small set of containers and codecs, do not open MKV, and support HEVC only on some platforms. For progressive playback they also want the index at the front of the file, so a large MP4 whose index sits at the end can stall in a browser even though it opens instantly from disk. Protected streams add digital rights management on top; a DRM-protected file cannot be converted or played outside its authorised app.
Televisions, consoles and car head units are a lottery of built-in decoders, so a file that works on one model can fail on the next. Social platforms and messaging apps usually accept MP4 with H.264 and AAC and re-encode it themselves, then reject other containers during upload. Knowing the destination is half the diagnosis: the same file can be perfectly correct and still be the wrong format for where it is going.
When the file itself is the problem
A download that stopped early is the classic case. MP4 and MOV files keep their index in a box called moov, which some writers place at the end of the file; when the transfer never finished, the index is missing and players report invalid data or simply show nothing. A file that is smaller than the source, or that fails in every player rather than in one, is a strong candidate for an incomplete or corrupted transfer.
Before blaming the file, test it in a second and third player, compare its size with the original source, and make sure it is not a cloud-storage placeholder that has not been downloaded yet. Re-downloading to a local folder fixes many of these cases. If a fresh copy from the source also fails everywhere, the file was broken when it was created, and conversion is not a reliable repair.
- Play it in two different players before concluding anything.
- Compare the file size with the source and look for an interrupted download.
- Move it out of a cloud-sync folder so the whole file is present locally.
- Open a known-good video in the same player to confirm the player itself works.
What conversion can fix, and what it cannot
There are two kinds of conversion. A remux copies the existing streams into a different container: fast, lossless, and useful when only the envelope is wrong. A transcode decodes the video and audio and encodes them again, which is slower and lossy but can change the codec, bit depth and resolution so an incompatible file becomes playable. For an unknown destination, H.264 video with AAC audio in an MP4 container is the combination with the widest support.
A conversion is a repair only when the diagnosis is compatibility. It cannot reconstruct a missing index, legalise a DRM-protected purchase or restore detail a low-bitrate source never had, and re-encoding HDR footage to standard dynamic range can noticeably change its colour. Keep the original file, convert a copy for the destination, and avoid repeated conversions of the same clip, because each lossy generation reduces quality.