
Fix "Output File Is Empty, Nothing Was Encoded" in FFmpeg
An ffmpeg output file empty result is usually a warning, not an error: FFmpeg exits 0 with nothing encoded. Every cause, plus the ffprobe guard to catch it.
9 articles about troubleshooting.

An ffmpeg output file empty result is usually a warning, not an error: FFmpeg exits 0 with nothing encoded. Every cause, plus the ffprobe guard to catch it.

Your HEVC MP4 plays in VLC but not in Safari? The FFmpeg hvc1 tag fix is a metadata-only remux: one stream copy, done in seconds, with zero quality loss.

MP4 not playing in browser? VLC decodes almost anything, hiding the four real breakers: pixel format, H.264 profile/level, moov placement, audio codec.

FFmpeg's "Too many packets buffered for output stream" error is a stream mapping problem. Fix the cause first, then size max_muxing_queue_size without an OOM.

Non-monotonous DTS in output stream: what the warning means, when -fflags +genpts or -reset_timestamps 1 is right, and when only a CFR re-encode fixes it.

FFmpeg audio out of sync is usually a variable-frame-rate source hitting a fixed -r. Detect VFR with ffprobe, then fix it with -fps_mode cfr and aresample.

FFmpeg's "height not divisible by 2" error is a yuv420p chroma constraint, not a broken file. Three fixes (scale=-2, trunc, pad) with measured output sizes.

"moov atom not found" almost never means a corrupt video. It means a truncated upload or a Range request that missed the trailing moov box. Check and fix it.

Fix 'ffmpeg' is not recognized as an internal or external command. Diagnose ffmpeg not recognized: install check, PATH bin folder, stray spaces, restart.