Understand your IAMF.
Get a clear report.

Check your file’s supported metadata against the IAMF specification. Review issues, evidence, and next steps — all in your browser.

Open validator

Know your file. Keep the evidence.

MP4 containers
Standalone IAMF
Local processing

Inspect your file

Choose an IAMF file or an MP4 containing IAMF audio. Get a report of the checks passed, issues found, and areas that need further validation.

01 Select your file

LOCAL PROCESSING

Drop an MP4 or IAMF file here

Inspect one file. Your original stays unchanged.

Choose a file.mp4 / .iamf · Type is identified from file contents

Check type

Check selected IAMF v1.1.0 requirements and decode supported Opus or PCM mixes with libiamf. Files up to 64 MiB receive the decode check; the report lists any remaining limits.

Loading account…

The bundled example is free. Credits are charged when analysis is authorized, including cancelled or incomplete runs. Media stays on your device.

Ready for a file

Checks cover supported IAMF metadata and a libiamf decode of Opus or PCM mixes, up to 64 MiB. The report shows remaining limits; a clear result does not establish full IAMF conformance. See all checks and limits.

Plans and credits

Use credits to inspect your files. Your administrator sets welcome credits, usage costs, and available plans.

Loading plans and credit costs…

See what the inspector can and cannot check.

Read the methodology

Inspect. Understand. Prepare your upload.

Connect the metadata in your export to the next steps in your YouTube upload workflow.

Read the upload guide

Before you inspect

What does IAMF Validator inspect?

It checks supported metadata against selected IAMF v1.1.0 requirements, then uses libiamf to decode supported Opus and PCM mixes locally. Your report separates specification findings, decoding results, and unchecked areas. YouTube recommendations are optional.

Does my file leave my device?

No. Media inspection runs locally in your browser. Your media and report stay in the current session. Exported reports omit the filename and embedded labels by default; you can choose to include them.

Will a clear report guarantee YouTube playback?

No. The inspector does not upload to YouTube, test platform ingestion, or verify device playback. Use the findings alongside the upload guide and test the published result on your intended playback devices.

Can it measure loudness or repair my audio?

No. The reference decode checks whether supported mixes can be rendered to stereo. It does not measure loudness, verify actual channel content, or repair files. If a finding needs a change, return to your source project or encoder and inspect the new export.

Why does a finding say unknown or partial?

Some structures are outside the current parser’s coverage, and a file may not contain enough evidence for a conclusion. Unknown and partial results remain visible so missing coverage is not mistaken for a successful check.

Do I need an account or a paid plan?

An email account is required to inspect your own files. Each inspection uses the credit amount shown before you start. Your administrator sets welcome credits, usage costs, and plans. Available credits can be used without a plan; contact your administrator to add credits or activate a plan. You can try the bundled example without an account.