Free tool · No sign-up · Nothing uploaded
AI music export inspector
Check a finished song export before you spend a credit, a mastering session or a distribution slot on it. Drop the file in and read what it actually contains: rate, depth, peaks, loudness, mono behaviour and whether a lossless wrapper is hiding lossy audio.
Last updated .
Runs on your device
Drop a song export here
WAV, FLAC, AIFF, MP3 or M4A up to 150.00 MB. The audio is decoded in this browser tab. It is never uploaded, stored or sent anywhere.
Most problems people try to fix with processing are already visible in the file. A truncated ending, a master pinned against full scale, a mono-incompatible stereo field or a 128 kbps MP3 renamed as a WAV will all survive any amount of later treatment.
This inspector exists to make that visible in a few seconds, for free, before you commit to the next step. It reports measurements and states plainly where a number is an estimate.
What the inspector measures
Container, codec and bit depth
The header is read directly, so a WAV that is really a re-wrapped MP3 does not get to hide behind a lossless file extension.
Sample peak and estimated true peak
Sample peak shows the highest stored value. The interpolated true-peak estimate shows where inter-sample peaks may push a lossy encoder into distortion.
Clipped runs
Consecutive samples pinned at full scale are counted. Flattened peaks are a source problem, not something a later processing pass should be asked to rebuild.
Integrated loudness
Loudness is measured with the ITU-R BS.1770 K-weighted gated method so you can compare two versions at matched level instead of judging the louder file as the better one.
Mono compatibility and DC offset
Channel correlation shows whether parts of the mix cancel on a single speaker, and a constant offset that wastes headroom is reported separately.
Frequency ceiling
An averaged spectrum across the whole song reveals a hard ceiling well below Nyquist, the usual fingerprint of lossy encoding somewhere upstream.
How to read the score
The score is a simple summary of the checks below it, not a quality rating of your music. A song can be excellent and still score poorly because its export was handled badly, and a dull track can score 100. Always read the individual checks rather than the number alone.
- Looks ready. No blocking problems were found. Continue with your normal workflow.
- Worth reviewing. Something deserves a second look, usually headroom, loudness or edges.
- Fix at the source. Clipping, truncation or a lossy rewrap should be corrected upstream first.
Why export quality matters before anything else
Every later stage inherits the file you start with. Lossy encoding discards detail permanently, so a re-wrapped download cannot regain it. Peaks already flattened against the ceiling cannot be un-flattened. A cancelled stereo field will still collapse on a phone speaker after mastering.
Checking first also makes comparison honest. Once you know the loudness of both files, you can match levels and judge whether a change actually improved the sound, which is the core habit described in the guide to humanizing AI-generated music. If the inspector flags artefacts, the artifact diagnosis guide covers what each symptom usually means.
What this tool cannot tell you
- It cannot tell whether a recording was made by a person or a model.
- It cannot guarantee detector results, distributor approval or platform acceptance.
- True peak is an interpolated estimate, not a certified meter reading.
- The frequency ceiling is a heuristic. Sparse arrangements can look bandwidth limited without any lossy history.
- It does not judge composition, performance or mix decisions. Those remain yours.
After the inspection
If the export is clean and you still hear unwanted synthetic texture, that is where Omega fits. Uploading is free, one full-length render uses one paid credit, there is no subscription, and the finished WAV is yours to release through any distributor.
Check supported exports, read the FAQ and limitations, or open the Studio when your complete song is ready.
Questions about the inspector
Is the Export Inspector really free, and do I need an account?
Yes, it is free and no account is required. The inspector is a public tool, separate from the paid Omega render workflow.
Does my song get uploaded anywhere?
No. The file is decoded and measured inside your own browser tab using the Web Audio API. It is not uploaded to a server, not stored and not shared.
Which formats can it inspect?
WAV, FLAC, AIFF, MP3 and M4A exports up to 150 MB work in current browsers. Bit depth is reported when the container declares it, which lossy formats do not.
Can it tell whether a song was made with AI?
No. It measures audio properties of the file you provide. It does not detect how a recording was made and it cannot predict any distributor or platform decision.
Why does a WAV file get flagged for a low frequency ceiling?
Because converting a lossy download to WAV changes the wrapper, not the missing detail. When lossless packaging contains bandwidth-limited audio, the original was probably compressed. Re-export from the source instead.