How to Make YouTube Louder — The Complete 2026 Guide for Any Device
YouTube too quiet? The 3 real causes — -14 LUFS, Opus codec, device ceiling — plus 8 ranked fixes, device-specific quirks, and the FAQ nobody answers.
You found the perfect tutorial, podcast interview, or music video on YouTube, but even at max volume it sounds like the creator recorded it from across the room. You crank your system volume to 100%, drag the YouTube slider all the way right, and it is still barely audible. This is not a YouTube bug — it is the predictable result of how the platform normalizes, encodes, and serves audio, layered on top of physical limits in your playback hardware. Below are the three real causes, eight ranked fixes that actually move the needle, and the device-specific quirks that determine which fix matters for you. Short on time? Skip to the TL;DR — or jump to Hearably for the browser-side fix.
Why YouTube is too quiet — the three real causes
YouTube’s volume problem isn’t one issue. It’s three independent constraints stacked on top of each other — the platform’s normalization policy, the codec it uses to deliver audio, and the physical ceiling of whatever device you’re playing on. Each one strips a few dB of headroom; together they explain why a lecture or vlog you found can stay barely audible no matter how hard you push the slider.
YouTube’s -14 LUFS normalization (it only ever turns audio down)
YouTube measures the integrated loudness of every uploaded video in LUFS (Loudness Units Full Scale) and adjusts playback gain to target approximately -14 LUFS. The critical detail almost nobody explains correctly: YouTube only normalizes down, never up. If a music video is mastered at -8 LUFS (very loud), YouTube applies roughly -6 dB of attenuation on playback. If a screen-recording tutorial sits at -28 LUFS (very quiet), YouTube applies zero gain — it stays at -28 LUFS. That’s a 14 LUFS asymmetry, perceived as roughly 4x perceived loudness difference between two videos in the same playlist.
The asymmetric policy is deliberate. Boosting quiet content would amplify the noise floor of the original recording — a vlog filmed in a coffee shop would suddenly broadcast the espresso machine at -14 LUFS. From YouTube’s risk perspective, that’s worse than leaving the audio quiet. From your perspective as a viewer trying to hear a podcast on the train, it means the platform actively refuses to help you.
The Opus codec at 128–256 kbps eats quiet dynamics
YouTube serves audio in two codecs depending on container: Opus at 128–256 kbps for WebM streams (the default on Chrome/Edge/Firefox), and AAC at 128 kbps for MP4 fallback (older Safari, some embeds). Opus is excellent — among the highest-quality general-purpose codecs available — but it’s still a perceptual codec, which means it makes lossy decisions about what to keep.
In quiet passages, perceptual coding becomes less forgiving. The codec’s bit-allocation algorithm assumes that quieter content has less perceptual relevance and assigns fewer bits to it. Combined with the bitstream’s noise-shaping behavior, the result is that whispered dialogue, breath sounds between sentences, and low-level ambient detail all sit closer to the codec’s noise floor than the original recording did. The audio you hear has subtle smearing in exactly the low-level regions where YouTube already refused to add gain. The 1080p tier on a given upload often has higher audio bitrate than 720p — checking the quality menu is sometimes worth a few perceptible dB.
Device output ceiling (laptop ~82 dB SPL, phones worse)
Even if YouTube delivered a perfectly mastered -14 LUFS stream at full quality, your hardware caps the output. Laptop speakers — physically tiny drivers in a sealed chassis — typically max out at 78–82 dB SPL at the user’s ear at one meter. That’s roughly the sound level of a busy street, which is fine for a quiet room and useless on a train, in a coffee shop, or with a window open. Phone speakers are even worse: most flagship phones hit 75–78 dB SPL, and YouTube Music on a phone tops out lower than YouTube proper because Google caps mobile playback gain to protect Bluetooth audio paths.
Headphones nominally help — wired in-ears can hit 105–110 dB SPL — but only if your source has enough drive power. Laptop headphone jacks are often current-starved for impedances above 80 ohms, so a pair of HD 600s sounds quieter on a MacBook than on a $30 USB DAC. The platform problem is loudness normalization; the device problem is wattage and SPL. The fix has to address both.
The 8 fixes — by impact
Ordered by how much each actually helps. Number one solves 70–80% of cases for browser viewers; the rest matter for mobile, archival viewing, the audiophile path, and the cases where EQ matters more than gain.
1. Browser extension audio boost on the viewer side
If you watch in Chrome or Edge, the cleanest fix is intercepting tab audio before it hits your speakers. Hearably’s YouTube volume booster uses chrome.tabCapture to grab the decoded PCM after YouTube’s player has applied its normalization, pushes it through a 3-band Linkwitz-Riley crossover with per-band gain and compression, and catches every peak with a 5 ms look-ahead AudioWorklet limiter at -0.45 dBFS. Effective gain runs to 800% with zero audible clipping. A lecture at -28 LUFS lands at conversational loudness, a music video at -8 LUFS stays at conversational loudness, the 14 LUFS gap collapses to 2–4 dB.
Best for: every YouTube viewer in a desktop browser. The <video> element’s 100% cap stops mattering.
2. The <video> element volume cap and how tabCapture bypasses it
YouTube’s player slider drives videoElement.volume, which is a Web platform spec that clamps to the range 0.0–1.0. There is no JavaScript API to push it past 1.0 — even if YouTube wanted to expose a “150%” slider, the browser would silently clip it. This is why every web-based “volume boost” that operates inside YouTube’s player is a lie; they can attenuate from 100%, never boost above it. The only way around the cap is to capture the tab’s audio output downstream of the <video> element (via chrome.tabCapture), apply gain in a Web Audio context that has no upper limit, and play back through a separate MediaStreamAudioDestinationNode. That’s the architecture used by Hearably and the few other serious browser audio extensions.
Best for: understanding why every fix below #1 has to live outside the player.
3. YouTube’s Stable Volume toggle (mobile and TV)
On the mobile app and most smart-TV YouTube apps, there’s a setting called Stable Volume (Settings → Audio → Stable Volume on iOS/Android; Settings → Video Quality on TV apps). When enabled, it applies real-time dynamic-range compression on top of the -14 LUFS normalization — quiet passages get pulled up, loud peaks get pulled down. The mobile feature really does help; reviewers report a 3–6 dB perceived loudness boost on dynamic content like film trailers and music videos. It is not available on the desktop web player — Google has rolled it to mobile and TV first.
Best for: mobile and smart-TV viewers watching dynamic content. Free, built-in, one toggle.
4. yt-dlp + mpv with --af=loudnorm (the audiophile archival path)
For videos you watch repeatedly, the cleanest fix is to download the source audio and process it offline. yt-dlp extracts the original Opus or AAC stream at full bitrate, and mpv --af=loudnorm=I=-16:LRA=11:TP=-1.5 applies broadcast-grade EBU R128 loudness normalization on playback. You bypass YouTube’s normalization entirely and target a loudness that fits your environment.
Best for: anything you’ll watch more than twice. Free, one-time install.
5. System-level EQ + boost (eqMac, Equalizer APO, Peace)
If the bottleneck is your OS output stage rather than the YouTube stream itself, a system-wide EQ does double duty: it boosts perceived loudness via Fletcher-Munson presence emphasis (2–4 kHz +3 dB), and it exposes a software gain stage that can push output above unity. On macOS, eqMac inserts a virtual audio device with parametric EQ and a gain slider that goes past 100%. On Windows, Equalizer APO (with the Peace GUI) does the same at the audio service level. Both apply to every audio source — fixes YouTube and every other app at once.
Best for: users who want one consistent setting across every audio source.
6. YouTube Music vs YouTube — different audio paths and lower mobile caps
The dedicated YouTube Music app on mobile applies a more conservative playback cap than YouTube does — Google’s stated rationale is EU hearing-safety regulation (EN 60065/IEC 62368-1). The cap is most noticeable over Bluetooth. The web client at music.youtube.com is identical from a browser perspective to youtube.com — same <video> element, same tabCapture access, same Hearably behaviour. If a song sounds quiet on the YouTube Music app and loud in the web player, the mobile cap is the difference.
Best for: music listeners hitting the mobile cap — switch to web YouTube Music with Hearably.
7. Quality tier matters — 1080p+ has higher audio bitrate
YouTube’s quality selector changes audio bitrate too. On most uploads, 360p/480p ship Opus at 70–96 kbps; 720p/1080p ship Opus at 128 kbps; 1080p Premium and 4K tiers ship Opus at 160–256 kbps. The bump from 96 to 256 kbps is audible on music and well-recorded podcasts through headphones. Auto-quality optimizes for bandwidth, not audio; forcing 1080p on talking-head content costs almost no data and gives noticeably better audio.
Best for: anyone watching music or speech-heavy content with headphones.
8. The DSP chain approach — what Hearably does
Gain alone amplifies everything proportionally — quiet ambient noise climbs by the same factor as voice, and the perceptual gap stays the same. The professional fix is a multiband compressor followed by a look-ahead limiter: split the signal at 250 Hz and 4 kHz with a phase-aligned Linkwitz-Riley crossover, compress each band independently (mid band gets the most attention because speech and vocals live there), feed the recombined signal through a 5 ms look-ahead limiter that catches transients before output.
That’s the signal chain Hearably runs on every YouTube tab. Mid band gets a 25% extra presence boost at high gain, exploiting Fletcher-Munson sensitivity so intelligibility climbs faster than peak level. A whispered podcast intro at -32 LUFS lands at conversational loudness; the brand bumper at the start of the next video stays at conversational loudness; the 18 dB gap between them collapses to 3–4 dB and the look-ahead limiter catches the loud transient before it hits the speakers.
Best for: anyone who watches YouTube daily across mixed content types. The only fix that scales cleanly across every video and every device.
Device-specific YouTube fixes
The right path depends on what you’re actually watching on. YouTube’s various clients all decode the same underlying streams but expose very different audio controls.
Desktop browser (Chrome / Edge / Safari / Firefox)
Chrome and Edge share Blink and a near-identical Web Audio implementation. Both support chrome.tabCapture cleanly, so a DSP extension attaches to YouTube without user-gesture issues. Safari ships its own WebKit audio stack — Web Audio API but no tabCapture equivalent and a stricter AudioWorklet sandbox, which is why audio booster extensions for Safari are rare. Firefox has Web Audio but no Chromium-style cross-tab capture API; most extensions don’t implement Firefox’s alternative. For real volume boosting, Chrome or Edge is the path that works.
Mobile YouTube app vs YouTube in mobile browser
The native YouTube app on iOS and Android uses platform audio APIs and bypasses the browser. No extensions, no Web Audio — just the in-app slider, OS volume, and the regulatory cap that limits headroom on mobile. On iOS the cap routes through the mediaplayer service and respects EU/CE limits (“raising volume above safe level may damage hearing”). Mobile web YouTube exposes the same <video> element as desktop but no mobile browser supports a tabCapture-style extension surface. For mobile-only viewing, the Stable Volume toggle (fix #3) and forcing a Bluetooth headset to A2DP are the two highest-impact moves.
Smart TV YouTube app (the locked-down path)
The YouTube app on Apple TV, Fire TV, Roku, Samsung Tizen, LG webOS, and built-in TV apps is the most constrained client. There’s an in-app slider, the Stable Volume toggle, and that’s it. On Apple TV, Reduce Loud Sounds under Settings → Video and Audio applies broad dynamic-range compression. Modern Samsung, LG, and Sony TVs expose a dialogue-clarity mode (Active Voice Amplifier, Clear Voice Pro, Dialogue Enhancer). The cleanest fix for TV YouTube is upstream: cast from a Chrome desktop tab with Hearably already attached, and the processed audio is what reaches the TV.
YouTube Music app vs YouTube Music web
Dedicated YouTube Music apps apply the same regulatory cap as the YouTube app, with the twist that the music app pre-attenuates to protect its target -14 LUFS master. If a track sounds quieter in the YouTube Music app than the same track in the YouTube Music web client, the pre-attenuation is the difference. Mobile users hitting the cap can move listening to the web client on a desktop with Hearably for a real boost.
YouTube vs Spotify normalization — same target, different downstream
YouTube targets -14 LUFS and never normalizes upward. Spotify also targets -14 LUFS on its default playback setting, but Spotify offers a “Loud” preset at -11 LUFS that does apply upward gain to quiet tracks (with a built-in limiter), and a “Quiet” preset at -19 LUFS for late-night listening. Same baseline target, very different policy. The codec story is also different: Spotify Premium uses Ogg Vorbis at 320 kbps (FLAC on the new HiFi tier), versus YouTube’s Opus at 128–256 kbps.
A track sitting at conversational loudness on Spotify Loud can sound noticeably quieter on YouTube even though both target -14 LUFS, because Spotify pushes the master up to target and YouTube doesn’t. If a song is quieter on YouTube than on Spotify, that’s the asymmetric normalization at work. The companion read is the YouTube audio normalization deep-dive, which compares LUFS targets and codecs across every major platform.
FAQ
Does disabling Stable Volume make YouTube louder? No — and the question reveals a misconception. The desktop YouTube web player does not have Stable Volume; it only exists on mobile and TV apps. On those apps, disabling Stable Volume removes the additional compression but does not undo the -14 LUFS normalization, which is platform-level and not toggleable. The toggle helps when a video has wide dynamic range and you want quiet sections lifted relative to peaks.
Why does the same video sound louder on one device and quieter on another? The streams are identical — the device’s output ceiling and codec path differ. The mobile YouTube app applies a stricter playback cap than the mobile web client; smart TVs route through TV speakers with their own EQ and AGC. The biggest single-device variable is Bluetooth (HFP/A2DP profile differences change perceived loudness by 6–10 dB).
Does YouTube Premium make audio louder? No. Premium removes ads, enables background play, and grants access to higher-bitrate streams (the 256 kbps Opus tier on some uploads), but it does not change the -14 LUFS normalization. A higher-bitrate stream is perceptibly cleaner — especially on music — but the loudness target is identical for free and Premium accounts.
Can I boost a single YouTube tab without affecting other tabs? Yes — but only with per-tab DSP. The OS mixer attenuates per-application but can’t boost beyond unity. An extension using chrome.tabCapture attaches its DSP chain per-tab, so a YouTube tab can run at 600% effective gain while a music tab stays at 100%.
Will boosting YouTube volume damage my speakers or headphones? A well-implemented look-ahead limiter prevents digital clipping, so the signal handed to your DAC and amp stays within safe bounds. The risk is acoustic: if you set a 600% gain and play a loud master, you’ll hit dangerous SPL at your ear. Safety guidelines suggest staying below 85 dB SPL for extended listening.
Does Hearably work with embedded YouTube players on other sites? Yes. Embedded players use the same <video> element and Web Audio pipeline as youtube.com. Any tab-level DSP that works on the main site works identically on embedded videos in blog posts and course platforms.
TL;DR — what to do right now
- Watching YouTube in Chrome or Edge? Install the YouTube volume booster and use the Voice or Music preset. The -14 LUFS asymmetric normalization stops being a ceiling.
- Mobile YouTube? Turn on Stable Volume in the app’s audio settings — it’s the only built-in fix that actually helps. For Bluetooth listening, force A2DP by closing any app holding the mic.
- Smart TV YouTube? Enable the TV’s dialogue-clarity mode (Active Voice Amplifier / Clear Voice Pro / Dialogue Enhancer) or cast from a Chrome desktop with Hearably attached.
- Want to compare YouTube vs Spotify or understand why they disagree on the same -14 LUFS? Read the YouTube audio normalization deep-dive.
- One-click fix for everything above? Hearably handles the boost, the EQ, the multiband compressor, and the look-ahead limiter automatically — works on every YouTube tab.
Try Hearably for free
Volume boost, live captions, noise reduction, and more — all in your browser.
Add to Chrome — Free