LUFS Loudness Checker

Free · No sign-up · Your file never uploads — a broadcast-standard loudness engine (BS.1770) runs in your browser. First use downloads the ~31 MB engine once; it's cached after that.

Target: −14 LUFS integrated and true peak ≤ −1 dBTP for YouTube. Best under ~500 MB in a browser tab.

How to read the result

Why your export sounds quieter on YouTube

You mixed it until it sounded right, exported it, and on YouTube it feels smaller than everything around it. The cause is almost never your export settings — it is normalization. YouTube measures every upload's integrated loudness and applies a gain change so playback lands near −14 LUFS. Crucially, that gain mostly goes one way: loud uploads are turned down, but quiet uploads are barely turned up, if at all. A video mastered at −22 LUFS keeps most of that gap permanently, playing noticeably quieter than the −14 LUFS video beside it — and turning the phone up just raises the noise floor along with the voice.

Loudness is also an average, not a peak. Integrated LUFS weighs the whole video, so a master with a few loud moments and long quiet passages can measure far below −14 even while its peaks hit the ceiling. Raising the master fader doesn't fix that the way creators expect: once an upload measures louder than −14, YouTube simply applies the difference as turn-down, so the perceived loudness after normalization is the same — while your true peaks get pushed closer to, or past, the −1 dBTP ceiling, where platform re-encoding starts to clip and distort. A louder master buys nothing on YouTube except lost headroom.

The fix happens in the mix, not the export: control the dynamics so quiet parts aren't too quiet, master to about −14 LUFS integrated with true peak at or below −1 dBTP, and measure the actual exported file — not the timeline — before uploading. That file is the number YouTube will judge.

Honest limits

  • This measures the file you give it. If you edit after measuring, measure again.
  • YouTube's exact normalization has undocumented edges (it differs slightly for music and Premium). −14/−1 is the professional consensus target, not a guarantee of a specific playback gain.
  • Loudness can't fix a bad recording — it only tells you the level truthfully.

What this tool cannot tell you

  • It cannot tell you how your audio will sound after a platform re-encodes it. It measures the file you hand it — the platform's processed version is a second step this measurement never hears.
  • It cannot hear quality problems: distortion or clipping baked into the recording, harsh sibilance, a muddy mix. A file can measure exactly −14 LUFS and still sound bad.
  • It cannot measure a link, a stream or a moment. It needs the actual file, and it reports the whole file's loudness — not the one loud scene you remember.
  • It cannot promise a specific playback volume in a real room. Platform normalization, the listener's device and their volume knob all sit between this number and an actual ear.

Frequently asked questions

What loudness does YouTube use?

YouTube normalizes playback to about −14 LUFS integrated. Louder uploads are turned down; quieter ones are mostly left alone (YouTube rarely turns things up much), so mastering near −14 LUFS with true peak at or below −1 dBTP is the standard target for spoken and mixed content.

What is true peak and why −1 dBTP?

True peak measures inter-sample peaks that appear after decoding — the peaks your file's samples hide. Above −1 dBTP, platform encoders (AAC/Opus) can clip and distort. −1 dBTP is the widely used safe ceiling; −2 dBTP if your content is loud and dense.

Podcasts, music, Shorts — same target?

Spoken word: −14 to −16 LUFS works (podcast platforms use −16 stereo). Music: −14 is YouTube's number, but many artists master louder for artistic reasons and accept the turn-down. Shorts are normalized on the same systems — keep them near −14 too, with true peak controlled.

Why does the measurement engine download ~31 MB once?

Broadcast-standard loudness (BS.1770) needs a real audio engine. We load the single-thread ffmpeg engine from a public CDN the first time you measure; your browser caches it for next time. Your media file itself never leaves your device — only the engine is fetched.

Is this the same measurement as my DAW's meter?

Yes — integrated loudness per ITU-R BS.1770 with the standard gating, and true peak per the same spec, computed by ffmpeg's loudnorm analysis. Small differences (±0.1–0.3 LU) between meters are normal.

Do you upload or keep my file?

No. The file is read into this tab's memory, measured locally, and forgotten when you close the tab.

Related tools

Related guides

CreatorChecks is not affiliated with YouTube or Google. Measurement engine: ffmpeg (LGPL) via ffmpeg.wasm, loaded from the jsDelivr CDN.