← BACK TO BLOG

How to Read a Loudness Meter: LUFS in Plain Language

A loudness meter shows momentary loudness over 400 ms, short-term over 3 seconds, integrated across the measured program, true peak in dBTP, and loudness range (LRA). Read all five with BeamTracer's browser loudness meter, on the Loudness tab of the Audio Analysis Engine in Chrome or Edge. Measure the complete track before comparing its integrated reading with a platform target.

Hi, I'm Trina with BeamTracer.com — let's put names on the five numbers your loudness meter keeps showing you.

At some point someone told you your track needs to "hit −14 LUFS", you opened a loudness meter to check, and it answered with five different numbers, none of which was labeled "your track". M, S, I, dBTP, LRA. A graph. A histogram.

Each reading answers a different question about your track: how loud the current passage is, how loud the measured program is overall, how high its peaks reach, and how much its loudness varies.

What are the five numbers on a loudness meter?

ReadingWindowThe question it answers
M (momentary)last 400 msHow loud is it right now?
S (short-term)last 3 sHow loud is this section?
I (integrated)everything since resetHow loud is the measured program?
True peak (dBTP)inter-sampleHow high do reconstructed peaks reach?
LRAwhole sessionHow much does the loudness move?

What does LUFS measure, and how is it different from RMS?

LUFS is a time-averaged loudness measurement, like RMS, with two fixes that make the average match your ears. If you grew up watching an RMS meter, you already understand LUFS — both average the signal's level over time instead of chasing peaks.

LUFS is frequency-weighted. Your ears don't hear all frequencies as equally loud, so the measurement runs through a filter curve (called K-weighting) that tips the scale toward what humans actually perceive — a bit more sensitivity up top, less rumble counted down low.

LUFS is gated. Silence and near-silence get thrown out of the average. An RMS reading of a track with a long quiet intro is dragged down by the intro; the LUFS integrated reading excludes blocks below its gates. LUFS is used for loudness measurement; platform playback targets and normalization behavior differ.

LUFS, LKFS, LU — same thing

LUFS and LKFS are the identical unit with two names — the broadcast standard says LKFS, the music world says LUFS. And 1 LU = 1 dB, exactly. If a reading moves by 2 LU, the level moved by 2 dB. There is no conversion to memorize.

What do momentary, short-term and integrated loudness mean?

They are three clocks on the same signal: momentary averages the last 400 milliseconds, short-term the last 3 seconds, and integrated everything since the last reset. Use integrated to compare the measured program with a target; momentary and short-term show changes while the music plays.

Integrated is the headline; M and S live underneath it.

Momentary is the last 400 milliseconds — it jumps with every drum hit, and it's the number you watch when something spikes.

Short-term is the last 3 seconds — the loudness of the section you're in. When people say "the chorus is 4 dB hotter than the verse", short-term is the number they compared.

Integrated is the gated average of everything since you last hit reset. It describes the audio measured so far. For a whole-track result, measure the complete track; an early reading describes only the opening passage. Playback normalization depends on the platform, player and settings.

All three clocks at once, live: the bright line is momentary, the filled area is short-term, the dashed line is the target — and the histogram underneath is quietly filing every second away.

One habit that will save you from bad readings: integrated loudness is cumulative, so reset before you measure. If you start a measurement mid-track, or leave the meter running across three different songs, the integrated number describes that whole accumulated mess, not your track.

What is true peak, and why is it not the peak in your file?

True peak (dBTP) is the highest level the reconstructed analog waveform reaches between your samples — which can be higher than any sample in the file. A sample meter reads the samples; true peak oversamples the signal the way the standard specifies and reads what the listener's converter will actually produce.

The numeral holds the session max; L / R follow the signal live.

A normal peak meter reads the highest sample in your file. But the analog waveform your listener hears is reconstructed between those samples, and it can swing higher than any of them — a file that reads −0.1 dBFS on a sample meter can genuinely exceed 0 in reconstruction.

This matters because of what happens after you upload: lossy encoders (AAC, Ogg, MP3) reshape the waveform slightly and can push peaks up to a dB or so higher. A master that "never clips" on a sample meter can distort on the listener's phone.

Check the destination's true-peak guidance

Spotify recommends keeping true peak below −1 dBTP, or below −2 dBTP for masters louder than −14 LUFS. Treat these as Spotify's guidelines, and check the requirements for your destination. A true-peak limit does not guarantee the result of every codec or playback system.

What does LRA (loudness range) tell you?

Loudness range measures how spread out your short-term loudness is over the session, in LU. A dynamic live set might read 15 LU; a brickwalled master reads 3–5. Neither is "correct" — LRA is a description, not a grade — but it tells you instantly which kind of track you're looking at.

One caveat the meter should tell you itself: LRA is statistical, so it needs about a minute of program before the number means anything. A good meter flags the reading as settling until then instead of showing you a confident wrong answer.

The histogram: where your mix actually lives.

The distribution histogram under the graph is the fastest way to see LRA: every second of short-term loudness files into a bin, so over a session it becomes the honest answer to "where does this mix live?" A twin-peaked histogram is a set with two levels. A single narrow spike is a master with one. The dashed brackets show the range the LRA calculation actually keeps — the extremes outside them are deliberately discarded by the standard.

If dynamics are the part you care about, there's a whole companion post on PSR, PLR and LRA — including the one threshold worth memorizing.

Can you measure a whole file without playing it through?

Yes. Drop an audio file onto the Loudness tab, or click ANALYZE FILE, and BeamTracer measures the entire track on your machine: integrated, true peak, LRA and the full history, from start to finish. Processing time depends on the file and your computer. It is the reliable way to get an integrated number, because an offline pass can never be contaminated by a mid-track start or a forgotten reset.

Is there a free loudness meter that runs without installing anything?

Yes. BeamTracer's Loudness tab runs in Chrome or Edge, with its views, target presets, file analysis and exports free. If you prefer a meter inside a DAW, Youlean Loudness Meter is available as a standalone application and plugin on Windows and macOS.

WorkflowYoulean Loudness MeterBeamTracer Loudness
Integrated loudness, true peak and LRAFreeFree
Analyze a dropped audio fileProFree
Target presetsFilm, TV and gaming in Free; streaming presets in ProFree platform presets
Export measurement reportsPDF, PNG or SVG in ProCSV or JSON, free
Runs without installing softwareNo: application or pluginYes: browser tab

Youlean's feature list was checked October 12, 2026. Its Pro report formats differ from BeamTracer's data exports. Stock DAW meters vary by product and version, so check your DAW's documentation for offline analysis and export support. BeamTracer reads audio you can get into a tab, including a file you drag onto the meter.

BeamTracer reports loudness using the ITU-R BS.1770 and EBU R128 standards. Compare the same complete track with the measurement reset, then choose the workflow that fits your session.

How do you measure a track's loudness in BeamTracer?

Open the Loudness tab, start audio, and read M, S and I as they settle; click ANALYZE FILE when you want the whole-track answer instead of a live pass. Pick your platform in the TARGET card so every reading is judged against it, then export the session as CSV or JSON.

  1. Open the Loudness meter — the Loudness tab of BeamTracer's Audio Analysis Engine, free, no account
  2. Start audio: the bundled demo track, a file of your own, or your microphone
  3. Watch M and S move, and measure the complete track for a whole-track I result
  4. Click ANALYZE FILE, or drop a track onto the tab, for the whole-file reading — integrated, true peak, LRA, all of it
  5. Pick your platform in the TARGET card and the whole meter judges against it — verdict colors, the target band on the graph, the counters
  6. Press RESET before any live measurement you intend to keep, because integrated loudness accumulates until you do
  7. Export the session as CSV or JSON, or use COPY for a numeric summary you can paste into notes or a client email

The question-mark button knows where you are

Every reading on the meter is documented — the help button in the corner of the Analysis Engine opens the full Loudness reference for whichever tab you're on, so you never have to leave the meter to look something up.

Next

Open a broadcast-grade loudness meter in your browser. Free, no install, no account.

OPEN THE LOUDNESS METER →

Get BeamTracer updates by email

Email me

At most one email a day and three a week across both. No spam. Unsubscribe anytime.

We email a link to confirm first. Every email has an unsubscribe link. See our Privacy Policy.