Skip to content
saturalabs

Peak vs Loudness Normalization: How to Adjust Audio Levels

Choose peak or loudness normalization for a quiet recording. Learn dBFS, LUFS, linked stereo gain, noise limits, and how to preview a normalized WAV.

Updated

In this guide
The short version

Peak normalization sets the highest sample level with one gain adjustment. Loudness normalization uses a loudness measurement. Choose by the problem you hear, keep stereo balance deliberate, and measure the final export when a delivery specification matters.

An original listening comparison

Hear equal peaks with different integrated loudness

These two four-second synthetic tones share the same sample peak and duration. One stays steady; the other spends most of its time at a lower amplitude. They are not voices, musical performances, or AI isolation results.

Start at a comfortable playback volume and keep the player and device volumes consistent. Playback equipment affects what you hear. A LUFS difference is a measurement of these files, not a guarantee of the same perceived difference for every listener.

A steady tone

The tone keeps its level through the middle, with short fades at the outer edges.

-12.04 dBFS sample peak
-15.74 LUFS integrated

Download WAV ≈375 KiB

The same peak, with quieter intervals

Short louder pulses reach the same peak. Most of each half-second cycle stays at one quarter of that amplitude.

-12.04 dBFS sample peak
-22.65 LUFS integrated

Download WAV ≈375 KiB

Both peaks measure −12.04 dBFS, while integrated loudness differs by about 6.91 LU. Setting both to the same new peak applies the same gain to each; that alone does not make their loudness match. The quieter intervals are part of the second file's pattern, not missing audio to repair.

Download each WAV and open it separately in the free integrated LUFS meter. Measure the complete four seconds. For a sample-peak exercise, use each original in the peak normalizer with the same target, then compare their loudness again. These are separate tools, and files are not transferred automatically.

To test a loudness target, choose each original separately in the free LUFS normalizer. At a requested −16 LUFS, these two examples have enough sample-peak headroom for the adjustment. Compare the actual exported readings and their now-different sample peaks. Other recordings can be constrained by the ceiling, so use the reported output rather than assuming a requested target was reached.

Each file is mono, 48 kHz, 16-bit PCM WAV: 192,000 frames and 384,044 bytes. The 440 Hz tones have 20 ms outer fades; the pulsed version has smooth level transitions. Measurements use the shipped integer PCM. Independent FFmpeg checks agree within 0.12 LU. Read the generation and verification notes or download the measurements JSON. These original Saturalabs audio assets are dedicated to the public domain under CC0 1.0.

If a recording is quiet throughout, peak normalization can raise its level with one gain adjustment. If you need several recordings to have consistent perceived loudness, use a loudness measurement and an intentional loudness-normalization workflow. These operations answer different questions, so start by listening to the problem rather than choosing the largest number.

The free audio normalizer provides sample-peak normalization for short mono or stereo MP3/WAV files. It reports the decoded peak, lets you choose a target in dBFS, applies the same gain to both stereo channels, and exports a WAV locally. It does not measure LUFS or true peak.

What peak normalization does

Peak normalization finds the largest absolute sample value and calculates a constant multiplier to bring it to the target. Every sample receives that multiplier. The timing, channel count, and relationship between quiet and loud passages stay the same before export quantization.

For example, a peak of 0.25 relative to full scale is about −12.04 dBFS. A target of −1 dBFS corresponds to a peak of about 0.89125. Dividing the target amplitude by the measured peak gives a gain of about 3.565, or +11.04 dB. The downloaded 16-bit WAV can differ slightly because its sample values are rounded.

The dB to gain calculator converts a gain change to its linear amplitude multiplier, or reverses a positive ratio. Enter the gain difference, not the target dBFS by itself: a −1 dBFS target is not a −1 dB adjustment unless the input peak is 0 dBFS. The calculator does not measure or normalize a file.

Gain needed to move a measured sample peak to a target
Original sample peakTarget sample peakRequired gain
−18 dBFS−3 dBFS+15 dB: raise the complete clip
−6 dBFS−1 dBFS+5 dB: raise the complete clip
−1 dBFS−6 dBFS−5 dB: lower the complete clip

These are arithmetic examples, not measurements of recordings or recommended delivery standards. A target should fit the edit you are making. Increasing the level can make an already clear, quiet clip easier to place in a project; decreasing it can leave more sample headroom for a later edit.

To measure a supported short mono or stereo recording first, use the free integrated LUFS meter. It reports integrated loudness and decoded sample peak locally; it does not normalize, measure true peak, or certify a delivery.

What loudness normalization adds

A highest sample does not describe the whole listening experience. A short impact and a dense, sustained passage can have the same peak. The quiet recording around that impact may still seem much softer. Matching both files to the same sample peak leaves their different patterns intact.

Audacity’s Loudness Normalization reference distinguishes perceived-loudness measurement in LUFS from RMS measurement. Use an appropriate loudness meter when your task is to match perceived loudness or satisfy a stated loudness requirement. Sample-peak dBFS is not a substitute for a LUFS reading.

Even a loudness target does not automatically resolve every delivery issue. The final file’s peak and changing levels still matter. FFmpeg’s loudnorm documentation, for example, describes separate integrated-loudness, loudness-range, and maximum-true-peak controls. A single gain setting is not the same process.

Read the actual delivery specification instead of applying a universal “podcast” or “streaming” preset to every project. The peak normalizer offers a sample-peak target only. The separate LUFS loudness normalizer adjusts a short recording toward a chosen integrated target, constrains gain by a sample-peak ceiling, and reports the actual exported reading. It does not force a target with a limiter or establish delivery compliance. Verify the final export with tools covering your actual requirements.

When a peak adjustment is a useful starting point

Choose a level workflow from the problem in the recording
ProblemStarting workflowWhy
The complete clip is quiet, with peaks well below the desired levelTest a peak-normalized copyOne gain can raise the whole recording while retaining its internal balance
One impact dominates a quiet interviewInspect the impact and edit it deliberately before remeasuringThe highest sample determines a peak normalizer’s gain
Two speakers alternate between quiet and loud sentencesUse separate track gain where available, or careful automation/dynamics processingOne gain leaves their relative difference intact
Several clips need consistent perceived loudnessUse loudness measurements and a chosen loudness targetTheir peak values alone do not describe their overall level
Noise covers the voiceEvaluate noise reduction or source isolationIncreasing gain changes the voice and noise together

Keep any edits to impacts or individual words separate from peak normalization. A compressor, limiter, or gain envelope can change different parts by different amounts. Their settings and audible tradeoffs need their own listening checks.

Preserve stereo balance deliberately

This normalizer measures the highest sample across both channels and applies one shared gain. Suppose the left peak is 0.25 and the right peak is 0.125. Bringing the left peak to about 0.89125 brings the right to about 0.44563. The right remains about 6.02 dB below the left in sample peak.

That is useful when the existing stereo balance is intentional. Audacity’s Normalize documentation explains the distinction between linked and independent stereo-channel processing. This tool always links channels and does not remove DC offset.

If an interview has a different microphone on each side, decide whether the channels should be edited separately first. The channel splitter can export existing left and right recordings as separate mono WAVs. Channel extraction still does not remove room noise or spill already captured on each microphone.

Gain does not improve the voice-to-noise relationship

A constant multiplier applies to every sound. If you raise a voice by 10 dB, you also raise the hiss and traffic mixed with it by 10 dB. A recording may become easier to hear, but the relative level of that noise has not improved.

Listen before normalization to decide whether the clip is simply quiet or whether a competing source is the real obstacle. The audio cleanup chooser helps distinguish a steady-noise treatment from source isolation, a gate, or an edit. For an overlapping source, evaluate the voice isolation workflow on a representative original excerpt.

After cleanup, compare the processed result with the original at a similar listening volume so the louder version does not dominate your judgment. Check consonants, soft words, breaths, and overlapping sections. Choosing the same peak for both copies is not a complete loudness match; a loud impact can still skew the comparison.

Sample headroom is different from a true-peak check

A −1 dBFS sample target leaves room below the full-scale stored-sample limit. It does not establish the highest reconstructed peak between those samples. Later mixing, effects, and lossy encoding can also change the final result.

For a delivery with a true-peak limit, use a true-peak meter on the final exported file. This tool does not oversample to estimate true peak or use a limiter. Do not turn its default target into a claim that every playback system or later encoding is protected from overload.

Lowering a damaged clip is also not a clipping repair. Flat or distorted portions already in the source remain after gain adjustment. An alternate intact take may be a better starting point than repeated processing. Compare the original clipped and attenuated audio examples to see why a lower peak reading does not establish repair.

Normalize and check a short file locally

  1. Open the peak normalizer and choose a supported MP3 or WAV up to 50 MiB and five minutes.
  2. Play the original at a comfortable level. Read the measured decoded sample peak and check whether the issue is overall gain.
  3. Enter a sample-peak target from −24 to −0.1 dBFS. Read the required gain; a large boost also raises low-level noise.
  4. Keep the default WAV for a PCM working copy, or choose MP3 and a bitrate for a delivery copy. Prepare the result and alternate between the original and processed previews; the players pause each other to help avoid doubled playback.
  5. Download the result and listen in the intended edit. For a specified delivery, measure the final export with appropriate loudness and true-peak tools.

The default WAV output is 48 kHz, 16-bit PCM, retaining the complete decoded duration and mono/stereo channel count. Browser decoding can resample the input, as documented in MDN’s decodeAudioData reference. The WAV is a new PCM export, not a copy of the source bytes or metadata.

Optional MP3 exports use 128, 192 or 320 kbps. The same linked gain is applied before encoding, but MP3 is a new lossy copy: decoding it again can change the sample peak and loudness. A −1 dBFS normalization setting is therefore not a guarantee that a decoded MP3 will stay below −1 dBFS, and it is not a true-peak ceiling. Measure the actual chosen file with the loudness and sample-peak meter; use a suitable separate true-peak meter if your delivery requires one.

MP3 can add codec delay or padding. Use WAV for precise timeline placement, listen to the actual MP3 preview when sharing, and retain the original for another edit. Compare the measured WAV and MP3 examples for a controlled illustration of file size and timing, not a quality recommendation.

A compressed input can fit while its uncompressed WAV is too large. The output must also fit within 50 MiB. Use the size calculator to plan a shorter excerpt, or the trimmer to cut one. The WAV inspector can check the downloaded file’s stored format and size. Keep the original throughout.

For a repeatable comparison, keep the audio-comparison worksheet with your reference, candidate, selected range and settings. It separates requested targets from actual sample-peak and integrated-LUFS readings. Its worked equal-peak example contains stored synthetic-file measurements, with listening notes left for you to complete.

Common questions

Why did my normalized clip remain quiet?

One loud sample or impact can determine the gain for the entire clip. Inspect that event and the changing level of the wanted audio. A higher sample target alone may leave the passages you care about relatively quiet.

Can I normalize without uploading audio?

Yes. The free normalizer decodes, measures, adjusts, previews, and exports in this browser. No audio is sent to Saturalabs, and no account or download credits are required for this utility.

Should I normalize every file before AI isolation?

Do not assume a gain change improves separation. If your supported original is ready, test it first and judge the audible result. The preparation guide explains how to choose a useful excerpt and preserve its timeline position.

Does equal peak mean equal volume?

Equal sample peak means the maximum stored sample reaches the same level. It does not ensure that different recordings have equal perceived loudness. Use a suitable loudness measurement for that comparison.

From the Saturalabs journal

Practical notes on sound isolation, music, and clearer dialogue. About our guides ↗

Your next step

Normalize a short recording

Read a decoded sample peak, choose a dBFS target, and preview a free WAV export locally.

Open the tool