Open your game. Join Discord. Someone shares a YouTube clip in the group chat. Your stream notification fires. A music bot plays in your stream lobby. Your headset is now a battlefield where six different audio sources are all trying to be the loudest thing in the room.
This is the normal state of gaming audio. And it's doing more damage to your hearing than you think.
The Volume Chaos Problem
Game audio mixes are designed for impact, not consistency. The audio engineer who mixed your FPS optimized for realism — which means gunshots are loud, footsteps are quiet, and explosions are designed to feel physically overwhelming. There's no compression pass at the end. It's mixed for theaters, not for your headphones at 11pm.
Meanwhile, Discord normalizes voice at around -19 LUFS. Game audio averages -18 to -12 LUFS depending on the title. Stream alerts are often mastered to -14 LUFS (louder than the game). Music, if you're running a background playlist, is somewhere in between.
Your volume knob can't solve this. You set it for one source, and every other source is either inaudible or a spike. The result: a volume-setting habit that's calibrated for the loudest thing in the mix — which means you're over-exposing your ears during everything else.
When you spike to 100 dB during an in-game explosion, your ears have already been at 85–90 dB from the previous 30 minutes of game audio. You're not starting fresh each spike — you're stacking cumulative exposure. The CDC threshold isn't a daily reset; it's a cumulative dose.
Why Manual Solutions Don't Work
If you've tried to solve this, you've probably gone through some version of the standard stack:
- Windows Volume Mixer — Yes, you can set per-app volumes. But the settings don't persist across sessions. Launch a new game, and it's reset to 100%. Also: Discord voice and game audio are both system-level sounds; they share a stack and you can't isolate them cleanly.
- Per-app volume in Discord — Discord has its own output slider, but it only controls Discord output — not the relative loudness between Discord and everything else. And it resets every time you restart the client.
- OBS audio filters — If you stream, you've probably added a compressor to your mic track and maybe to your game audio capture. That's great for your stream's output. It does nothing for what you hear in your headset. The stream mix and your monitor mix are separate signal chains.
- Nvidia Broadcast / other audio processing tools — These handle your mic and Discord output, but they don't touch game audio in a way that's perceptible for the mixer. And they add latency and CPU load.
The core problem: all of these solutions operate at the OS or application level, and each one only controls its own audio output. There's no tool that manages the result — what your ears actually experience after all six sources have mixed together.
What Normalization Actually Means for Gamers
In streaming, normalization means keeping content at a consistent perceived loudness — no spike to -13 LUFS when the video was recorded at -18 LUFS. For gaming, the problem is the same but the sources are different: you want every sound to stay within a range you've chosen, so your volume knob works consistently across the entire session.
The technical mechanism is the same one used in broadcast audio: dynamic range compression. A compressor detects peaks above a set threshold and scales them down in real time. What it does not do is make everything the same volume — it just puts a ceiling on the loudest parts while leaving everything else alone. This is why normalization is different from limiting: a limiter at -6 dBFS means everything at -6 dBFS or above gets smashed to -6 dBFS. A compressor with a 20:1 ratio lets it through but scaled back.
For gamers, this means: explosions get tamed without making footsteps inaudible. The jump in loudness when you tab back to Discord after a cutscene doesn't blow past your set ceiling. Your stream alerts don't make you flinch.
The ceiling is personal. For competitive FPS, you may want -8 dBFS — you want to hear everything, but you don't want a C4 explosion at full volume. For a chill stream watch-along, -12 dBFS might feel more comfortable. You set the range. The compressor enforces it.
SoundBound's Approach for Gaming Audio
SoundBound applies real-time compression to the audio output of any browser tab on desktop Chrome and Edge — which covers most of the audio sources in a gaming session: Discord web (if you're using the browser version), your stream tab, YouTube clips shared in chat, Spotify web player, and any other browser-based audio.
The audio chain is simple: tab audio capture → DynamicsCompressorNode (user-configured ceiling) → speakers. You set your floor and ceiling sliders, and everything that would otherwise spike above your ceiling gets compressed transparently before it reaches your ears.
This approach works specifically for browser-based audio, which covers a significant portion of the modern gaming setup's non-game audio. For game audio itself (the .exe process, not the browser), you need OS-level solutions like Windows Sonic or hardware-based compression. But the browser audio problem — Discord web, stream alerts, background music, shared clips — is exactly what tab capture solves.
Recommended Settings for Common Scenarios
These are starting points. Every headset, every room, every hearing profile is different. The right settings are the ones that let you set your volume knob once and not touch it again.
| Scenario | Floor (boost quiet) | Ceiling (limit loud) | Best for |
|---|---|---|---|
| Competitive FPS | -36 dBFS | -8 dBFS | Hearing footsteps without explosion damage. Tight ratio keeps game audio punchy. |
| Stream viewing | -32 dBFS | -12 dBFS | YouTube ads vs. content. Catches the -13 LUFS ad jump before it reaches your ears. See why ads are louder or how to normalize YouTube audio. |
| Discord + game simultaneously | -28 dBFS | -10 dBFS | Voice call doesn't get buried by game SFX. Game audio doesn't blast you when the call goes quiet. |
| Background music while gaming | -38 dBFS | -14 dBFS | Music stays consistent and present without competing with game audio. Wide dynamic range preserved. |
For competitive FPS, a tighter ceiling protects your hearing during intense matches without sacrificing situational awareness. Footsteps sit around -30 to -20 dBFS in most competitive titles — they won't be affected by a -8 dBFS ceiling. Explosions and gunfire (typically -10 to 0 dBFS) get caught by the compressor. You still hear everything; it just doesn't spike.
For Discord + game simultaneously, the key challenge is that Discord voice is usually mixed at a significantly lower LUFS than the game. When Discord goes quiet between transmissions, you instinctively turn up the game volume. Then Discord activates and it's too loud. The compressor doesn't fix the underlying level mismatch, but it keeps both from going to full volume simultaneously — which is where the real exposure happens.
4+ Hour Sessions and Cumulative Hearing Damage
A typical gaming session is 2–6 hours. If you're playing at 90 dB average, you're already at or past the CDC's recommended 8-hour exposure threshold. Add Discord, stream alerts, and occasional spikes to 100+ dB during action sequences, and you're stacking exposure faster than your ears can recover from.
The damage is cumulative and permanent. The hair cells in your cochlea that process high frequencies are the first to go — and they're also the ones that process speech clarity and spatial audio (which is exactly what you need for competitive gaming). Hearing protection isn't just for concerts. It's for every long gaming session where you're running at volume.
The practical fix isn't turning down the volume — it's installing a ceiling. With a compressor capping peaks at -8 or -10 dBFS, you can run a comfortable volume for the entire session without the spikes undoing your hearing over time. The quiet content stays audible. The dangerous peaks get caught.
For most gamers, start with a -10 dBFS ceiling and a -28 dBFS floor. This covers the widest range of gaming audio without making quiet content disappear. Adjust toward -8 dBFS if you play competitively and need maximum punch, or toward -14 dBFS if you're watching streams for long periods and prioritize comfort.
Setting It Up Once and Forgetting It
The goal is a volume knob that works. You set it once at the start of the session and never touch it again. Every audio source — Discord, stream alerts, game SFX, background music — sits within your chosen range. The compressor handles the rest.
This is the difference between audio normalization as a concept and audio normalization as something that actually works in your specific setup. It's not about hitting a standard — it's about making your volume knob honest again.
If the problem extends beyond gaming — switching between Netflix, Spotify, YouTube, and podcasts throughout the day — see our guide on fixing volume differences between streaming services. It covers why every platform targets a different LUFS, why none of them can solve it internally, and how one browser-level setting normalizes all of them. For the hearing science behind why volume spikes matter even during casual streaming sessions, the hearing protection guide has the research. And if the relationship between compression and normalization is still fuzzy — the compressor is what catches the peaks, normalization is what sets the target level — our audio compression vs normalization explainer makes both clear with a direct comparison.
Ready to try it? SoundBound normalizes your browser audio in real-time. No downloads, no extensions.
Stop fighting with volume controls.
SoundBound keeps your audio within your chosen dB range — YouTube, Spotify, gaming, everything. No downloads, no extensions. Works in Chrome and Edge on desktop.
Try SoundBound FreeFirst 100 users get a free trial