LUFS Loudness Normalizer — Free ITU-R BS.1770 Online

LUFS Loudness Normalizer is a self-contained audio editing and conversion workspace. Normalize an audio file to a specific integrated loudness target (e.g. -16 LUFS for podcast distribution, -14 LUFS for Spotify) using the ITU-R BS.1770 measurement standard. Open the page, get the result, close the tab — that is the entire workflow.

LUFS Loudness Normalizer sees the most use from students preparing oral submissions and teachers recording lessons, but the design is intentionally generic enough that you do not need a specialist background to get a good result. The defaults aim at the most common case so a first-time user can get the right output without changing any settings.

Most people land on LUFS Loudness Normalizer via a search at the moment they actually need the tool. That shapes the design: the page is a single screen with the input on one side, the controls in the middle, and the result on the other, so a first-time visitor can complete the job without reading documentation.

Under the hood, LUFS Loudness Normalizer uses the Web Audio API to do the actual work. The tool accepts MP3, WAV, OGG, FLAC, M4A, and AAC as input, with a per-file ceiling of 200 MB so memory usage stays predictable on lower-end laptops and tablets. The engine ships as part of the page bundle, so once the page is loaded the tool keeps working even if your network connection drops.

The architecture is local-first by design. Once the page is loaded, you can disconnect from the network and the tool still completes the job. The processing stack — the Web Audio API and the small UI shell wrapping it — ships with the page itself, so the tool keeps working in offline conditions, on a captive-portal Wi-Fi, or behind a corporate proxy that limits what the tab can reach.

LUFS Loudness Normalizer is intentionally narrow in what it does, which makes it easy to slot into a longer workflow. Take its output, hand it to whichever next tool fits the job, and LUFS Loudness Normalizer stays out of your way until the next time you need it.

The only practical limit is the 200 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.

LUFS Loudness Normalizer keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.

Output handling is intentionally boring: LUFS Loudness Normalizer produces `{name}-normalized.wav` and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.

LUFS Loudness Normalizer is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.

LUFS Loudness Normalizer is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical audio editing and conversion workflow.

If you want to get the most out of LUFS Loudness Normalizer, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.

Common gotchas worth flagging: LUFS Loudness Normalizer only accepts MP3, WAV, OGG, FLAC, M4A, and AAC, so if your file is in another format you will need to convert it first. The 200 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.

If LUFS Loudness Normalizer solved your problem, sharing the page link with someone who has the same problem is the most useful thing you can do. The catalog grows mostly through word of mouth; visitors arriving through a recommendation tend to be the ones the tool serves best.