Turn an ffprobe JSON report into a readable delivery check. Add your expected dimensions, audio-stream count or file-size limit to identify mismatches. Your report is processed locally; no media is uploaded.
On this page
Create the report on your computer
ffprobe -v error -show_format -show_streams -of json "delivery.mp4" > "delivery-report.json"Install ffprobe from a trusted FFmpeg distribution if it is not already available. Choose the actual exported file. The JSON may contain private file paths or tags; this tool omits those fields from the downloadable summary. The original report stays in page memory until you leave or replace it. It is not saved to browser storage by this tool.
How comparisons work
- Stored width and height are compared with the first video stream that is not flagged as attached artwork. Rotation is reported separately.
- Audio stream count counts tracks, not channels. One stereo track is one stream with two channels.
- Maximum MB is decimal: one MB equals 1,000,000 bytes. A missing reported size produces an unknown comparison.
- Whole-file average Mbps is bytes × 8 ÷ duration ÷ 1,000,000. It includes all streams and container data, not just the video.
- Different average and reported frame rates produce a review warning, not a diagnosis of variable frame rate.
- Absent color tags mean not reported; they do not prove the file is SDR or HDR.
Try a deliberate failure
Load the synthetic example, enter required width 3840 and inspect it. The example stores 1920 pixels of width, so the result must show a mismatch. Change the brief to 1920 and inspect again. The example has one audio stream, 60 seconds and 77.4 MB. It is fabricated test data for checking the tool, not a real export benchmark.
What still needs human review
This tool does not decode media, measure loudness, compare the actual picture, inspect per-frame timing, verify sync, read caption meaning or guarantee destination acceptance. Watch and listen to the saved file, especially its beginning, critical sections and end. For a full procedure use the export acceptance guide.
Sources and verification
Documentation checked October 28, 2026. The worked numbers are illustrative calculations, not hardware benchmarks. Instructions describe a reproducible procedure; software labels can vary by release. How we verify and correct our work.
Build on what you just learned
Your next useful step.
Budget the size, inspect the export, keep a record.
Generative Extend: a few extra frames still need an editorial review
I would use generated extensions for a deliberate transition or timing need, then inspect the new frames and identify them in the project record.
Read the guide →
Budget video bitrate for a hard file-size limit
Allocate the total size budget across duration, audio and a stated reserve before choosing video bitrate. Then measure the actual exported bytes, especially when…
Read the guide →