Skip to content
Utiloom

Media Metadata Inspector

Compare detected audio or video container evidence with filename and MIME claims, probe browser-visible metadata, and export a bounded JSON report.

LocalNo media retention

Reviewed July 13, 2026

Guide, examples, and validation Show

About this tool

Separate binary container evidence from browser claims and metadata availability before using a media file in a publishing or support workflow.

  • Uses file-type 22.0.1 signature evidence before browser MIME claims or filename extensions to classify supported audio and video containers.
  • Runs a cancelable 15-second browser metadata probe for duration and video dimensions, then derives aspect ratio and an explicitly labeled whole-file bitrate estimate.
  • Exports versioned JSON with signature, claim comparison, browser support, probe errors, derived values, findings, and every unsupported assurance set to false.

How to use Media Metadata

Choose one bounded audio or video file, run inspection, compare detected container evidence with the browser MIME claim and extension, then review browser metadata and scope findings before downloading JSON evidence.

When this tool is useful

  • Checking media dimensions and duration before upload.
  • Recording browser-visible metadata for a support report.

Practical tips

  • A metadata-load failure can mean the current browser lacks container or codec support; it does not by itself prove file corruption.
  • Treat whole-file bitrate as a rough inventory value, not a video or audio stream measurement.
  • Test full playback, seeking, and the actual delivery browser separately.

Examples you can test

Load an example, compare the result with the expected output, then replace it with your own input.

Inspect a short MP4

Example input

1920×1080 MP4, 30 seconds, 18 MB

Expected output

Detected container, MIME consistency, browser duration and dimensions, 16:9 aspect ratio, estimated whole-file bitrate, and JSON scope evidence

The browser probe does not expose or validate every track, codec, tag, or frame.

Validation checklist

  • Confirm the signature, extension, and MIME evidence refer to the expected container.
  • Compare duration and dimensions with a trusted player or source record.
  • Keep bitrate labeled as a whole-file estimate.
  • Test complete playback and target-device compatibility separately.

Frequently asked questions

Does this identify exact audio and video codecs?

No. It detects a supported binary container and asks the current browser to load metadata, but does not parse every track, codec profile, frame rate, channel layout, sample rate, tag, or attachment.

Are media files uploaded?

No. Signature detection, browser metadata loading, derived calculations, and report generation run locally in this browser.

Why is bitrate marked estimated?

It divides the entire file size by browser-reported duration, so the value includes container overhead and every audio, video, subtitle, and metadata stream rather than measuring one elementary stream.

Does loaded metadata prove the whole file will play?

No. loadedmetadata is a bounded browser capability result and does not prove full playback, seeking, structural validity, content safety, or support in another browser or device.

Related tools

Keep the workflow moving

Continue with tools that handle a related input, output, or validation step.

File

File Checksum Verifier

Strictly calculate and verify SHA-256 file checksums.

Local
File

ZIP File Maker

Create and verify standard ZIP archives locally.

Local
File

Audio Trim & WAV Export

Trim local audio into a verified PCM WAV.

Local
File

Folder Manifest & Integrity

Create and compare strict SHA-256 folder manifests.

Local