Sound but No Picture: How to Fix a Video That Plays Black

Why sound can play when the picture cannot

A video file is a container holding separate streams: usually one video stream and one or more audio streams, each compressed with its own codec. A player decodes them independently. Audio codecs such as AAC are supported almost everywhere, while video codecs and their variants are far more fragmented. So a player that understands the audio but not the picture will often carry on and play sound over black rather than refuse the file. The explainer on video codecs covers the difference between codecs, profiles and containers.

Variations on the symptom carry clues:

• Black from the first frame, everywhere you try it: likely the file or the way it was recorded.
• Black in one player or browser, fine in another: likely codec support or hardware decoding.
• Black for the first few seconds, then the picture appears: likely a missing keyframe at the start.
• A first frame that freezes while audio continues: often a decoder that gave up after starting.
• Green, pink or blocky garbage instead of black: a decoding problem of the same family.

The usual causes

Unsupported codec

HEVC, AV1, VP9 or ProRes in a player or browser that lacks a decoder for it

Unsupported profile or bit depth

10-bit H.264, 4:2:2 colour or very high resolutions that a device's decoder does not handle

Hardware decoding fault

A graphics driver or decoder that fails on certain files while software decoding would work

HDR handling

HDR footage shown on a display or in an app that maps it badly, sometimes very dark rather than fully black

No keyframe at the start

A clip trimmed without re-encoding that begins mid-way through a group of frames

Damaged file

An interrupted recording or transfer that left the video data incomplete

Protected content

A screen recording of a streaming service or protected player that captured audio but a blank picture

HEVC is the most common culprit with phone footage; its particular support gaps, and the MP4 versus MOV differences, are covered in HEVC compatibility.

Diagnose in this order

1. Play the file in a second player that brings its own decoders, such as VLC or mpv. If the picture appears there, the file is fine and the first player lacks support.
2. Try a second device. A file that is black on an older laptop but fine on a newer phone points to decoder support or hardware limits.
3. Inspect the file with MediaInfo or ffprobe. Note the video codec, profile, bit depth, chroma subsampling, resolution, frame rate and any HDR information.
4. Toggle hardware acceleration. Browsers and most players have a setting to turn it off; if the picture appears with it off, the hardware decoder or its driver is at fault.
5. Skip ahead 10 or 20 seconds. If the picture appears later, the start of the file lacks a keyframe.
6. Ask how the file was made. A screen recording of a streaming service, a video call with protected content, or a recording interrupted by a crash each point to a cause that no player setting can fix.

This command prints the details that matter most in step 3:

ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,profile,pix_fmt,width,height,color_transfer input.mp4

A pix_fmt containing 10 indicates 10-bit video, and a colour transfer such as smpte2084 or arib-std-b67 indicates HDR.

Fixes for each cause

Missing decoder. Update the player, browser and operating system, or use a player with broad codec support. On some systems HEVC playback needs an additional codec package from the operating system's store. If the file must play everywhere, convert it.

Profile, bit depth or resolution beyond the device. Re-encode to the most widely supported combination: H.264, 8-bit, 4:2:0, at a resolution the target devices handle. This re-encodes the picture, so keep the original:

ffmpeg -i input.mov -c:v libx264 -pix_fmt yuv420p -crf 18 -preset slow -c:a copy output.mp4

Hardware decoding fault. Update the graphics driver first. As a workaround, turn off hardware acceleration in the browser or player, accepting higher CPU use, or re-encode to a profile the hardware handles.

HDR problems. Play HDR files in an app and on a display that support HDR, or convert to SDR in an editor with proper tone mapping. Simple conversions can look flat or wrong, so check skin tones afterwards.

Missing keyframe. Trim again with re-encoding at the start, or move the cut point to a keyframe. The guide to converting video formats explains when remuxing is enough and when re-encoding is needed.

Damaged files. Some repair tools can rebuild an interrupted MP4 or MOV using a healthy reference file recorded on the same device with the same settings. Results vary, and missing data cannot be restored.

Protected content. A blank picture in a recording of protected playback is the protection working as designed. Ask the owner for a proper copy of the video instead of trying to work around it.

A worked example: an agency file that plays black in the browser

Black screen in your own recordings

If you made the recording yourself and the picture is black everywhere, the cause is usually in the capture setup rather than playback:

• Screen recording permission. Operating systems require explicit permission for apps to record the screen; without it, some recorders capture a blank or partial picture.
• Graphics switching. On some laptops with two graphics processors, a screen recorder running on one cannot capture a window drawn by the other, and records black.
• Protected playback. Streaming services and some apps block capture, so recordings of them show black while the audio, captured separately, still works.
• Wrong capture source. A recorder set to capture an inactive display or a closed window records nothing useful.

Make a 10-second test recording after changing any setting, rather than discovering the problem after an hour-long session.

Pitfalls and limits of black-screen fixes

• Converting a file that was never broken. If VLC shows the picture, a conversion is only needed for the destination, not to repair anything.
• Re-encoding repeatedly. Each lossy re-encode loses some detail; convert once from the original.
• Expecting conversion to restore a blank recording. If the picture was never captured, no tool can bring it back.
• Flattening HDR carelessly. Quick conversions can make footage look washed out or overly contrasty.
• Treating a damaged file as a codec problem. If the file is black in every player, inspect it before buying codec packs.

What this means for mydubly

mydubly needs only the audio to transcribe or translate, so a file whose picture plays black on your laptop can still produce a transcript, subtitles or a translated voice track, as long as it is one of the accepted formats (MP4, MOV, WebM, MKV or M4V, up to 2 hours). The video picture never leaves your device; only compressed audio chunks are uploaded.

For a translated video, the browser copies the original picture packet by packet without re-encoding it and replaces the audio with the dubbed track. That keeps the picture identical, but it also means mydubly does not convert the video: a picture codec that a player cannot show will be just as black in the translated version on that player. If the codec cannot go into MP4, the output is MKV, which may not play inline in every browser even though it plays in desktop players. If a file was recorded with a blank picture, the translated video will be blank too. Convert or fix the source first if the translated video needs to play on a specific device, as covered in unsupported video files.

Next step: confirm the picture, then translate

Once the source shows its picture in the players your audience uses, run it through the video translator and check the result on the same devices. For phone footage, the MP4 to text page lists what to expect when you only need the words.