How to Fix Volume Differences Between Streaming Services

The volume adjustment ritual is one of the most common micro-frustrations in modern media consumption. You watch Netflix at 40% system volume. You switch to Spotify and it's quiet, so you go to 60%. You open a YouTube tab to check something and it's ear-splitting at 60%. A podcast app follows and you can barely hear it without going to 80%. Every app has a different idea of "normal," and there is no global standard they all agree on.

This isn't a settings misconfiguration. It's a fundamental mismatch between how different platforms measure and target loudness. Understanding why it happens is the first step to fixing it.

---

Why Netflix Is Louder Than Spotify (and Everything Else)

Audio engineers measure loudness in LUFS — Loudness Units relative to Full Scale. It's a perceptual measurement that approximates how loud something sounds to human ears, rather than just measuring peak signal levels. Every streaming service targets a different LUFS value, and those differences translate directly into the volume jumps you experience when switching between them.

The gap between Netflix and Spotify is the most dramatic example. Netflix targets -27 LKFS for dialogue-referenced content — that's the loudness level for the spoken word portions of a show or film. Spotify targets -14 LUFS for music. That 13-unit difference is enormous — roughly equivalent to 13 dB in perceived loudness. Music on Spotify will sound roughly twice as loud as a Netflix drama at the same system volume.

Service	Target Loudness	Standard / Notes
Netflix	-27 LKFS	Dialogue-referenced; matches broadcast TV spec (ATSC A/85)
Spotify	-14 LUFS	Music loudness norm; turns loud tracks down, quiet ones up
YouTube	-14 LUFS	Uploaded video content only; ads bypass this ceiling
Apple Music	-16 LUFS	"Sound Check" targets -16 LUFS; off by default in browser
Tidal / Amazon Music	-14 LUFS	Follows industry music loudness standard
Podcast apps (browser)	-16 to -24 LUFS	No enforced standard; entirely up to each show's producers
Twitch / live streams	No standard	Each streamer mixes independently; no platform normalization

The core problem: these services don't know about each other. Netflix optimizes for cinematic dialogue clarity. Spotify optimizes for consistent music playback within its library. YouTube normalizes uploaded video but can't touch ads. Each standard is internally consistent — and externally incompatible with every other platform you use.

---

Why Each Platform Can't Solve It Alone

You might expect each streaming service to add a setting that matches other platforms. A few have tried half-measures, but none of them solve the cross-platform problem:

Netflix: No user volume control at all

Netflix encodes audio to its -27 LKFS spec and provides no loudness adjustment in the browser player. The assumption is that you're watching at a fixed volume — the way you'd watch broadcast TV. That assumption breaks down the moment you have a Spotify tab open in another window.

Spotify: "Loudness normalization" only works inside Spotify

Spotify's built-in loudness normalization is genuinely good — it ensures a loud album doesn't blast you compared to a quiet one within the same listening session. But it only operates on Spotify's content. The moment you leave the Spotify tab, the normalization stops. Your system volume is unchanged. Netflix is still 13 LUFS quieter.

YouTube: Normalization with a gap

YouTube normalizes uploaded content to -14 LUFS, but as covered in our YouTube audio normalization guide, ads bypass this ceiling entirely and are routinely mixed 3–5 dB louder. YouTube can't fix its own ad loudness problem — let alone the gap with Netflix or podcast apps.

---

Common Workarounds (And Why They Fall Short)

OS-level volume mixer

Windows and macOS let you set per-application volume. But your browser — Chrome, Firefox, Edge — is a single application. All browser tabs share one audio stream from the OS's perspective. You can't set Netflix tabs to 80% and Spotify tabs to 50% from the OS mixer. Every tab moves together.

Soundbar or receiver "night mode"

Night mode on soundbars and receivers compresses dynamic range to keep loud moments from waking people up. It addresses extreme peaks but doesn't level out the average loudness differences between services — a Netflix dialogue scene and a Spotify track will still sound dramatically different after night mode. It's also a blunt instrument: it changes the character of music playback significantly.

Manual volume adjustment

The default approach for most people. You learn that Netflix requires 50%, Spotify requires 35%, YouTube requires 30%, podcasts require 75%. You build muscle memory around adjusting constantly. It works — but it's a tax you pay every single time you switch between apps, and it breaks the moment you use an unfamiliar service or someone else touches your setup.

None of these approaches address what's actually happening: the audio reaching your speakers has no consistent loudness ceiling or floor. The fix needs to happen between the audio stream and your speakers — in real time, regardless of source.

---

How Real-Time Browser Audio Normalization Solves This

The correct fix operates at a different level than any of the platform-level or OS-level workarounds above. Instead of trying to influence what each service sends, you intercept the audio output from the browser tab and apply normalization before it reaches your speakers. Whatever the source — Netflix at -27 LKFS, Spotify at -14 LUFS, a podcaster who never thought about loudness — everything passes through the same ceiling and floor you set.

This is technically possible in Chrome and Edge on desktop using the Tab Capture API. The browser captures audio from a specific tab, pipes it through the Web Audio API's DynamicsCompressorNode (which acts as a real-time limiter), and plays the processed signal back through your speakers. The source tab is muted automatically to prevent double-playback.

The result: every tab you capture outputs audio at the loudness level you chose — not the level each platform decided for you. Set Netflix and Spotify to the same ceiling and they'll match. No manual adjustment, no per-service memorization.

For the technical details of how dynamic range compression works at the Web Audio API level, see our deep-dive on real-time audio normalization in the browser.

---

How to Use SoundBound Across Streaming Services

SoundBound implements this approach as a browser app — no install, no extension. It runs in Chrome or Edge on desktop and normalizes any tab you point it at. Here's the setup:

1. 01
   Open SoundBound Go to soundbound.polsia.app/app in Chrome or Edge on desktop. No download or install needed — it runs entirely in the browser.
2. 02
   Set your loudness range Use the ceiling slider to set your maximum output level (−14 dBFS is a good starting point — it matches Spotify's and YouTube's normalization target). Use the floor slider to catch anything too quiet. The live meters show exactly what's coming in and what's going out.
3. 03
   Start capture — select your streaming tab Click "Start Capture." Your browser will show a tab-sharing dialog. Select your Netflix, Spotify, YouTube, or podcast tab. The source tab mutes automatically so you don't hear it twice.
4. 04
   Watch the levels, fine-tune if needed The input meter shows what the service is sending. The output meter shows what reaches your speakers — capped at your ceiling. If Netflix sounds too quiet relative to your ceiling, nudge the floor up slightly. If Spotify clips, lower the ceiling a touch.
5. 05
   Switch tabs freely — leave it running SoundBound keeps normalizing as long as it's running. Switch between Netflix episodes, jump to Spotify, check a YouTube video — everything from the captured tab stays within your range. You stop touching volume.

---

Works for Any Audio Source

Because SoundBound captures the audio stream at the tab level — not from any specific streaming service's player — it works with anything you play in a browser tab:

• Netflix, Disney+, HBO Max, Hulu — all normalized to the same ceiling you set
• Spotify, Apple Music, Tidal in the browser — music that no longer requires a volume bump after watching video
• YouTube, Twitch, live events — ad spikes caught, quiet content boosted
• Podcast players, audiobook apps — inconsistently-mixed speech content leveled out
• Any other browser tab playing audio — news sites, social video, screenshares

If you're dealing with the specific problem of loud ads on every platform, the same normalization that levels Spotify against Netflix also clips those ad spikes. And if you're a gamer managing Discord, game audio, and stream alerts simultaneously, our gaming and streaming audio settings guide covers the optimal setup for that scenario.

The underlying issue — the cumulative effect of spending hours daily with unpredictable volume spikes — is also worth understanding from a health perspective. Our hearing protection guide covers the research on safe listening levels and why normalization matters for long-term hearing health.

If you've ever wondered why streaming "normalization" doesn't prevent sudden spikes — the short answer is that normalization alone can't, only compression can. Our audio compression vs normalization explainer breaks down exactly how the two techniques differ and why you need both.

---

Stop Adjusting. Start Listening.

The volume inconsistency between streaming services isn't going away. The platforms have different business reasons for their loudness targets, they're optimized for different listening contexts, and they have no incentive to coordinate on a single standard. The gap between Netflix and Spotify isn't a bug — it's a structural feature of how separate services evolved independently.

The fix isn't on their end. It's on yours: intercept the audio before it reaches your speakers, set a ceiling and floor that works for you, and let every service output at the same level. One setting. Every platform. No manual adjustments.

---