> ## Content Index > Fetch the complete content index at: https://soundforgepro.com/llms.txt > Use this file to discover other available public pages before exploring further. # Streaming Loudness Standards: What Platforms Publish - URL: https://soundforgepro.com/streaming-loudness-standards/ - Published: 2026-08-26T06:12:45.000Z - Updated: 2026-09-04T21:30:34.000Z - Description: Separate master loudness, upload requirements, distribution gain and listener playback before choosing a LUFS or true-peak reference. - Author: Erick Finn - Tags: Mastering **There is no universal streaming loudness standard.** Spotify publishes a −14 LUFS Normal playback reference for music. Apple documents Sound Check but does not state one public LUFS delivery target on its current consumer page. YouTube publishes codec, channel and sample-rate guidance, but its current upload documentation does not declare a −14 LUFS requirement. Those differences are not trivia. A master loudness, an upload specification, a distributor’s normalization target and the level a listener gets from a particular device are four separate facts. A chart that puts all four under one “platform target” heading looks useful and can still send you in the wrong direction. **Practical answer:** keep a clean high-resolution master, follow any written delivery specification, measure Integrated LUFS and true peak together, and verify the encoded file. Treat a platform’s playback number as evidence about gain behavior, not permission to crush every master to that number. ## Streaming loudness guidance at a glance Swipe horizontally to compare every column → | Service or standard | Published loudness information | True-peak information | What it actually governs | | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | [Spotify music](https://support.spotify.com/bi-en/artists/article/loudness-normalization/) | Normal −14 LUFS; Premium Loud −11 and Quiet −19 | Mastering guidance: below −1 dBTP at −14 LUFS; below −2 dBTP when louder than −14 | Playback normalization and mastering advice, not a universal upload rejection threshold | | [Apple Music Sound Check](https://support.apple.com/en-ie/109331) | Normalizes songs toward a similar playback loudness; no public numeric target on the current consumer page | Apple Digital Masters asks for a clean, auditioned encode rather than publishing one consumer-page ceiling | Optional playback matching plus a separate mastering/delivery workflow | | [YouTube upload guidance](https://support.google.com/youtube/answer/1722171?hl=en) | No public LUFS upload target stated on the current encoding page | No numeric true-peak upload ceiling stated there | MP4 video, AAC-LC/Opus/Eclipsa Audio, stereo and 48 kHz format guidance | | [AES77-2023](https://aes.org/publications/standards-store/) / public AESTD1008 | Distribution guidance varies by content: public TD1008 examples include −18 assorted/speech, −16 track-normalized music and −14 album-loudest-track | Public TD1008 recommends no more than −1 dBTP at lossy codec input | Industry guidance for distributors, not a promise that every consumer service implements it | | [EBU R 128 S2 v3](https://tech.ebu.ch/docs/r/r128s2.pdf) | −23 LUFS unchanged with correct metadata; interim −20 to −16 LUFS may be used without metadata | Device-side true-peak limiting where a higher playback target leaves insufficient headroom | Broadcaster streaming and reproduction strategy | The useful column is the last one. Spotify’s figures describe music playback behavior and related mastering advice, EBU R 128 S2 covers a broadcaster’s streaming system, and AES77 is a distribution recommended practice. YouTube’s public page describes upload encoding. These aren’t interchangeable specifications. ![Spotify, Apple Music and YouTube loudness documentation status with published and unpublished LUFS guidance](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/platform-status-map.webp) Spotify publishes numeric music-playback levels. Apple documents Sound Check without a public consumer LUFS target. YouTube’s current encoding page does not publish a −14 LUFS upload target. ## Master, upload, distribution and playback are different stages Start by naming the stage attached to a number. Your master might measure −10 LUFS. A distributor may store that file unchanged, write loudness metadata, or calculate a gain offset. The player may then apply that offset, ignore it, offer several normalization modes or change behavior by device. ![Four-stage loudness chain from master and upload through distribution metadata to device playback](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/loudness-pipeline.webp) A single LUFS value cannot describe the master, delivery file, distribution process and listener playback at the same time. Spotify provides an unusually clear example. Its current artist documentation says Normal playback adjusts music to −14 LUFS under ITU 1770\. It measures during upload but applies normalization during playback. The same page says the web player and third-party devices such as some TVs or speakers do not use that normalization, so playback can vary. Apple’s current Sound Check support page is clear about the feature and deliberately less numeric: Sound Check adjusts loudness between songs so they play at a similar volume. That supports the statement “Apple Music can normalize playback.” It does not support “Apple rejects anything that is not −16 LUFS.” YouTube’s current recommended encoding page names MP4, AAC-LC or Opus, stereo and 48 kHz. It doesn’t state a universal LUFS upload target. Third-party measurements can describe observed playback, but observation isn’t the same as an official delivery requirement. If the official page doesn’t publish −14, don’t write −14 into a client specification with YouTube’s name attached. ## What Spotify’s −14 LUFS number does—and does not—mean On Spotify’s Normal setting, a −9 LUFS track needs roughly −5 dB of playback gain to land near −14 LUFS. A −14 LUFS track needs no loudness gain move. A −18 LUFS track could theoretically receive up to +4 dB, but available headroom can prevent the full lift. ![Loud, matched and quiet masters showing Spotify-style gain changes toward minus 14 LUFS with true-peak headroom](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/normalization-gain.webp) Normalization changes playback gain, not the balance, compression or distortion already printed into the master. Spotify states that louder material is turned down without adding distortion. For softer material, it considers headroom and leaves 1 dB for lossy encoding; its example stops a −20 LUFS file with a −5 dBFS true peak at −16 LUFS rather than forcing it to −14\. Premium users can also select Loud at −11 or Quiet at −19 LUFS. Loud mode uses a limiter, while the web player and some third-party playback paths remain exceptions. So “master everything at −14” is not the lesson. A dynamic master below −14 may remain below the nominal target when positive gain would run out of headroom. A dense master above −14 is normally attenuated. Neither outcome repairs an over-limited mix. ## Apple Music and YouTube: document the unknowns ### Apple Music Apple documents that Sound Check can match playback loudness and can preserve album relationships. Its [Apple Digital Masters technology brief](https://www.apple.com/vn/apple-music/apple-digital-masters/docs/apple-digital-masters.pdf) tells engineers to avoid clipping, use the supplied AAC audition tools and listen to the encoded result. It also frames loudness as a creative decision. That is stronger production advice than copying an unofficial Apple target from a comparison chart. ### YouTube YouTube re-encodes uploads. Its public guidance asks for high-quality source material and currently recommends AAC-LC, Opus or Eclipsa Audio at 48 kHz for the relevant upload workflow. A measured “content loudness” value in a player can help diagnose a specific video, but it does not turn a community rule of thumb into a published upload standard. For either service, write the evidence status next to the number: *officially published*, *observed in playback*, *client requirement* or *house target*. If you cannot name the status, the number is not ready for a delivery sheet. ## Where AES77 and EBU R 128 S2 fit [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en) defines how programme loudness and true peak are measured. It doesn’t choose one creative master level for Spotify, Apple Music and YouTube; AES and EBU documents build distribution strategies on top of those measurements. AES77-2023 is the current recommended practice for internet audio streaming and on-demand distribution. The freely available [AESTD1008 technical document](https://aes.org/wp-content/uploads/2024/01/20210924%5FTD1008%5Fv3.13.pdf) shows why a single number is inadequate: its table distinguishes assorted speech-anchored content at −18 LUFS, track-normalized music at −16 and album-loudest-track normalization at −14\. It also recommends a maximum true peak no higher than −1 dBTP at the input to a lossy codec. EBU R 128 S2 v3 addresses broadcasters moving −23 LUFS programmes into streaming. It recommends unchanged −23 LUFS streams with correct loudness metadata. Where metadata is not used and the broadcaster wants to control dynamic treatment, it permits an interim distribution range of −20 to −16 LUFS. That is a system design, not evidence that an independent music master must be −23. ## True peak is the second half of the decision Integrated LUFS tells you the measured programme loudness. [True peak estimates reconstructed peaks between samples](https://soundforgepro.com/true-peak-explained/). A gain move that raises loudness also raises true peak by roughly the same amount until a limiter intervenes. Spotify’s current mastering guidance says to keep a −14 LUFS master below −1 dBTP and a louder master below −2 dBTP because louder material is more susceptible to distortion after encoding. AES TD1008 recommends no more than −1 dBTP at the lossy codec input. These are defensible references, but the written destination specification still wins. ![Browser LUFS meter showing integrated loudness, estimated true peak, loudness range and sample peak](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/lufs-meter-results-real-1.webp) Measure Integrated LUFS and true peak together. The meter result describes the file; it does not tell you which platform rule applies. The [SoundForgePro LUFS Meter](https://soundforgepro.com/lufs-meter/) can measure a local file in the browser without uploading the audio. Use it as a practical pre-check. If a contract requires a certified meter or a named measurement mode, follow that specification. ## A six-step streaming loudness workflow ### 1\. Name the exact destination and content type Music track, album, [podcast](https://soundforgepro.com/podcast-loudness-standard/), live stream and video are not one delivery class. Record the platform, distributor, client and intended player path. ### 2\. Save an unconstrained archive master Keep the best lossless version before platform-specific gain, codec or limiter changes. Do not destroy the archive to satisfy a playback reference. ### 3\. Measure the complete programme Reset the meter, play the full file and record Integrated LUFS, maximum true peak and channel layout. For an album, preserve the intended relationship between tracks. ### 4\. Simulate the likely gain move Subtract measured loudness from the documented playback or delivery reference. Check whether the same gain move would push true peak beyond the relevant ceiling. ### 5\. Encode the actual delivery file Use the current codec, sample rate and channel requirements. If you need a gain correction in Sound Forge, the [Peak, RMS and LUFS normalization workflow](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates a constant gain move from dynamics processing. ### 6\. Reopen, remeasure and audition Check the encoded file, not only the lossless session. Listen to the loudest transient, a quiet passage, the opening and the ending. Where a platform offers a preview or unlisted upload, compare that playback without treating one device as universal evidence. ## Five mistakes behind bad streaming-loudness advice - **One chart, no source dates.** Platform behavior changes; every mutable row needs a current official link and check date. - **Playback target presented as upload rejection.** Gain normalization and file acceptance are different systems. - **LUFS without true peak.** Positive gain can run out of headroom, and lossy encoding can expose reconstructed overs. - **Track normalization applied to an album.** Independent gain changes can erase intended loudness relationships. - **Mastering to the loudest rumor.** Normalization cannot restore transients removed by excessive limiting. For Sound Forge’s own meter routes and reset sequence, use the [Sound Forge LUFS and true-peak guide](https://soundforgepro.com/sound-forge-loudness-meters/). That tool-specific page covers the interface; the cross-platform decision lives here. ## Streaming loudness standards FAQ ### Is −14 LUFS the standard for every streaming service? No. Spotify publishes −14 LUFS for its Normal music-playback setting, but other services document different behavior or do not publish one public numeric target. An upload requirement, distribution recommendation and playback target are not the same thing. ### Does Spotify reject music that is not −14 LUFS? Spotify’s current documentation describes measuring files during upload and applying gain during playback. Louder masters are normally turned down; softer masters may be raised only as far as headroom allows. That is not a simple −14 LUFS rejection gate. ### What LUFS target does Apple Music use? Apple publicly documents that Sound Check matches playback loudness, but its current consumer support page does not state one universal LUFS target. Follow current distributor requirements, avoid clipping and audition the encoded Apple delivery path. ### Does YouTube require −14 LUFS? YouTube’s current public recommended encoding page does not state a −14 LUFS upload requirement. It does publish format guidance such as 48 kHz audio and AAC-LC, Opus or Eclipsa Audio. Treat measured player behavior separately from an official upload specification. ### Should I master louder so streaming normalization turns the track down? Only if that sound is the artistic choice. Downward normalization changes gain; it does not undo clipping, limiting or lost transient contrast. Compare level-matched versions before choosing the denser master. ### What true peak should I use for streaming? There is no universal ceiling, but −1 dBTP is a common defensible starting point for lossy delivery. Spotify advises below −1 dBTP around −14 LUFS and below −2 dBTP for louder masters. A written platform, distributor or client specification overrides the general starting point. *Last fact-checked September 5, 2026 against Spotify for Artists, Apple Support and Apple Digital Masters, YouTube Help, AES77/AESTD1008, EBU R 128 S2 and ITU-R BS.1770-5.*