Audio Metadata Viewer — free online tool
Audio Metadata Viewer inspects an MP3, WAV or AAC file and reports its technical properties: duration, container format, overall bitrate, audio codec, channel count and sample rate. It never modifies the file. Use it to learn what you have before converting, compressing or submitting audio to a service with specific requirements.
Drop a MP3, WAV, AAC file here, or click to choose one
Processed temporarily, deleted afterDrop a MP3, WAV, AAC file here, or click to choose one
MP3, WAV, AAC
How it works
How the report is produced
The tool runs ffprobe on your upload and reads the audio stream header and container information. It does not play or decode the sound, which makes the process quick regardless of file length. The result summarises codec, sample rate, channels, bitrate and duration, and the upload is deleted after the report is made. Because your file is only read, you can check as many files as you like safely.
Using it
Upload an MP3, WAV or AAC file and wait a moment for the report. Note the values that matter for your task. For example, a transcription service might ask for mono audio at 16 kHz, a streaming platform might require 44.1 kHz stereo, and a voice system might need 8 kHz WAV. Comparing these numbers with the requirements tells you if conversion is needed.
Understanding sample rate and channels
Sample rate is how many measurements per second the audio contains. 44.1 kHz is the CD standard, 48 kHz is the video and broadcast standard, 22.05 or 16 kHz is common for voice, and 8 kHz is telephone quality. Channels show mono (1) or stereo (2). A stereo speech recording at 128 kbps is often twice as large as it needs to be, because speech is typically mono.
Reading bitrate and codec
For MP3 and AAC, bitrate shows how heavily compressed the file is: 64 kbps is voice quality, 128 kbps is standard, 256 to 320 kbps is high quality. A constant bitrate stays steady while variable bitrate fluctuates, so the displayed figure may be an average. WAV bitrate reflects raw data, with CD-quality at 1,411 kbps. The codec field distinguishes, for example, PCM in WAV from MP3 or AAC.
Use cases
Podcasters verifying that an episode meets a host's technical guidelines. Musicians checking whether a bounce has the expected sample rate. Archivists cataloguing a folder of recordings. Developers debugging why an app rejects a file. Teachers confirming that audio they plan to embed in slides is a supported format. Checking before converting avoids pointless re-encoding of material that already complies.
Limits of the report
The report describes the stream, not the sound quality. A 320 kbps MP3 can still be made from a poor source, and a high sample rate does not prove high fidelity. Embedded tags such as ID3 artist and title may or may not be shown. A file with the wrong extension, or a damaged header, might yield partial information or an error rather than a complete report.
Limitations
The tool reports stream properties only and cannot judge audible quality, edit tags or repair damaged files. Some tag fields may not appear. Inputs are MP3, WAV and AAC, and uploads are capped in size.
Frequently asked questions
Does this tool alter my audio file?
No. It reads header and stream information only and does not change the file. The upload is deleted once the report is generated.
What sample rate should my audio have?
44.1 kHz is standard for music and 48 kHz for video. Speech services often accept 16 kHz mono. Check the requirements of whatever platform you are submitting to.
Why does an MP3 show a bitrate that differs from what I set?
If the file uses variable bitrate, the figure is an average across the file. The instantaneous rate rises and falls with the complexity of the sound.
Can it tell me if audio is high quality?
Only indirectly. High bitrate and sample rate suggest more capacity for quality, but a file converted from a poor source remains poor. Your ears and the source history matter more.
Will it show title, artist and album tags?
If the container exposes such tags, they may appear, but the tool focuses on technical properties. A dedicated tag editor is better for editing them.
Why do I get an error for a renamed file?
If the actual format does not match the extension, or the file is damaged, the report may be incomplete. Re-export the file in its proper format and try again.