Can ffprobe detect all types of MOV file corruption?

No. ffprobe checks the container structure but does not decode the video data. It can detect a broken container, but it may miss corruption in the video or audio streams. Use ffmpeg with the -v error flag for a full decode check.

What does it mean if ffmpeg shows no output after the full decode?

It means FFmpeg decoded the entire file without encountering any errors. The file is likely playable and free of corruption.

How do I check multiple MOV files at once without typing each filename?

Use a batch loop. On Windows, run 'for %i in (*.mov) do ffmpeg -v error -i "%i" -f null - 2>> errors.txt'. On macOS or Linux, run 'for file in *.mov; do ffmpeg -v error -i "$file" -f null - 2>> errors.txt; done'.

Is there a graphical tool that can check MOV files for errors?

Yes, MediaInfo is a free graphical alternative that shows container and codec details. However, it does not perform a full decode check like ffmpeg does.

Check a MOV File for Errors With FFmpeg and ffprobe

FFmpeg and ffprobe, two free tools that run on Windows, macOS, and Linux, confirm and locate damage in a MOV file before you attempt any repair. Use ffprobe to inspect the container and ffmpeg to decode the file. You will detect corrupted video and know exactly where problems begin. You can also batch-check a folder of clips with a single command.

Why Check a MOV File for Errors First

Know whether the file is actually damaged and where the damage is before you repair anything. Running a diagnostic with FFmpeg or ffprobe saves time and avoids unnecessary repairs. The tools are free, command-line based, and work on all major operating systems. Prefer a graphical alternative? MediaInfo is a free option that shows container and codec details.

Quick File Inspection with Ffprobe

The fastest way to check a MOV file for errors is to use ffprobe. Run this command in your terminal:

ffprobe file.mov

ffprobe prints the container format, duration, and each stream (video, audio, data). If the command fails or shows an error, the container itself is broken. A successful output does not guarantee the video is fully playable, but it confirms the file structure is readable.

For a more detailed check, add the -v error flag to suppress informational messages and show only errors:

ffprobe -v error file.mov

No output means the container is intact. Any error messages point to structural problems.

Full Decode Check with Ffmpeg

To verify video file integrity beyond the container level, use ffmpeg to decode the entire file without creating an output. The command is:

ffmpeg -v error -i file.mov -f null -

This command does the following:

-v error makes FFmpeg print only error messages.
-i file.mov specifies the input file.
-f null - sends the decoded output to nowhere, so no new file is created.

FFmpeg processes every frame. A clean file produces no output. Errors appear in the terminal. This method detects corrupted video data that ffprobe might miss.

Locating Damage by Timestamp

When ffmpeg reports errors, it includes a timestamp showing where the problem occurs. An error might appear near a specific timecode. That tells you where damage begins. Use that timestamp to decide whether to repair only that section or to trim the file.

To get more detail about the error location, run the same command and redirect the output to a text file:

ffmpeg -v error -i file.mov -f null - 2> errors.txt

Open errors.txt to see every error with its timestamp. This makes it easier to assess the severity of the corruption.

Batch-Checking a Folder of MOV Files

If you have many MOV files to check, batch-check them with a simple loop. The exact syntax depends on your operating system, but the logic works the same.

Windows Command Prompt

for %i in (*.mov) do ffmpeg -v error -i "%i" -f null - 2>> batch_errors.txt

This command runs ffmpeg on every .mov file in the current folder and appends all errors to a single text file.

macOS and Linux Bash

for file in *.mov; do ffmpeg -v error -i "$file" -f null - 2>> batch_errors.txt; done

After the loop finishes, open batch_errors.txt to see which files have errors and where the damage starts. Files that produced no output are clean.

Understanding the Results

After running the checks, you will have one of these outcomes:

No output from ffprobe or ffmpeg. The file is clean and can be used as is.
ffprobe fails. The container is broken. Repair may require rebuilding the file structure.
ffmpeg prints errors with timestamps. The video data is corrupted at those points. Attempt to repair or cut the damaged section.

MediaInfo can show container and codec details, but it does not perform a full decode check. For a thorough check, ffmpeg is the reliable option.

Next Steps After Detection

Once you know where the damage is, decide how to proceed. If the corruption is minor, re-encode the file from the point of damage. If the file is heavily damaged, use a dedicated repair tool. Mov.repair recovers corrupted MOV files online for free, without a watermark.