Media verification
Media result receipts: compare a new output without calling it certified
A media receipt turns a completed local file operation into inspectable facts: source relationship, output name, duration, dimensions or audio properties, codec observations, bytes, and visible warnings. It is evidence of the local operation, not a certification of every downstream use.
On this page
A useful receipt answers the questions that change decisions
For video, output duration, pixel dimensions, container, observed streams, and byte count can help explain whether a compression or crop hit the intended technical target. For audio, duration, channels, sample rate, output format, and bytes matter. The receipt should describe what the browser actually observed, not speculate about invisible properties.
Keep the source and result names distinct. A receipt that says “output.mp4 created from selected source” is more useful than a claim that a generic file was “optimized” without a baseline.
Worked example: fitting under a delivery ceiling
A 90-second 1920 × 1080 video might be re-encoded to an output measured at 18.4 MB under a 20 MB local target. That tells the reviewer that the browser measured the completed output below the selected ceiling. It does not establish whether the video is visually acceptable, whether a portal counts megabytes differently, or whether the destination accepts its codec.
The final human review should play the beginning, detail-heavy middle, and end; check audio sync; and read the destination’s current requirements. The receipt helps organize that review; it does not replace it.
| Receipt can report | Reviewer still decides | Destination still decides |
|---|---|---|
| Measured output bytes | Whether artefacts are acceptable. | Whether the upload ceiling and rounding rule accept it. |
| Duration and dimensions | Whether the narrative or crop is complete. | Whether timing and format meet current policy. |
| Observed stream information | Whether playback sounds and looks correct. | Whether its own transcode preserves the media. |
Compare the output at the right points
Compression damage can hide in motion, gradients, text, faces, quiet audio, or transition points. A first-frame thumbnail comparison is not enough. Pick representative moments that stress the content and listen through the intended playback device.
If a result is under a byte target but visibly unacceptable, reject it and change an intentional input: duration, dimensions, crop, target, source, or delivery format. Do not treat the numerical pass as a mandate to submit.
Keep the receipt narrow and truthful
A receipt should not promise upload approval, platform compatibility, originality, copyright clearance, accessibility, or a professional quality judgement. Those claims require evidence beyond browser-local file facts.
That restraint makes the receipt more valuable. It shows exactly what was measured and leaves room for the human and external reviews that follow.
Desktop tools and commands
Use a local tool