Notification cues succeed when they're instantly recognizable, short, and consistent across a product. Use the guide below to choose a clip from the library or write prompts that control attack, pitch, and tail so the sound reads clearly without becoming annoying over time.
Match the sound to the action
Start by naming the UI event. "Message received" should feel different from "error" or "success". In prompts, state the intent first, then describe the timbre.
- Success: bright, stable pitch, smooth decay (ding/chime)
- Info: neutral beep or soft pop with low intensity
- Warning: sharper transient, slightly higher loudness, shorter tail
Control attack and tail for clarity
A great notification reads in the first 100–300 ms. Too much ring or ambience can overlap the next UI element and smear timing.
- Ask for "crisp attack" when you need precise sync to animation
- Ask for "short decay" to prevent stacking during rapid notifications
- Avoid heavy reverb unless it's a deliberate brand choice
Choose pitch and brightness that won't fatigue
Very bright tones cut through noise, but repeated exposure can become tiring. Use pitch and EQ language in prompts to land the right balance.
- For calm products: mid pitch, softened highs, gentle transient
- For busy environments: slightly brighter attack, but keep duration short
- If it feels harsh, request "less high-end" or "warmer tone"
Design for real playback conditions
Notifications must work on phone speakers, earbuds, and laptop speakers. Keep the stereo image sensible and avoid sub-heavy thumps that disappear on small devices.
- Use narrow stereo or mono for system-like beeps
- Reserve wider stereo shimmer for premium or celebratory cues
- Avoid deep low-end rumble; it muddies and often won't translate
