Audio Tools

Audio File Info

Inspect local audio source hints, embedded tags and browser-decoded signal evidence, then compare files and export a transparent audit.

Wave162 · browser-local source + decoded-signal evidence

Audio File Inspector & Signal Audit Studio

Inspect up to 20 local audio files, separate source-container hints from browser-decoded PCM, review WAV/ID3 tags, measure signal levels, compare files, and export an evidence report without uploading audio.

local · measurable · auditable

Drop audio files hereChoose up to 20 files. Browser codec support varies; failed decodes remain visible instead of being guessed.

Near-full-scale threshold (dBFS)Silence threshold (dBFS)

Choose or drop one or more browser-decodable audio files.

1. Batch file passport

0 decoded / 0 selected

Open	File	Signature hint	Duration	Decoded rate	Ch	Est. bitrate	Peak	Crest	Near-full-scale samples
Choose audio files to build a local comparison queue.

2. Current file: source vs decoded PCM

File—

Source bytes—

Signature hint—

Duration—

Decoded rate—

Channels—

Est. file bitrate—

16-bit PCM estimate—

3. Decoded signal evidence

Sample peak—

RMS—

Crest factor—

DC offset—

Near-full-scale count—

Below silence threshold—

Stereo correlation—

Analysis coverage—

4. Waveform & bounded spectrum snapshot

Waveform overview

Middle-window FFT snapshot

Dominant bin—

Spectral centroid—

Low / mid / high energy—

5. Source-header evidence & embedded tags

WAV fmt evidence

No source parsed yet.

Supported tags

No source parsed yet.

Embedded artwork

No source parsed yet.

6. Audit, export & repeat use

Choose a file to generate a signal audit.

Local numeric history

How to read the evidence

Container hint ≠ codec certification

Magic bytes can identify common container families. Exact codec/profile metadata needs a deeper container parser when the browser does not expose it.

Decoded rate can be runtime rate

Web Audio can resample during decode. Compare RIFF/WAVE header evidence where available and use a dedicated media parser when untouched encoded-stream values matter.

Peak and RMS are not LUFS

Sample peak, RMS and crest are useful signal measurements. They are not integrated loudness, inter-sample true peak or a mastering-quality score.

Clipping is threshold-based here

The count uses your chosen near-full-scale threshold. Long files may be sampled with a stated stride to keep browser work bounded, so it is an audit signal rather than forensic proof.

Spectrum is a bounded snapshot

The graph is one Hann-windowed FFT around the middle of the decoded file. Dominant-bin and centroid values describe that window, not the entire recording.

Tag parsing is intentionally limited

The lightweight source parser reads RIFF INFO and common ID3v2 text/artwork frames. It does not claim complete MP4 atoms, Vorbis comments, every ID3 frame or forensic tag parity.

Truth boundary: Selected audio stays in this browser tab. This Studio does not claim certified codec/profile extraction for every container, LUFS or inter-sample true peak, fake-lossless detection, subjective quality scoring, repair, transcoding, DRM bypass, or professional MediaInfo/FFmpeg forensic parity. Use the dedicated loudness/frequency tools when those measurements are the actual task.

Audio processing cluster

Verify the source before trusting the render

Decode locally, confirm sample rate, channels, duration and level evidence, then apply the transformation. Keep codec, browser decode and export-format limits explicit.

Start: Audio Editor Inspect a File

All 24 audio tools

Sample RateResample rate, Nyquist and output frames Stereo → MonoDownmix, correlation and cancellation risk Speed ChangerDuration, pitch and resampling behavior Loop MakerLoop boundaries, seam and repeated duration Frequency AnalyzerFFT resolution and spectral evidence Bass BoosterLow-shelf gain and clipping headroom Audio JoinerClip order, transitions and output duration Loudness AnalyzerLUFS planning, peak and dynamics

Separate source-file evidence from decoded PCM

File bytes and header signatures describe the stored object. Web Audio measurements describe the signal the browser actually decoded, which can differ when the runtime resamples or lacks support for a format.

Estimated bitrate is not parsed codec bitrate

The Studio divides source bytes by decoded duration for an average file-rate estimate. This is useful as a sanity check but does not prove codec mode, frame bitrate, profile, encoder quality or whether a lossy source was transcoded.

Use level metrics as evidence, not a quality score

Peak, RMS, crest, DC offset, threshold-based near-full-scale count and silence proportion help diagnose signal behavior. They do not replace integrated loudness, true-peak oversampling or calibrated listening.

Header parsers are deliberately scoped

RIFF/WAVE fmt and INFO chunks plus common ID3v2 text/artwork frames are read when present. Other containers may expose only signature, MIME and decoded evidence rather than invented metadata.

Privacy and repeat use

Audio remains local. History stores numeric summaries only, and settings-only share links contain threshold settings—not audio bytes, filenames, tags, artwork or analysis history.

Practical guide and verification

Use the interactive product above first. These notes add interpretation, verification and limits below the results and product controls.

Container and codec are separate properties

A file extension such as .m4a, .mp4 or .webm identifies a container convention, while the encoded audio stream may use a separate codec. Compatibility decisions should use the decoded stream information rather than filename alone.

Bitrate does not equal audible quality by itself

Codec efficiency, source complexity, channel count and encoding mode all affect the relationship between bitrate and quality. Compare bitrate only among reasonably similar encoding conditions and keep the original file for reference.

Sample rate sets the representable frequency range

For PCM-style sampling, the Nyquist limit is half the sample rate. A 48 kHz stream cannot represent new content above roughly 24 kHz after decoding, and resampling does not recreate frequencies that were absent from the source.

Browser decoding support is a boundary

Some codecs or metadata fields may not be exposed consistently by every browser. If a professional workflow depends on exact container tags or codec profiles, verify the same file with a dedicated media inspection tool as a second source.

Use duration and stream properties as a sanity check

For uncompressed PCM, sample rate, bit depth, channel count and duration imply an approximate data size before headers. A large mismatch can reveal that the file is compressed, that a displayed value describes a different stream, or that metadata was interpreted incorrectly.