Normalize audio to streaming platform loudness targets (-14 LUFS for Spotify, -16 LUFS for Apple Music)

domain: izotope.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Measure the integrated loudness of your finished mix using a LUFS meter that implements ITU-R BS.1770 gating — tools include iZotope Insight, the free Youlean Loudness Meter plugin, or FFmpeg's ebur128 filter
  2. Determine your primary delivery target: Spotify normalizes to approximately -14 LUFS integrated; Apple Music targets approximately -16 LUFS; YouTube targets approximately -14 LUFS; platforms only turn loud tracks down, they do not boost quiet tracks to these targets
  3. Apply loudness normalization in your DAW or via FFmpeg's loudnorm filter targeting -14 LUFS integrated with a true peak ceiling of -1 dBTP — this value satisfies most major streaming platforms and provides codec headroom for AAC and Ogg Vorbis encoding
  4. Do not simply apply a limiter to hit the number — use a true-peak compliant limiter or the loudnorm filter's linear mode to avoid inter-sample peak distortion that emerges after lossy encoding
  5. For Apple Music specifically, if you want a dedicated master, target -16 LUFS integrated with -1 dBTP true peak — Apple's Sound Check feature will still normalize playback, but a quieter master may have better dynamic range preservation
  6. Export at 24-bit depth before delivery so the platform's encoder has full dynamic range to work with, even if the final consumer file will be 16-bit or lossy

Known gotchas

Related routes

Normalize audio loudness to EBU R128 using ffmpeg's loudnorm filter
ffmpeg · 5 steps · unrated
Implement two-pass EBU R128 loudness normalization with FFmpeg's loudnorm filter to hit a precise integrated loudness target
ffmpeg.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans