Normalizing audio means applying a single gain change to a clip, a track or an entire mix so it lands on a target level, either a peak ceiling in dBFS or a perceived loudness target in LUFS. Knowing how to normalize audio levels in an edit means your editor measures the audio, works out the difference from your target, and shifts every sample by the same amount.
The whole job takes about ten minutes on a mid-length interview once you know the order of operations: clean first, measure second, apply gain third, control peaks fourth, then export and verify. Skipping a step is what produces the two classic failures — audio that still sounds uneven after normalizing, and audio that distorts the moment you push it up.
What You Need
Any current editor will do. A digital audio workstation, or DAW, is software that records, edits and mixes sound; Audacity, Reaper, Adobe Audition and Logic Pro all handle the job, and if you cut video then DaVinci Resolve, Premiere Pro and Final Cut Pro each have a built-in loudness meter. Free or paid does not change the maths.
You also need monitoring you can trust. Closed-back headphones will find hiss and pumping that laptop speakers hide, and a pair of decent monitors is worth more here than any plugin. Trust your ears for tone, but trust the meter for level.
Four terms carry most of the confusion, so it is worth fixing them before you touch a fader. LUFS is a measure of perceived loudness that weights frequencies the way human hearing does, then averages the result over the programme. Integrated loudness is that average across the entire file, which is the number platforms care about. True peak, written dBTP, is the highest point in the waveform after the signal is reconstructed as an analogue waveform, and it can sit above the highest stored sample. Headroom is the space you leave below 0 dBFS so peaks have somewhere to go.
Step-by-Step
Choose a target loudness for how to normalize audio levels in an edit
Pick one number and commit to it, because the difference between the three measurements is the reason people normalize twice. Integrated loudness describes the whole file. Short-term loudness describes roughly three-second windows, which is what catches a section that jumps in level. True peak describes the single highest transient.
Match the target to where the file is going. These are editorial starting points, not the formal delivery specifications that streaming services and broadcasters publish, so check your distributor’s current spec before final delivery.
| Destination | Integrated loudness | True peak ceiling |
|---|---|---|
| Mid-edit working level (peak normalize) | n/a, use -6 dBFS peak | -6 dBFS |
| Podcasts, spoken word (stereo) | -16 LUFS | -1 dBTP |
| Podcasts, spoken word (mono) | -19 LUFS | -1 dBTP |
| YouTube and general online video | -14 LUFS | -1 dBTP |
| EBU R128 broadcast (Europe) | -23 LUFS | -1 dBTP |
| ATSC A/85 broadcast (US) | -24 LKFS | -2 dBTP |
| AES streaming recommendation | -16 to -18 LUFS | -1 dBTP |
For a radio station feed, -6 dBFS peak during editing with a -23 LUFS integrated target at delivery is the standard path. Musicians may not care, but every listener’s device has one volume knob, and consistency matters more than a high number.
Prepare and clean the audio before normalization
Normalizing amplifies everything in the clip, including the parts you did not want. A recording with a -60 dB noise floor will come out of a +12 dB gain change with that hiss at -48 dB, which is clearly audible. Editors on r/VideoEditing raise this constantly, and the rule they land on is simple: clean first, normalize last.
Work through the edit in this order. Trim dead air and long gaps, then apply noise reduction or hum removal at a conservative setting, then de-ess if sibilance is spiky, then cut breaths only if they distract. Repair clicks and pops, and if the source recorded into clipping, flag it now rather than hoping a plugin can rescue it.
Next, look for hidden clipping. Zoom the waveform in until individual samples are visible, and check the sections around the loudest words. Where peaks flatten into a flat-topped plateau, the recording itself is already distorted, and no amount of normalization will bring those samples back.
Finally, separate what you are leveling. Put each speaker on their own track, label the music and effects beds, and reset every clip’s manual level offset to 0 dB before you do anything else. Editors working in Final Cut Pro hit this hard: the normalization gain filter ignores manual level offsets, so a clip you trimmed to -12 dB earlier will normalize to the wrong place unless the offset is cleared first.
Measure the loudness before applying gain
Measure, do not guess. The loudness meter lives in a different place in each editor, but every one of the big three has a permanent readout worth learning.
- DaVinci Resolve: open the Fairlight workspace and look for the Loudness meter in the mixer, or add it from the audio options menu. Reading clip loudness is easier from the Audio Processing Options panel, which opens when you normalize a clip.
- Premiere Pro: the Audio Meter panel in the Essential Sound workspace shows loudness alongside the classic peak meters, and the panel can be pinned to the timeline so it never disappears.
- Final Cut Pro: the loudness meter sits in the top-right of the timeline window and can also be opened from the View menu. It reports integrated loudness and loudness range directly.
- Audacity: there is no permanent LUFS meter, so open Effect, then Loudness Normalization, and read the measured value it prints for your track.
Play the entire programme and let the meter settle. Measuring only a quiet passage or a single clip will give you a number that makes no sense for the finished piece, which is the single most common reason a normalized file still sounds uneven. Integrated loudness is an average over the whole timeline, so the sample you measure has to be the whole timeline.
Watch the peak meter at the same time. If loud sections are well above the average, you have a dynamics problem, and a flat gain change will not fix it.
Apply gain or loudness normalization
The calculation is subtraction. Take your measured integrated loudness, take your target, and the difference is the gain you apply. If the file measures -22.4 LUFS and you want -16 LUFS, add 6.4 dB. If a quiet voiceover measures -31 LUFS and you want -14 LUFS, add 17 dB, and you should listen hard afterwards because that much lift will reveal every noise artefact you left behind.
Never work backwards with a negative number by accident. Normalizing from -14 LUFS down to -16 LUFS means subtracting 2 dB, and typing a positive figure instead will push the whole programme into clipping.
Each editor has its own route to the same result, and the menu labels differ more than the logic does.
| Editor | Menu path | What it does |
|---|---|---|
| DaVinci Resolve | Right-click clip, then Normalize Audio, then Normalize to -14 LUFS | Applies loudness normalization to the selected clip |
| DaVinci Resolve | Right-click clip, then Normalize Audio, then Normalize to Peak | Peak normalization, useful as a rough mid-edit pass |
| DaVinci Resolve | Fairlight, select the bus, then Audio Processing Options, then Loudness | Sets loudness normalization for a whole track or mix bus |
| Premiere Pro | Right-click clip, then Audio Gain, or press G | Opens the dialog with Normalize All Peaks To and Normalize Max Peak |
| Premiere Pro | Essential Sound panel, mark clips as Dialogue, then Edit, then Auto-Match Audio | Level-matches dialogue clips to a LUFS target |
| Premiere Pro | Audio Track Mixer, then Normalize Mix Track | Normalizes the finished mix rather than individual clips |
| Final Cut Pro | Modify, then Audio, then Normalization Gain | Sets Smart, Normal, Loudness or Level mode and the target |
| Final Cut Pro | Modify, then Audio, then Normalize Mix Track | Applies the target to the whole mix |
| Audacity | Effect, then Normalize, then tick Normalize peak amplitude to | Peak normalization to a chosen dBFS value |
| CapCut | Select clip, then Volume, then switch Normalize on | Auto-levels a clip toward the app’s target |
Two Resolve options cause lasting confusion. Loudness normalization measures the program and applies gain to hit a LUFS or dBTP target, while the older Optimize to Standard command simply picks a preset standard for you without showing the measurement. Use loudness normalization when you want a specific number, and check the result in the Audio Processing Options panel before you move on.
To confirm the adjustment worked, re-measure. The integrated reading should land within about 0.1 to 0.3 LU of your target once the clip is analysed again, and any clip you skipped should still read at its original level, which tells you the pass did what you expected and nothing else.
Control peaks with compression or a true-peak limiter
A gain change moves peaks and average level together, so a file that peaked at -3 dBFS and you lift by 6 dB now peaks at +3 dBFS, and everything above 0 dBFS is hard clipping. That is the whole reason a normalized file can distort.
Work in this order. Compress first, so the loud and quiet parts sit closer together and you need less gain. Then apply the gain. Then catch whatever transients are left with a limiter, setting a true peak ceiling of -1 dBTP rather than 0 dBFS, because intersample peaks can still exceed the stored samples and cause distortion after conversion.
Use conservative settings. A ratio of 4:1 to 6:1 with a few decibels of reduction at moderate attack speeds does the job; a fast limiter slammed onto dialogue sounds like the words are being cut off. Listen specifically for pumping, where the level swells on every breath, and back off the threshold until it disappears.
Check the meter again afterwards. Integrated loudness should be close to your target, and the maximum true peak reading should sit at or under the ceiling you chose.
Export, compare, and verify the normalized file
Always render a fresh master rather than re-processing a file you have already processed. Re-normalizing an already-normalized export stacks a second gain change on the first, and if the first pass hit a limiter, the second pass pushes the limiting harder.
Then do a proper A/B. Align the original and the new master to the same monitoring level so you are not fooled by volume differences, and listen to the beginning, the middle and the end rather than the first ten seconds. On the export, read the integrated loudness and the maximum true peak and confirm both match what you intended.
If the delivered file reads higher than your target, check whether the exporter recalculated the loudness measurement. Some encoders re-measure on write, so the number on your timeline is not always the number in the file.
Common Mistakes
Normalizing at the very start of the chain, before any editing, raises the noise floor and makes room hiss obvious. The fix is to normalize once the edit is finished and the audio is clean, with a peak pass at -6 dBFS early on if you need a rough guide.
Applying peak normalization to everything lifts music beds and ambient tracks to dialogue level, which surfaces compression pumping and reveals how loud the effects actually are. The fix is to tag your clips and normalize only dialogue, leaving music beds at the level the music was mastered to.
Targeting peak level instead of perceived loudness is the same mistake from the other side. Clips with matching peaks can still sound very different because their dynamics differ, so match clips on loudness, then use limiting to control the peaks.
Forgetting to reset manual level offsets before a multi-clip pass means clips you already trimmed normalize to the wrong place, particularly in Final Cut Pro where the gain filter ignores those offsets. The fix is to clear all attributes to 0 dB first, then normalize the selection in one action.
Setting a limiter ceiling above 0 dBFS guarantees hard clipping. A conventional sample-peak ceiling of 0 dBFS also allows intersample peaks through, so use a true peak limiter and set the ceiling at -1 dBTP.
Raising the file after limiting undoes the limiter’s work. Gain before the limiter, never after, or the ceiling you carefully set becomes meaningless.
Exporting lossy formats repeatedly degrades audio, and exporting the same lossy file to judge loudness gives you a misleading reading. Render one lossless master, and do your level checks on that file.
Judging levels only through headphones at whatever volume feels comfortable hides the real problem. Audition at a controlled level matched to a reference you trust, and confirm the numbers on the meter.
One more worth knowing: if the audio still sounds uneven after normalizing, check that you actually measured the whole programme. A reading taken from ten seconds of the loudest section will produce a gain change that makes the quiet half of the file too quiet to hear.
Frequently Asked Questions
What loudness level should I normalize audio to?
For spoken content such as podcasts, start at -16 LUFS integrated for stereo and -19 LUFS for mono, with a true peak ceiling of -1 dBTP. Online video sits nearer -14 LUFS. Broadcast follows EBU R128 at -23 LUFS or ATSC A/85 at -24 LKFS. While editing, normalize peak to about -6 dBFS and save the loudness pass for the final render.
What is the difference between LUFS and dBFS?
LUFS measures perceived loudness. It weights frequencies the way human hearing does and averages the result across the programme, which is why a sparse piece of music can measure low while sounding loud. dBFS measures one sample against digital full scale, where 0 dBFS is the maximum a file can hold. A healthy peak sits near -6 dBFS, while integrated loudness usually lands somewhere between -14 and -24 LUFS.
Should I normalize audio before or after compression?
Compress first, then normalize. A compressor changes the gap between quiet and loud passages, so a level you set beforehand drifts as the compressor works. A peak pass at -6 dBFS early in the edit is harmless as a rough guide, but apply your final loudness target after dynamics processing and before the limiter. That way the number you measured is the number you deliver.
Why does audio clip after I normalize it?
Normalization adds the same number of decibels to every sample, so a clip peaking near -3 dBFS will run over the top after a 6 dB lift. Leave headroom instead: compress or limit after the gain change, and set a true peak ceiling at or below -1 dBTP. Remember that clipping baked in at the recording stage cannot be undone afterwards, whatever a plugin’s name suggests.
Should I normalize each speaker or track separately?
For an interview, yes. Put each speaker on their own track, normalize every dialogue track to the same target, then bring them together on a bus with its own loudness normalization. Normalizing the finished mix alone cannot rescue a speaker who is 10 dB quieter than the other, because the louder voice already sets the reference. Editors on r/videography use this per-speaker approach as standard.
Conclusion
Start by cleaning the recording, because normalization will not fix hiss, hum or a clipped source. Then measure the integrated loudness of the entire programme, pick a target that suits the destination, and apply exactly the difference. Compress first, limit the peaks at a true peak ceiling of -1 dBTP afterwards, export a fresh master and read the meter one more time before you deliver it.
