Loading audio tools…
Loading audio tools…
Loading audio tools…
Inspect the technical properties of any audio file — duration, sample rate, channels, and more.
Sometimes you need to know exactly what's inside an audio file before you use it — whether it meets a podcast host's sample rate requirement, whether it's mono or stereo, or whether the "high quality" file someone sent you is actually what it claims to be. This tool reads a file's technical properties directly in your browser using the Web Audio API and displays them instantly: no upload, no waiting, and nothing leaves your device. Drop in any browser-playable audio file and see its duration, sample rate, channel count, bit depth, and file size laid out clearly, so you can verify compatibility or troubleshoot a problem file in seconds.
Your audio never leaves your browser. All processing uses the Web Audio API locally.
Drop any audio or video file to inspect metadata
Metadata is read using the Web Audio API — nothing is uploaded
Upload your audio file
Click 'Choose File' or drag and drop your audio file onto the upload area.
Metadata appears instantly
As soon as the file loads, the tool reads its properties and displays them — no button press needed.
Review all properties
Examine the duration, sample rate, number of channels, bit depth, and file size displayed in the results panel.
When your browser loads an audio file, the Web Audio API decodes the compressed or raw waveform data into an AudioBuffer, exposing a set of technical properties along the way: total duration, sample rate, number of channels, and the underlying bit depth of the source. This tool reads exactly those properties and presents them in plain language. It's important to distinguish this from text metadata like ID3 tags — the artist name, album title, or track number embedded in a file's header. This tool doesn't touch those tags at all; it's purely reading the technical characteristics of the audio signal itself, not the descriptive labels attached to it.
Sample rate and bit depth are the two properties people check most often, and for good reason — they define the technical ceiling of a file's quality. Sample rate is how many times per second the waveform was measured; 44,100 Hz (CD quality) and 48,000 Hz (the broadcast and video-production standard) are the two most common values, while 22,050 Hz or 8,000 Hz usually signal an already compressed or telephony-grade source. Bit depth determines how finely each of those samples is measured — 16-bit is standard for consumer audio, 24-bit is common in professional recording and mastering because it captures more dynamic range and headroom before clipping. Checking these numbers tells you immediately whether a file genuinely matches the quality it claims, or whether it was upsampled from something lower — a file created by simply raising its sample rate reports the higher number without gaining any real detail back.
This tool is especially useful as a diagnostic step before or after using other audio tools on this site. If you've just run a file through the Compress Audio tool, you can check here to confirm the sample rate actually dropped as expected. If someone sends you a file claiming to be "studio quality," checking its bit depth and sample rate here takes seconds and tells you the truth. It's also useful for troubleshooting: a file that fails to decode, or that reports zero channels or an implausible duration, is a strong sign the file is corrupted or was exported incorrectly.
Unlike most online tools, Toolivon processes everything directly in your browser using the Web APIs built into Chrome, Firefox, Safari, and Edge.
Last updated:
Your audio files never leave your device
All processing runs directly in your browser using built-in Web APIs — the Canvas API, Web Audio API, and WebAssembly. Nothing is uploaded to any server. There is no account, no email, and no data retention. You can verify this yourself: open your browser's DevTools Network tab and watch zero outbound file requests while the tool processes your audio files.
GDPR-friendly · Works offline after page load · No file size limits beyond your device memory