Dictionary

What Does Probe Score Mean?

The probe score is a number from 0 to 100. It shows how confident FFmpeg is about the container format of a file.

probe-score

Probe score means how confident FFmpeg is about the container format of a file. FFmpeg is a multimedia framework that reads and converts audio and video files, and its program ffprobe reports the score.

The score is a whole number from 0 to 100, and a higher number means a stronger match. The score describes only the container format, such as MKV or MP4. The score does not measure the quality of the sound or picture.

Where the value comes from

The probe score is not stored in your file. FFmpeg works out the number each time it opens the file.

FFmpeg has a small detector for many formats. Each detector reads the start of the file, looks for signs of its own format, and returns a score. The format with the highest score wins.

FFmpeg begins with 2048 bytes of data. If no format scores above 25, FFmpeg doubles the amount and tries again.

The default limit is 1,048,576 bytes, or about 1 MB. On the last attempt, any score above 0 is enough.

If the input reports a MIME type that matches a format, that format gets 30 extra points, up to 100. If 2 formats tie for the highest score, FFmpeg rejects both. With no format left after the last attempt, FFmpeg stops with the error Invalid data found when processing input.

How the file extension affects the score

A high probe score does not prove that the file extension is correct. For example, the Matroska detector returns 100 for a known document type in the file header, whatever the file is called.

When a format has a detector, a matching extension usually only lifts a score of 0 to 1. A format without a detector depends on the extension, and a match gives that format a score of 50. To check a doubtful extension, compare the extension with the format name that ffprobe reports next to the score.

What the value looks like

With the -show_format option, ffprobe prints the score as one line in the format section: probe_score=100. The XML report of ffprobe carries the same number in an attribute named probe_score.

Typical values

These examples come from the FFmpeg 9.0 source code. Other versions can give other numbers, such as 51 for the MP3 example in FFmpeg 8.1.

  • 100: an MP4 or MOV file with a section named ftyp or moov
  • 100: a Matroska or WebM file with a known document type
  • 100: a FLAC file with valid stream information
  • 99: a WAV file with a standard RIFF header
  • 52: an MP3 file with at least 7 audio frames at the start
  • 51: an AAC file in ADTS form with at least 3 audio frames at the start
  • 50: a file in a format without a detector, matched only by its extension
  • 0: a file whose format was forced with the -f option, so FFmpeg skipped the detection

Why it matters for your file

A detected score of 25 or lower is a warning sign, not proof of a fault. FFmpeg then prints a message with the words misdetection possible, which means FFmpeg may have picked the wrong format.

A score near 50 is normal for MP3 and AAC files, because their detectors do not return more than 52. So a score of 51 or 52 does not mean that your MP3 file has a problem.

For a detected score of 25 or lower, the FFmpeg developer documentation recommends a retry with more data. The -formatprobesize option sets the limit for format detection in bytes. The -probesize and -analyzeduration options do a different job: they limit the data FFmpeg reads to find stream details.