UI Sound Design: How to Add Sounds to an App or Game Without Annoying People
Practical rules for interface sounds: which actions deserve a sound, how loud and how long, file formats, and how to check a sound license before you ship.
Good interface sound is felt more than heard. It confirms that something happened, signals errors before the user reads them, and gives a product character. Bad interface sound gets muted in a day. These rules keep you on the right side of that line.
Only sound the moments that matter
Give sounds to actions where feedback helps: a sent message, a completed payment step, a toggle that's easy to miss, an error, a level-up. Skip hovers and scrolling in most apps. Anything that happens dozens of times a minute becomes noise.
Keep them short and quiet
- Taps and clicks: under 100 ms.
- Confirmations and notifications: around 200–600 ms.
- Play UI sounds noticeably quieter than music or speech, and give users a mute or volume setting.
Match the meaning
Rising pitch tends to read as positive or forward (success, open), and falling pitch as negative or backward (error, close). Use one consistent family of sounds rather than mixing styles from different sources.
Pick the right format
- WAV for editing and for engines that compress on import.
- OGG for games and web (small, widely supported).
- MP3 where you need universal browser playback.
Preload short UI sounds so there's no delay on the first play.
Test on real devices
Phone speakers drop the low frequencies, while headphones exaggerate everything. Check your sounds on both, at low volume, in a quiet room.
Read the license before you ship
For commercial work, confirm the license allows commercial use in your kind of project, whether attribution is required, and what's not allowed (usually reselling the raw files). Keep a copy of the license with your project files.
Or try the free sample first.
Sold by Quietcog. Support: gb1@mail.grokbot.com. General information only, not professional advice.