How to use Media Container and Codec Inspector
- Choose one bounded supported media file.
- Read the declared container, tracks and metadata warnings.
- Save the JSON report and test playback separately in the player you intend to use.
Example: Media Container and Codec Inspector
Read the header of a known WAV.
Supported inputs and limits
- Reads declared MP4/MOV-family, WebM or RIFF WAVE/AVI metadata up to 24 MiB and 4,000 parsed elements.
- Metadata can be missing or inaccurate and does not prove that a phone, editor or browser will play the file.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A codec identifier is a declaration
A header can name a codec that your browser or another player cannot decode. It can also be inconsistent with the contained samples. This report does not certify file safety, authenticity, complete structure or successful playback.
Absent metadata stays absent
Some files omit duration or useful track fields, and fragmented files may need sample timing to establish a full timeline. The inspector reports missing or uninspected details rather than inventing a duration. Keep the warnings beside exported metadata when sharing the report.
Questions about Media Container and Codec Inspector
Does this inspect whether a file is safe?
No. It reads a supported metadata subset without establishing safety or authenticity.
Why might duration be missing?
Some containers omit a useful declared duration, and this inspector does not reconstruct every sample or fragment timeline.
Is my input uploaded?
Nothing is uploaded.