FixMyVideos

Video Plays as Black Screen — Audio Works, No Picture

The audio plays. The duration counter advances normally. The screen shows nothing — solid black, no picture, no glitch, no error. Three categories of cause.

Cause 1: codec/colour mismatch in the player

The most common cause, especially for ProRes / 10-bit footage played in a browser or in QuickTime. Some pixel formats — yuv422p10le, yuv444p10le — aren't supported by browser <video> tags or by older versions of QuickTime. The codec can't render, so the player draws black.

ProRes files are routinely yuv422p10le in their native form. If you preview a recovered ProRes file in a browser-based video element and see a black square, that's why.

Fix: transcode to yuv420p (8-bit, browser-safe):

ffmpeg -i prores.mov -c:v libx264 -pix_fmt yuv420p -c:a copy preview.mp4

The recovered file is fine. The issue is the player you tested it in. Open it in DaVinci Resolve, Premiere, or VLC and the picture appears.

Cause 2: video stream is in the file but damaged

ffprobe shows a video stream but the codec data is unreadable. Possibilities:

  • Codec parameter set damage. The H.264 SPS / H.265 VPS / SPS is corrupted. The decoder can't initialise, so it draws black.
  • Wrong codec four-cc. The container says one codec; the data is something else. Decoder mismatch → black.
  • Frame-internal corruption. The codec data has bit-flips that prevent decoding.

For these, transcoding won't help (the source data itself is unreadable). The fix is to recover the codec parameters or codec identification.

Cause 3: the recording was actually black

Camera lens cap on. Camera in playback mode rather than record mode. Phone in pocket with screen face-down. These produce a real recording of black. The audio is fine because the microphone was working; the picture is what the lens saw.

Test by checking another recording from the same camera. If others have picture, you've got a real recovery case. If others are also black, the camera was recording black footage.

How to figure out which cause

ffprobe -v error -show_streams broken.mov

Look at the video stream's pix_fmt:

pix_fmt valueLikely cause
yuv420pShould play in browsers; if it doesn't, cause 2.
yuv422p10le, yuv444p10le, yuv420p10leCause 1 — transcode to yuv420p.
none or missingCause 2 — codec data damage.

Then try VLC. If VLC plays picture and the browser/QuickTime doesn't, cause 1. If even VLC plays black, cause 2.

For our preview pipeline specifically: every preview is forced to -pix_fmt yuv420p for browser compatibility. If you see a black preview from us, it's a real video failure (cause 2), not a pixel-format issue.

What you can try yourself

For cause 1:

ffmpeg -i source.mov -c:v libx264 -pix_fmt yuv420p preview.mp4

For cause 2:

ffmpeg -err_detect ignore_err -i broken.mov -c copy out.mov

(If FFmpeg can produce any output, the codec data is at least partly intact. If FFmpeg returns "no decodable frames found," cause 2 is severe and may be unrecoverable.)

For cause 3:

There's nothing to recover. The recording itself is black.

How our recovery handles black-screen cases

  • Codec parameter recovery from observed frames. If the SPS / VPS at the start of the file is damaged but the codec parameter set is repeated later in the stream (some codecs do, particularly H.265), we extract from a later frame.
  • Codec identification from frame markers. If the container's declared codec is wrong, we identify the actual codec from frame data and rebuild with the correct codec.
  • Preview pipeline forces yuv420p for the 5-second preview. You'll never see a "black screen because of pix_fmt" issue from our preview.
  • Honest about hard cases. If the codec data is genuinely corrupted (cause 2 severe), we tell you fast. There's no point taking your money for a file where the actual frames are unreadable.

What you do

  1. Upload the file.
  2. ~1 minute later you get a diagnostic + free preview. The diagnostic identifies whether the picture is recoverable or whether the video stream is genuinely too damaged.
  3. Pay only if the preview shows actual picture.

FAQ

My ProRes file shows black in QuickTime but plays fine in Resolve. Cause 1 — pixel format mismatch. The file is fine. QuickTime's HEVC/ProRes pipeline on older macOS doesn't render 10-bit 4:2:2 well. Update macOS or transcode for QuickTime.

My recovered file from another tool shows black screen. Could be cause 1 (their preview/output uses a non-browser-safe pixel format) or cause 2 (their recovery didn't reconstruct the codec parameters). Upload the original broken file to us; we'll attempt with proper codec handling.

Audio plays the right duration but no video at all from the start. Cause 2 severe — codec data so damaged that no frames decode. Sometimes recoverable by extracting frames from later in the file; sometimes not.

Is my footage safe? Server in France, auto-deleted after 48 hours, never used to train anything or shared. Privacy policy.

Related

Upload your file →

Free preview · No commitment

Ready to recover your video?

Upload your file — get a free 5-second preview in about a minute. Pay only if the preview looks right.

Upload your video →