How to Identify True Audio File Formats and Codec Containers
A file extension is a hint, not a fact. Anyone can rename a file, and plenty of tools do it accidentally: audio exported as WAV and saved with an .mp3 extension, or an MP3 renamed to .wav in the hope that something would accept it. The audio inside is unchanged by any of that, which is why the extension is the last thing to trust and the first thing people believe. What identifies a file is its opening bytes. Formats begin with a signature, and those signatures are unambiguous: a RIFF header followed by WAVE marks a WAV file, fLaC marks FLAC, an ID3 block or a frame sync marks MPEG audio, an ftyp box marks an MP4 container holding M4A or AAC. This page reads those bytes and reports what it finds, which is why a renamed file is caught immediately. There is a second reading here that matters more than it appears, and it comes from a problem that runs through this whole site. When a browser decodes audio, the result always arrives at the sample rate of your sound hardware, typically 48 kHz, whatever the file was stored at. So for a tool whose entire purpose is to say what a file is, the decoded rate is the wrong number to report. WAV and FLAC both carry the true rate in a readable header, at a fixed position, and this page reads it there. For formats where it cannot be read without a full parser, the page says what it actually knows instead of presenting the playback rate as though it were the file's. That distinction is the difference between a tool that reports and a tool that guesses convincingly, and it is worth knowing that the number shown here can legitimately differ from the sample rate displayed by the converters on this site. They are describing different things: this is the file, they are the decoded audio.
How to Use the Audio369 Online Audio Format Detector (Step-by-Step)
Only the first bytes are needed for identification, though the audio is decoded as well so the rest of the reading has something to work with.
Identified from the signature at the start of the file, which cannot be changed by renaming it.
A mismatch is the finding. It explains why software has been refusing the file, or opening it and producing nonsense.
For WAV and FLAC this comes from the header, so it is the rate the file holds rather than the rate your device decoded it to.
Technical Architecture & Audio Engine Specifications
Extension against reality
| Situation | What the extension says | What this reads |
|---|---|---|
| A renamed file | ✓ Whatever somebody typed | The actual container |
| WAV saved as .mp3 | ✓ MP3 | RIFF WAVE |
| MP3 renamed to .wav | ✓ WAV | MPEG audio |
| M4A described as MP4 | ✓ Video, apparently | An MP4 container holding audio |
| A correctly named file | ✓ The truth | The same truth, confirmed |
Who Uses Audio369 Audio Format Detector? (Practical Creative Workflows)
Working out why software rejects a file
An application that refuses a file is usually right about it. Checking the real container explains the refusal in one step.
Verifying a download
Files described as lossless are often not, and reading the container is the first check, with the quality analyzer's rolloff as the second.
Sorting an inherited archive
Old collections accumulate mislabelled files. Identifying them properly is what makes the rest of the library work reliably.
Checking what another tool produced
This is exactly how you confirm that a converter wrote real AAC rather than a renamed WAV, which is a common shortcut in cheap tools.
Finding the true sample rate
When a spec demands 44.1 kHz, the number stored in the file is what matters, and this reads it from the header rather than inferring it.
Frequently Asked Questions (FAQ)
Why does the sample rate here differ from the converter pages? +
Because they report different things. This reads the rate stored in the file's header. The converters report the decoded audio, which the browser resamples to your sound hardware's rate, usually 48 kHz. Both numbers are correct about their own subject.
Why can it not read the sample rate for every format? +
Because MP3 and MP4 need real parsing to answer reliably, where WAV and FLAC keep it at a fixed position near the start. Saying so is better than reporting the playback rate as though it came from the file.
Can I fix a mislabelled file by renaming it? +
Yes, if the only problem is the extension. Renaming changes nothing about the audio, so giving it the correct extension for what it actually is will often be all it needed.
Does this tell me the bitrate? +
It estimates one from the file size and duration, which is accurate for constant bitrate files and approximate for variable ones. For a picture of what the audio has been through, the quality analyzer's rolloff is more informative.
Is this the same as checking the file properties in my operating system? +
No. Your operating system generally believes the extension. This reads the bytes, which is why it catches the cases where the two disagree.
How does magic byte detection uncover fake file extensions? +
Operating systems rely on file extensions (.mp3, .wav), but files can be mislabeled. Our detector parses initial binary signature bytes (e.g., 'RIFF' for WAV, 'ID3' or 0xFFFB for MP3, 'fLaC' for FLAC).
Can this tool differentiate between raw AAC and M4A containers? +
Yes. Raw AAC files begin with ADTS sync words (0xFFF), while M4A files begin with ISO Base Media File Format box headers ('ftypM4A'). Identifying the container prevents playback failures.
Does the format detector inspect audio files without full decoding? +
Yes. It parses container metadata headers within the first few kilobytes of the file, providing instant identification of sample rate, bit depth, channel configuration, and container type.