Before and after
The editor shows the original peak, calculated gain, and predicted peak before export.
Measure the decoded file's highest sample, calculate one linear gain adjustment, preview it, and export from the same browser-based audio graph.
You can also drag and drop an audio or video file anywhere on this page.•Compatibility depends on the file codecs and device: MP3, WAV, M4A, AAC, FLAC, OGG, WebM, MP4, MOV, MKV, and more
This tool finds the largest absolute decoded sample and applies the same gain ratio to every channel. It is useful for setting a predictable sample-peak ceiling, but it does not measure perceived loudness.
The editor shows the original peak, calculated gain, and predicted peak before export.
One multiplier is used for every channel, preserving the relationship between left and right.
Playback and export use the same gain value in the shared processing graph.
Use the measured values as a check, not just an automatic button. The result is most useful when you know what the target represents.
Choose the recording and wait for the browser to decode every channel. The original sample peak is measured before any gain is applied.
The tool targets −1 dBFS with one multiplier for the whole file. Check the predicted peak and note when the 200% gain cap prevents the target from being reached.
Listen to quiet and loud passages, then export. If you need matched perceived loudness across several files, continue with a dedicated LUFS workflow.
Choosing the right measurement avoids treating peak normalization as a solution for every loudness problem.
The highest decoded digital sample in the file.
This is what the current normalizer measures and targets at −1 dBFS.
An estimate of peaks that can occur between samples during playback or conversion.
This tool does not calculate it; use a true-peak meter or limiter when delivery rules require dBTP.
A weighted measurement of perceived loudness over time.
Use it to match programs or episodes; a shared peak value does not guarantee equal perceived volume.
The selected audio is decoded and processed in browser memory. It is not uploaded to the application server to calculate or export the normalized result. Site resources and consented analytics may still use network requests.
Clear answers about what changes, what stays intact, and when another audio process is needed.
No. Two files can have the same sample peak and very different average energy, dynamics, and perceived loudness. LUFS matching is a separate process.
No. Lowering a clipped recording creates headroom but does not reconstruct waveform details already flattened at the recording or encoding stage.
The same linear gain is applied to all channels, so the existing level relationship between left and right is preserved.
Automatic amplification is capped at 200% for safety. A very quiet source may need more gain than that cap allows.
Guides written and reviewed by the person who builds the editor, including the real limits of each feature.
Understand integrated loudness and true peak, why this editor does not measure LUFS, and how to verify current delivery requirements externally.
14 min readLearn to set gain from 0 to 200% and normalize sample peak to -1 dBFS while distinguishing peak, LUFS, true peak and clipping.
13 min readAudio editing glossary with 40 essential terms. Learn what bitrate, normalization, clipping, EQ and compression mean — clear definitions for podcasters and content creators.
9 min read