What Is LUFS? Audio Loudness for Video Explained (2026)

LUFS stands for "Loudness Units relative to Full Scale" — a standardized estimate of perceived loudness over time, rather than an instantaneous peak. Some services normalize playback, but behavior depends on the service, device, and settings. Published delivery requirements, playback normalization levels, and practical mastering targets are different things. Choose the relevant guidance, preserve useful dynamics, and measure the encoded result.

Audio clarity matters even when the picture is strong. Cranking a master can crush its dynamics without making it louder on a normalized playback system. This guide demystifies LUFS: what it measures, why peak meters alone are not enough, which targets are documented, and how to check a finished mix. The one-line version lives in the LUFS glossary entry.

What is LUFS?

LUFS (Loudness Units relative to Full Scale) is a unit that measures perceived loudness — how loud audio seems to human ears over time. The measurement algorithm is specified in ITU-R BS.1770; EBU R 128 applies loudness measurement to programme delivery. Two clips with identical peak levels can sound very different in loudness.

You may also see LKFS (Loudness, K-weighted, relative to Full Scale). LUFS and LKFS are equivalent units when the same measurement algorithm, channels, and gating are used. A matching number alone is not enough if one specification measures dialogue and another measures the full mix.

Typical programme LUFS readings are negative: -14 LUFS is louder than -23 LUFS, a difference of 9 loudness units. LUFS is not a peak meter, so 0 LUFS should not be treated as the same ceiling as 0 dBFS. Compare programme loudness and peak headroom separately.

The key word is perceived. LUFS uses "K-weighting" — a filter that approximates how the human ear responds to different frequencies — and measures loudness over time, so it reflects what you actually hear, not just an instantaneous electrical peak.

Why not just use dB or peak levels?

For decades, people measured audio by its peak level in dBFS (decibels relative to full scale) — the highest instantaneous sample. The problem: peak level tells you nothing about how loud something sounds.

Consider two examples:

• A quiet acoustic guitar with one sharp pluck can peak at 0 dBFS but sound quiet overall.
• A heavily compressed pop master that's loud the entire time can also peak at 0 dBFS but sound much louder.

Same peak, totally different perceived loudness. Peak measures the ceiling; it says nothing about the average energy your ears integrate over time. This gap fueled the infamous "loudness war" — decades of music and ads being compressed and limited to be as loud as possible, because "louder" grabbed attention, even though it crushed dynamics and caused listener fatigue.

Loudness normalization reduces the incentive to master ever louder: when gain is reduced during playback, the lost dynamics are not restored. It has not made every service or device behave identically, and a mix still needs to sound good with normalization on or off.

LUFS vs dBFS vs RMS vs true peak

These terms all describe "level," but each measures something different. Here's how they relate:

The two you care about in practice are LUFS (how loud it sounds — your loudness target) and true peak (dBTP — your safety ceiling to prevent distortion). A typical delivery spec is something like "-14 LUFS integrated, true peak no higher than -1 dBTP."

Integrated, short-term, and momentary LUFS

LUFS is measured over different time windows, and knowing which is which prevents confusion:

• Momentary LUFS — measured over a very short window (~400ms). Reflects instantaneous loudness.
• Short-term LUFS — measured over ~3 seconds. Useful for watching loudness move through a section.
• Integrated LUFS — measured over the entire clip or program. This is the number platforms use and the one you target.

A target normally needs an integrated measurement, but also check the material and gating specified: whole-program loudness and dialogue-gated loudness are not interchangeable. Your meter may show all three time windows; select the mode required by the delivery spec.

Two related metrics you'll see on a meter:

• LRA (Loudness Range) — how much the loudness varies across the program (dynamics). A film has high LRA (whispers and explosions); a podcast wants low LRA (consistent, always intelligible).
• True Peak (dBTP) — an estimate of the reconstructed waveform's peak. Leaving headroom, often at least 1 dB for a web master, reduces encoding-related clipping risk; measure the encoded result and follow any stricter delivery spec.

Platform loudness targets (2026)

Use the status column: a suggested master level is not a claim about what every player does. The linked guidance was checked on September 14, 2026; confirm the destination's current requirements for a critical delivery.

A few practical takeaways:

• For web video without a specified target, -14 LUFS can be a starting point, not a requirement. Judge intelligibility, dynamics, and playback together.
• For Apple Podcasts, use its -16 LKFS (±1) recommendation; check other hosts rather than assuming all podcast services share a normalization policy.
• Broadcast targets of -23/-24 are not directly interchangeable with web-mastering recommendations. Follow the receiving broadcaster's spec.
• A playback target may vary by user setting or device. Re-check the linked documentation rather than treating a year in a table heading as a guarantee.

Why LUFS matters: loudness normalization

Loudness normalization adjusts playback gain toward a target, where the player supports it and it is enabled. It does not necessarily rewrite the uploaded file or apply the same adjustment everywhere.

• As an illustrative calculation, a -9 LUFS master played at a -14 LUFS normalization target needs roughly 5 dB of attenuation. The gain reduction does not restore dynamics already lost to heavy limiting.
• Raising quiet material may be limited by peak headroom or unsupported in a playback mode. Spotify documents both positive and negative gain, including headroom limits and devices that do not normalize.

The goal is a clear, balanced mix with appropriate loudness and peak headroom. Being turned down by playback normalization is not a content penalty; it is a gain adjustment. A dynamic mix can remain a good mix after that adjustment.

Related audio concepts: ducking and dialogue leveling

Loudness work in a video edit isn't just one master number — it's keeping the dialogue consistently intelligible. Two related techniques:

• Ducking — automatically lowering the music (or game audio, or ambience) whenever someone speaks, so the voice always sits on top. You've heard this in every podcast intro where the music drops under the host. It's often done with keyframed volume or a sidechain compressor.
• Dialogue leveling — evening out a speaker whose volume wanders (leaning in and out of the mic), so every word is at a consistent level before you set the overall LUFS.

Get dialogue leveled and ducked first, then set your integrated LUFS target. Loudness is the final stage, not the fix for a messy mix.

How to mix to a target LUFS

Here's the reliable order of operations for hitting a loudness target without crushing your audio.

Step 1: Clean and level the dialogue first

Remove noise, even out volume swings, and make speech consistently intelligible. Loudness targeting comes after the mix is balanced, never before.

Step 2: Duck music and effects under speech

Lower music and background beds whenever dialogue is present, so the voice stays on top. Aim for music several dB below the dialogue during speech.

Step 3: Add a loudness meter

Use a LUFS meter (built into most editors and DAWs) and play the whole program to read the integrated LUFS. Don't trust your ears alone — monitor level fools everyone.

Step 4: Adjust overall level toward the target

Raise or lower the master until integrated LUFS sits near your target (e.g., -14 for social, -16 for podcasts). Small gain moves, not aggressive limiting.

Step 5: Control true peak with a limiter

Set a true-peak limiter to the destination's ceiling; -1 dBTP is a common web-master starting point, with more headroom where required. Limiting can change integrated loudness, and encoding can create new peaks, so it is not a substitute for checking the final file.

Step 6: Verify and export

Re-measure integrated LUFS and true peak on the final render. Use export presets that match the platform, and check the numbers before you publish.

Common loudness mistakes

• Mastering as loud as possible. Normalized playback may turn it down without restoring the dynamics you removed.
• Confusing peak with loudness. Hitting 0 dBFS peaks doesn't mean you're at the right LUFS.
• Ignoring true peak. Peaks that look fine can distort after lossy encoding without a true-peak limiter.
• Targeting loudness before the mix is balanced. Fix dialogue and ducking first; loudness is the last step.
• Using the wrong delivery spec. A -14 LUFS master will not meet a -23 LUFS broadcast target without adjustment; web playback needs its own check.
• Quiet dialogue under loud music. The most common intelligibility killer — duck the music.
• Not metering at all. Guessing by ear leads to wildly inconsistent videos.

How AI video editors handle loudness

Loudness measurement and normalization are good candidates for automation and do not inherently require AI. Some AI video editors also offer dialogue leveling or ducking. These are separate capabilities: a tool that detects speech does not necessarily meter integrated loudness or limit true peaks.

A transcript and speaker detection can help locate speech for ducking, but timing and identity do not measure its level. Check for explicit loudness metering, normalization, and peak controls in the chosen tool. When you export for multiple platforms, verify each destination's requirements and the resulting files.

In Loopdesk (disclosure: Loopdesk is our product), plain-English direction is part of the editing workflow; it should not be taken as proof of a particular LUFS or true-peak implementation. Check the documented capabilities and meter your export, especially when stitching clips recorded at different levels. This belongs to the sound-mix stage. If the required loudness controls are not available, finish and verify the mix in a dedicated audio tool. LUFS is one entry in the full video editing glossary.

Frequently Asked Questions

What does LUFS mean?

LUFS stands for Loudness Units relative to Full Scale. It estimates perceived loudness over time using K-weighting, unlike a sample-peak reading. A programme at -14 LUFS is louder than one at -23 LUFS.

What LUFS should I use for YouTube?

Around -14 LUFS is a practical starting point for a web-video master, not a guaranteed rule for every YouTube playback mode. Leave true-peak headroom, preserve useful dynamics, and check the encoded upload.

What is the difference between LUFS and dB?

dB (specifically dBFS peak) measures the highest instantaneous level, while LUFS measures perceived loudness averaged over time using ear-weighting. Two clips can have the same peak dB but very different LUFS — that's exactly why LUFS was created.

What LUFS is best for podcasts?

Apple Podcasts recommends around -16 LKFS, with a ±1 dB tolerance and true peak no higher than -1 dBTP before encoding. Check your host's requirements and the encoded result; this is mastering guidance, not a universal podcast playback policy.

Why does my audio get quieter after uploading?

Playback normalization may reduce gain when a master exceeds the player's target. Behavior depends on the service, settings, and device. Compare the uploaded file and playback settings before assuming the platform changed your audio; attenuation is not a content penalty.

What is true peak (dBTP)?

True peak estimates the highest level of the reconstructed waveform, including between samples. Leave headroom appropriate to the delivery spec and re-measure the encoded file. A -1 dBTP limiter reduces clipping risk but does not guarantee a distortion-free encode.

Is louder always better for audio?

No. On normalized playback, extra mastering loudness may be turned down without restoring lost dynamics. Aim for intelligible dialogue, useful dynamic range, and controlled peaks at an appropriate delivery level, not maximum loudness.

Can AI set the right loudness automatically?

Some tools automate leveling, ducking, and loudness normalization, but these are separate features and do not inherently require AI. A transcript alone cannot measure loudness. Check the tool's controls and verify integrated LUFS and true peak on the exported file.

---

Planning your next edit? Open Loopdesk for prompt-driven editing, then verify the exported audio against your delivery requirements with a loudness meter.