Quick answer: Aim for an overall loudness in the neighborhood of -16 to -20 LUFS with true peaks safely below 0 dB — quieter than music streaming, loud enough to not get lost — and keep your dynamic range honest. Most player complaints aren't about absolute loudness anyway: they're about the game launching at ear-splitting defaults or whispering dialogue under booming effects.
Aim for an overall loudness in the neighborhood of -16 to -20 LUFS with true peaks safely below 0 dB — quieter than music streaming, loud enough to not get lost — and keep your dynamic range honest. Most player complaints aren't about absolute loudness anyway: they're about the game launching at ear-splitting defaults or whispering dialogue under booming effects. That's the short version — the sections below get into the how, the why, and the mistakes worth dodging.
Targets, and why games sit quieter than Spotify
Music platforms normalize around -14 LUFS; games conventionally master quieter (-16 to -24 depending on genre and platform guidance) because gameplay sessions are long, dynamics matter, and players share audio space with voice chat and notifications. Measure with a free LUFS meter over real gameplay capture, not a single track in a DAW.
Peaks matter separately: leave true-peak headroom (around -1 dB) so cheap DACs and compressed streams don't clip. A limiter on the master bus is standard insurance against the one explosion that stacks every sound at once.
First launch is your loudest moment, by design failure
The classic sin: a logo sting or menu music at full scale the instant the game opens, before any settings exist. Default master volume to a polite level (many ship 70-80%), persist the player's choice, and never reset it on update. Players forgive quiet defaults; they screenshot loud ones.
Offer the sliders everyone expects — master, music, effects, dialogue — and make them work on buses, immediately, with an audible test cue while dragging.
Consistency beats calibration
Players adjust to any reasonable overall level once; what they can't adjust to is variance — cutscenes louder than gameplay, one weapon thunderous, dialogue lines recorded at different levels. Loudness-match your assets at import and spot-check new content against a reference scene before shipping it.
Then do the device tour: laptop speakers, earbuds, TV at night (consider an optional compressed 'night mode' if your dynamics are wide). Each device exposes a different failure, and together they approximate your actual audience.
Audio bugs hide better than visual ones
A missing texture is obvious in any screenshot. A sound that silently fails to load, an audio device that disconnects mid-session, or music that stops looping after an hour only shows up in real play sessions — and players almost never file a report that says 'the music stopped'. They just feel the game got worse.
It's worth capturing errors and logs from real sessions for exactly this class of bug. The problems players can't articulate are the ones your tooling has to catch for you.
Audio is half the feel of your game
Players rarely praise game audio directly — they say the game feels 'satisfying' or 'atmospheric' and can't tell you why. Sound is doing that work. A well-timed impact sound makes a weak animation feel strong; a thin one makes a great animation feel hollow.
That's why audio repays attention even on a tiny budget. You don't need an orchestra; you need the handful of sounds players hear hundreds of times — jump, hit, click, collect — to feel exactly right.
Close the loop with real players
Advice gets you to a sensible starting point; only real player behavior tells you if it worked. Ship the change, then watch what actually happens — the reports that come in, the errors that spike or vanish, the place sessions end.
Make that loop short. When a player can report a bug in ten seconds and you see it with logs attached, you stop guessing what to fix next. Tight feedback loops are the closest thing indie development has to a cheat code.
Putting it to work
Don't try to act on all of this at once. Pick the one change that costs you the least and pays the most this week, do it, and see what actually happens before reaching for the next.
Most of this rewards steadiness over intensity. A small improvement made every week, checked against how real players respond, outruns any single burst of effort — in this corner of game development and every other one.
Get the five sounds players hear most to feel perfect before touching anything else.