Does inspecting a WAV file upload it anywhere?

No. The header is parsed in your browser from the local file. The audio data itself is not even fully read into memory — nothing leaves your device.

Can I compress or convert WAV files here?

Not yet, honestly. Audio re-encoding requires browser codecs or WASM encoders that have not shipped in CompressKit, so those operations are not offered rather than being faked.

Why would I inspect a WAV file?

Common reasons: checking whether a file is truly 48 kHz or 44.1 kHz, verifying channel count before mixing, or checking bit depth before archiving. Header facts prevent a surprising number of audio bugs.

What file types can be inspected?

PCM WAV files (.wav) with a standard RIFF header. Files without a valid RIFF signature are rejected with a clear message.

Inspect WAV files — locally, in your browser

Find out exactly what a .wav file contains before you work with it: duration, sample rate, channel count and bit depth, read from the RIFF header entirely on your device.

Open the WAV audio inspector tool Runs entirely in your browser — files never leave your device.

What this tool does

WAV files hide important details in plain sight — an unexpected sample rate or an odd channel layout is a common cause of playback and pipeline problems. This tool parses the RIFF structure in your browser and reports the file's real properties, so you know what you are working with.

This is an inspection tool on purpose: re-encoding audio requires WASM codecs that are not part of CompressKit yet, so the tool does not pretend to compress audio. What it does, it does honestly and locally.

How to inspect a WAV file without uploading it

Add the file. Drop your .wav into the home-page tool.
Inspect. The RIFF header is parsed locally and the file's properties are shown.
Act on the facts. Use the reported sample rate, channels and bit depth to decide what to do next — with no upload having taken place.

Supported operations

This list is generated from CompressKit's capability registry — only implemented and tested operations appear here.

Inspect file details

Read the RIFF header: duration, sample rate, channels and bit depth.

Frequently asked questions

Does inspecting a WAV file upload it anywhere?: No. The header is parsed in your browser from the local file. The audio data itself is not even fully read into memory — nothing leaves your device.
Can I compress or convert WAV files here?: Not yet, honestly. Audio re-encoding requires browser codecs or WASM encoders that have not shipped in CompressKit, so those operations are not offered rather than being faked.
Why would I inspect a WAV file?: Common reasons: checking whether a file is truly 48 kHz or 44.1 kHz, verifying channel count before mixing, or checking bit depth before archiving. Header facts prevent a surprising number of audio bugs.
What file types can be inspected?: PCM WAV files (.wav) with a standard RIFF header. Files without a valid RIFF signature are rejected with a clear message.

Ready to try it?

The WAV audio inspector tool runs on this site with no upload step — your file is processed by your own browser and saved back to your device.

Open the WAV audio inspector tool