When a converted video won't play, the cause is almost always one of four things: the device does not support the codec inside the file, the codec and container combination is unusual, the encoding settings (profile, level, bit depth or pixel format) are beyond what the player can decode, or the file was not finished properly. Checking the file's media information usually tells you which one within a minute.
This guide walks through how to diagnose the problem, the specific settings that most often break playback on TVs, phones, browsers and editors, and how to re-encode for maximum compatibility.
First, gather the facts
Before changing settings, answer three questions:
- Does it play anywhere? Try VLC or mpv on a PC. Both can play almost any valid file. If it fails there too, the file itself is probably damaged or incomplete.
- What exactly happens? No picture but sound, sound but no picture, an error message, a green or garbled image, or the file not appearing at all each point in different directions.
- What is in the file? Use a media info tool or run
ffprobe -hide_banner input.mp4to see the container, video codec, profile, pixel format, resolution and audio codec.
Common causes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Won't play anywhere, or stops partway | Encode interrupted or file truncated | Re-encode; check disk space and logs |
| Sound but black screen | Video codec not supported (often HEVC or AV1) | Re-encode to H.264, or install a decoder |
| Picture but no sound | Audio codec not supported (AC-3, DTS, Opus, FLAC in MP4) | Convert audio to AAC |
| Plays on PC, not on TV or phone | Profile, level, 10-bit or 4:2:2/4:4:4 too advanced | 8-bit 4:2:0, High profile, sensible level |
| Won't play in a web browser | Unsupported codec/container for that browser | H.264 + AAC in MP4, or VP9/AV1 + Opus in WebM |
| Washed-out or odd colours | HDR tags, wrong colour range or matrix | Tone map or tag colour correctly |
| Editor refuses to import | Long-GOP or VFR footage, unusual container | Convert to ProRes or DNxHR, constant frame rate |
Cause 1: the codec is not supported
The file extension does not tell you what is inside. An .mp4 can contain H.264, H.265, AV1 or MPEG-4 Part 2 video. Our guide to codecs and containers explains why this matters.
H.265 (HEVC) is the most common culprit. On Windows, the built-in Films & TV and Media Player apps need the HEVC Video Extensions from the Microsoft Store to play it, and older TVs, browsers and devices may lack support altogether. AV1 decoding needs relatively recent hardware or software; older phones and TVs often cannot play it smoothly or at all. If you need the widest compatibility, H.264 remains the safe choice - see H.264 vs H.265 for the trade-offs.
Audio matters too. MP4 files with AC-3, E-AC-3 or Opus audio are valid, but some players and many browsers will play the video silently. AAC is supported almost universally.
Cause 2: settings too advanced for the device
A file can use a supported codec and still be unplayable because of how it was encoded. The usual offenders are:
- Pixel format. H.264 in 4:2:2 or 4:4:4, or 10-bit H.264 (High 10 profile), is valid but most hardware decoders in TVs, phones and browsers cannot handle it. Encoding from ProRes, screen recordings or lossless sources can produce these by default if you do not specify
yuv420p. - Level. The level caps resolution, frame rate and bitrate. A 4K 60 fps H.264 file needs level 5.2, which many older devices do not support.
- Resolution and frame rate. 4K or high frame rate files may be beyond older or cheaper devices.
- Odd dimensions. Some players reject resolutions that are not multiples of 2, and some older hardware prefers multiples of 16.
A widely compatible re-encode looks like this:
ffmpeg -i input.mkv -c:v libx264 -crf 20 -profile:v high -level 4.1 -pix_fmt yuv420p -c:a aac -b:a 160k -movflags +faststart output.mp4
That produces 8-bit 4:2:0 H.264 High profile at level 4.1 (suitable for 1080p up to 30 fps) with AAC audio. The -movflags +faststart option moves the index to the start of the file so it can begin playing before it has fully downloaded - important for web pages and some streaming boxes.
Cause 3: an incomplete or damaged file
If an encode stopped because the disk filled up, the PC went to sleep or the app crashed, an MP4 file may be completely unplayable: MP4 normally writes its index (the "moov" atom) at the end, so a truncated file has no index. MKV and MPEG-TS files tolerate truncation better and usually play up to the point where they stop.
Check the output's duration against the source. If it is shorter or missing, re-encode with enough free disk space and check the log for errors. Repairing a truncated MP4 is sometimes possible with specialist tools that rebuild the index from a reference file, but re-encoding from the original is far more reliable.
Cause 4: incompatible codec and container pairings
Some combinations are technically possible but poorly supported - for example VP9 in MP4, PCM audio in MP4, or image-based subtitles in MP4. Others simply fail: MP4 cannot carry ASS or PGS subtitles, so stream copying them from MKV will cause an error or a broken file. When in doubt, MKV holds almost anything, while MP4 is the most widely playable.
Cause 5: colour and HDR problems
If the file plays but looks grey, washed out or oddly coloured, it may be HDR played on an SDR screen, or a file with the wrong colour range or matrix tags. Proper conversion needs tone mapping rather than a simple re-encode; our guide to converting HDR to SDR covers it.
Cause 6: playback is fine but sync is not
If it plays but audio and video drift apart, that is a different problem with its own causes, usually variable frame rate footage. See audio out of sync after converting.
Doing it with Movie Encoder
Movie Encoder shows full media info for every file - codec, profile, resolution, frame rate, bit depth, chroma subsampling, colour and HDR info, audio and subtitle tracks - so you can see exactly why a file is not playing. It warns about codec and container combinations that do not work, and lets you set profiles, levels, pixel format and bit depth explicitly when re-encoding for a particular device.
Encodes go to a temporary file and are only moved into place after finishing and passing a check, so a partial encode is never marked complete. Disk-space checks, clear error messages and full logs make it easier to see what went wrong if a job does fail.
Frequently asked questions
Why does my video play sound but show a black screen?
The player usually lacks a decoder for the video codec, most often HEVC or AV1. Install the decoder or re-encode to H.264.
What settings give the most compatible MP4?
H.264 High profile, 8-bit 4:2:0 (yuv420p), a level suited to the resolution, and AAC audio. Adding faststart helps it play in browsers before it has fully downloaded.
Can I repair an MP4 that stopped encoding partway?
A truncated MP4 often lacks its index and will not open. Specialist repair tools sometimes help, but re-encoding from the original is far more reliable.
