Free Online LUFS Meter
Measure your track’s loudness right in the browser — no upload, no registration, no size limits.
- What the metrics mean
- Why LUFS exists: a short loudness-war history
- How it works: ITU-R BS.1770 in plain words
- dBFS, LUFS, RMS, Peak — what’s the difference
- True Peak, and why −1 dBTP instead of 0
- Platform targets
- How each platform actually normalizes
- Recommendations by genre
- Gain staging: how to reach your target LUFS
- Glossary
- Privacy
- Need to hit a target?
Drop a WAV, MP3 or M4A file. The analyzer runs fully on your device and reports Integrated LUFS, Loudness Range (LRA), True Peak, plus short-term / momentary maxima. You’ll see at a glance whether your track fits Spotify, Apple Music, YouTube, Tidal, Amazon, Deezer, SoundCloud, CD or broadcast EBU R128.
Implemented as an AudioWorklet following ITU-R BS.1770-5 — the same standard streaming services use to compute normalization.
What the metrics mean
Integrated LUFS — the gated, perceived loudness of the whole track per ITU-R BS.1770. This is the value platforms use to decide whether to turn your track up or down.
Loudness Range (LRA) — dynamic range of loudness, in loudness units. Low LRA = squashed master, high LRA = living dynamics.
True Peak (dBTP) — the maximum inter-sample peak after oversampling (at least up to an equivalent of 192 kHz; 4× for 48 kHz material). Keep it below the platform ceiling to avoid clipping when transcoded to lossy formats.
Short-term max / Momentary max — the loudest 3-second / 400-ms window. Useful for spotting the hottest sections.
Why LUFS exists: a short loudness-war history
Back in the 80s, studio loudness was measured on VU meters and peak meters: voltage, RMS, dBFS. That was enough while each release sat on a single medium — vinyl, cassette, later CD — and its loudness was baked into the pressing.
With CDs in the 90s came the loudness war. Producers noticed: a track that plays louder than its neighbors on radio sounds brighter and grabs attention. To win, each new release was squeezed harder — compressors, limiters, masters pushed almost to 0 dBFS. Over a decade the average loudness of pop masters went up 6–10 dB, but dynamics died with it: quiet passages became as loud as the loud ones.
Then streaming arrived in the 2010s and solved the war with a single rule: we normalize loudness at playback. If you deliver a track at −6 LUFS, Spotify will pull it down to −14 anyway — all your loudness battle evaporates, leaving only a crushed sound.
That’s when the industry needed an honest, reproducible loudness metric — not dBFS, not RMS, not peaks. The answer was ITU-R BS.1770 and its unit LUFS. It measures how loud a track actually sounds to the ear, not how close it sits to the digital ceiling.
How it works: ITU-R BS.1770 in plain words
The ITU-R BS.1770 standard first appeared in 2006; the current version is BS.1770-5 (2023). It describes how to measure loudness properly. Three steps.
1. K-weighting — two filters in series: a pre-filter (high-shelf, ~+4 dB above 2 kHz) and an RLB filter (high-pass with noticeable roll-off below 100 Hz). This is a rough approximation of human hearing — the ear is less sensitive to low frequencies and more sensitive to the upper mid. The filtered signal is then mean-squared.
2. Time windows. Momentary is averaged over 400 ms, Short-term over 3 seconds, Integrated over the whole track with gating. Small windows catch momentary perception spikes; the big one gives overall loudness.
3. Gating. When computing Integrated LUFS the standard excludes quiet blocks — first anything below −70 LUFS (absolute gate), then anything below −10 LU relative to the loudness measured after the absolute gate (relative gate). Without gating, silence at the beginning and end would drag the average down by several LU.
True Peak is defined in BS.1770 Annex 2 — a peak value measured after oversampling to at least an equivalent of 192 kHz (4× for 48 kHz; 2× is enough for 96 kHz). That’s enough to catch intersample peaks. EBU Tech 3341 standardizes the meter requirements.
dBFS, LUFS, RMS, Peak — what’s the difference
All four are "loudness", but they measure different things. Easy to confuse, especially coming from a peak meter.
| Metric | What it shows |
|---|---|
Sample peak (dBFS) |
Max absolute sample value. A clipping indicator, not a loudness indicator. Two tracks with the same peak can sound completely different. |
RMS |
Root mean square. Gives a rough feel of "energy" but ignores the ear’s frequency sensitivity. Two tracks with the same RMS — one bassy, one bright — will sound different loudness-wise. |
LUFS |
RMS + K-weighting + gating. This is how loud the track actually sounds to a human. The only metric that lets you correctly compare loudness across different works. |
True Peak (dBTP) |
Same as sample peak but with oversampling. Shows peaks that will appear after D/A conversion or lossy encoding — where sample peak can’t see them yet. |
In short: dBFS tells you "how close to the digital ceiling", LUFS tells you "how loud to the ear". Streaming cares about LUFS; clipping protection cares about True Peak. RMS is now a historical metric.
True Peak, and why −1 dBTP instead of 0
If the file on disk peaks at −0.1 dBFS, it’s tempting to assume it doesn’t clip. It does. After D/A reconstruction at playback, an intermediate value between two "honest" samples can exceed 0 dBFS. That’s an intersample peak. The speaker doesn’t know, the amp doesn’t always know either — but a lossy decoder can reconstruct that peak explicitly and clip.
Typical behaviour:
-
AAC (used by Apple Music, YouTube, Spotify): can add 0.3–1 dB to intersample peaks.
-
MP3: 0.3–0.5 dB.
-
Ogg Vorbis / Opus: 0.5–1 dB.
That’s why streaming services set the ceiling at −1 dBTP (or −2 for "loud" presets) rather than 0 — headroom for the codec, so there’s no audible clipping on listeners' devices after transcoding to AAC/OGG. CD and Bandcamp play the uncompressed file as-is — no transcoding there, but even then 0 dBFS sample peak does not guarantee there are no intersample clips after D/A reconstruction in the listener’s player.
Simple mastering rule: if the file goes to streaming — set the limiter ceiling to −1 dBTP. For CD or Bandcamp — at least −0.3 dBTP as insurance against intersample peaks; for very loud masters you can stick to −1 dBTP.
Platform targets
Different destinations treat your file differently. The analyzer splits them into three groups because the rules differ in principle:
-
Streaming — the player normalizes each track to a fixed LUFS target at playback. Integrated loudness matters.
-
Aggregator recommendations — distributors (DistroKid, TuneCore, etc.) don’t play anything themselves; they deliver the file to streaming services. Their "recommended loudness" is essentially a streaming-safe mastering target, usually −14 LUFS / −1 dBTP, so the file sounds good wherever it lands.
-
Delivery (no normalization) — CD, Bandcamp and similar play the file exactly as you uploaded it. LUFS doesn’t matter there; only the True Peak ceiling matters, to avoid audible clipping.
Aggregator recommendations
Digital distributors don’t apply normalization of their own — they just relay your file. They all converge on a streaming-safe target so the file plays well wherever they deliver it.
Target: −14 LUFS integrated, −1 dBTP true peak.
Applies to: DistroKid, CD Baby, TuneCore, Amuse, Feiyr, RouteNote, Horus Music, Ditto Music.
Streaming (loudness-normalized)
Exceed the target and the platform will turn your track down at playback, so you lose the loudness you paid for with compression. Fall short and your track will sound quieter than its neighbors.
| Platform | Integrated | True Peak | Note |
|---|---|---|---|
Spotify |
−14 LUFS |
−1 dBTP |
Default normalization |
Spotify Loud |
−11 LUFS |
−2 dBTP |
Loud preset |
Apple Music |
−16 LUFS |
−1 dBTP |
Sound Check |
YouTube / YT Music |
−14 LUFS |
−1 dBTP |
Single-track target |
Amazon Music |
−14 LUFS |
−2 dBTP |
|
Tidal |
−14 LUFS |
−1 dBTP |
|
Deezer |
−15 LUFS |
−1 dBTP |
|
SoundCloud |
~−14 LUFS |
−1 dBTP |
Mastering guideline (does not normalize) |
EBU R128 |
−23 LUFS |
−1 dBTP |
Broadcast |
Delivery / no normalization (peak only)
These destinations play or deliver the file "as is", without loudness matching. Only peak headroom matters: 0 dBFS sample peak is the formal ceiling, but in practice keep True Peak below it to rule out intersample clipping at playback.
| Destination | Integrated | True Peak | Note |
|---|---|---|---|
CD master |
— |
≤ 0 dBFS (better ≤ −0.3 dBTP) |
Red Book |
Bandcamp |
— |
≤ 0 dBFS (better ≤ −0.3 dBTP) |
Plays as-is |
How each platform actually normalizes
Loudness normalization isn’t new. The idea came from ReplayGain (2001), which proposed metadata in audio tags. Apple shipped Sound Check in iTunes in 2002, and in 2014 Spotify launched modern BS.1770-based normalization. Today almost every major service uses the same algorithm, with different targets and logic.
Spotify (official guide): default target −14 LUFS (Normal mode). Users can switch to Loud (target −11 LUFS) or Quiet (target −19 LUFS). If the track is above target, the platform reduces gain at playback; if it’s quieter and Loud is selected, positive gain is added with an internal limiter around −1 dBTP to pull a quiet track up to target.
Apple Music — Sound Check, target −16 LUFS. The algorithm is very close to BS.1770, though Apple historically doesn’t publish the details. In practice the numbers match BS.1770 within 0.1–0.2 LU.
YouTube / YT Music: normalization down only, to −14 LUFS. A quiet track will stay quiet relative to its neighbors — YouTube won’t pull it up. This matters for albums: if one track is louder than the others, it gets lowered, and the quiet ones don’t rise to match.
Tidal, Amazon Music: −14 LUFS, logic similar to Spotify.
Deezer: −15 LUFS.
SoundCloud: nominally recommends −14 LUFS but actually plays files without normalization. That makes peaks here as important as loudness.
Recommendations by genre
Important: the numbers below are aesthetic master levels BEFORE normalization, not platform requirements. Platform demand is uniform: −14 LUFS (for most). Genre values exist so the track sounds dense and alive after streaming pulls it to its target.
After normalization the integrated loudness will still be matched to the platform target, but the living dynamics (LRA) and character stay — whereas a master crushed to −8 LUFS will, after Spotify, lose everything you fought for.
| Genre | Integrated LUFS | LRA |
|---|---|---|
EDM / dance / techno |
−7 … −9 |
3–5 |
Pop |
−8 … −10 |
5–7 |
Rock |
−9 … −11 |
5–8 |
Hip-hop / trap |
−8 … −10 |
4–6 |
Metal |
−7 … −9 |
4–6 |
R&B / soul |
−10 … −12 |
6–9 |
Indie / singer-songwriter |
−11 … −14 |
7–10 |
Jazz / acoustic |
−14 … −18 |
10–15 |
Classical |
−18 … −23 |
15–20+ |
Ambient / drone |
−18 … −22 |
10–15 |
Podcast (mono/stereo) |
−16 |
5–7 |
Film dialogue (EBU) |
−23 |
— |
Tracks with low LRA sound more aggressive and dense after normalization, but without dynamics. High-LRA tracks breathe, keep the contrast between loud and quiet parts. If your genre is classical or jazz, crushing to −8 LUFS is pointless: after Spotify the track will drop ~15 LU and lose everything you fought for.
Gain staging: how to reach your target LUFS
If you approach the final normalization with the right level structure, the master limiter works almost invisibly. A few simple rules:
-
At recording keep the average around −18 dBFS RMS (0 VU), with peaks typically −12 … −6 dBFS. The point is not clipping the input and not overheating analog emulations.
-
In the mix keep at least −6 dBFS peak headroom on the master bus. If the final limiter has to lift by 10+ dB, the mix is overbaked.
-
The master limiter belongs at the very end. Don’t stick a limiter at the start of the chain, don’t mix "into a limiter". It distorts your loudness perception during the mix and almost always leads to a flattened master.
-
Check LUFS before and after the limiter. 2–4 LU difference is normal. 6+ LU means the mix needs fixing, not limiter-pushing.
-
Don’t chase −8 LUFS. Aim for your genre: metal and EDM go louder, indie and jazz stay lower. Normalization will equalize everyone anyway.
Glossary
| LUFS (Loudness Units relative to Full Scale) |
Unit of perceived loudness per ITU-R BS.1770. Absolute scale — −23 LUFS ≈ broadcast (EBU), −14 LUFS ≈ streaming. |
| LKFS |
Same as LUFS, different name (ATSC / American standard). Values are identical. |
| LU (Loudness Unit) |
1 dB difference for a K-weighted signal. Used for ranges (LRA) and deltas. |
| dBTP (dB True Peak) |
Peak level accounting for inter-sample values, using oversampling (4× for 48 kHz, 2× for 96 kHz per BS.1770). Shows what will really happen after D/A conversion or a lossy codec. |
| dBFS (dB Full Scale) |
Digital scale relative to full amplitude. 0 dBFS is the maximum before clipping. |
| RMS |
Root mean square of the signal. Historical "average loudness" metric without frequency weighting. |
| K-weighting |
Sequence of two filters (pre-filter + RLB) approximating the ear’s frequency sensitivity. The foundation of BS.1770. |
| Gating |
Excluding quiet blocks (< −70 LUFS absolute and < −10 LU relative to the post-absolute-gate mean) when computing Integrated LUFS. |
| Integrated loudness |
Gated-averaged loudness of the whole track. The main number for normalization. |
| Short-term |
Loudness over a 3-second window. Shows "how loud the loudest section is". |
| Momentary |
Loudness over a 400-ms window. Reflects momentary perception spikes. |
| LRA (Loudness Range) |
Statistical spread of short-term loudness in LU — difference between the 95th and 10th percentiles after additional gating (EBU Tech 3342). Not the full dynamic range and not crest factor — it’s a convenient indicator of how much the track "breathes". |
| True Peak |
Real peak of the reconstructed signal between samples (oversampling ≥ 4× at 48 kHz). Measured in dBTP. Differs from sample peak because it accounts for intersample peaks. |
| Sample Peak |
Max absolute sample value in the digital signal. Shows clipping in the digital domain but not what happens after D/A conversion or lossy decoding. |
| Intersample peak |
Peak that appears between samples after reconstruction. Invisible without oversampling. |
| Oversampling |
Temporary increase of sample rate by N× (typically 4× for True Peak at 48 kHz) to detect intersample peaks. |
| D/A conversion |
Converting the digital PCM signal to analog. Inter-sample values are reconstructed at this stage — and intersample peaks can surface. |
| PCM (Pulse Code Modulation) |
The basic digital audio representation: a sequence of samples (amplitude vs. time). WAV is usually PCM in a container. |
| Normalization |
Automatic playback-level adjustment to a target LUFS. Done by streaming. |
| Limiter |
Device/plugin that prevents the signal from exceeding a set ceiling. A master limiter usually sits at −1 dBTP. |
| Ceiling |
The upper limit of a limiter; nothing passes above it. For streaming usually −1 dBTP; for CD/Bandcamp 0 dBFS. |
| Headroom |
Room between the current peak and the ceiling. Needed so plugins and codecs don’t clip. |
| Dynamic range |
General term for the difference between quiet and loud parts. LRA is one specific measure of it. |
| Compressor |
Processing that reduces the difference between quiet and loud passages (reduces dynamic range). Opposite of an expander. |
| Mastering |
The final post-production stage: tonal balance, compression, stereo image, limiting to a loudness and True Peak target. |
| VU |
Volume Unit meter — an analog needle meter that historically measured averaged loudness. Slow ~300 ms attack, no frequency weighting. |
| ReplayGain |
Early (2001) normalization standard based on metadata tags. Predecessor of BS.1770-based normalization. |
| Sound Check |
Apple’s normalization, in use since 2002, now powering Apple Music. |
| EBU R128 |
European broadcast normalization recommendation based on ITU-R BS.1770. First published Feb 2010; current V5 is 2023. Target −23 LUFS, max true peak −1 dBTP. Spec. |
| ITU-R BS.1770 |
International loudness-measurement standard. Currently at version −5. Official text at ITU. |
Privacy
The file never leaves the browser. Decoding and measurement run locally via the Web Audio API. No analytics are loaded inside the analyzer.
Need to hit a target?
Use the mastering tool to normalize your track to any of these targets — loudness, true-peak ceiling and compression in one pass.