An err cue is tiny, but it carries meaning: denial, mistake, or warning. The fastest way to get the right vibe is to prompt the action (denied, invalid, wrong answer) and then control three levers: pitch direction, transient sharpness, and tail length. Use the tips below to choose a downloadable clip or generate a custom variation that matches your interface and timing.
Choose the intent: denied, wrong, or warning
Start by deciding what the sound should communicate. Denied actions usually feel firm and short, wrong answers can be playful or harsh, and warnings often sound lighter but noticeable.
- Denied: short, firm, often a pitch drop
- Wrong answer: buzzer edge or comic chirp, slightly louder
- Warning: softer attack with a tidy tail, less aggressive
Dial in pitch and brightness for your UI
A higher pitch reads as attention-grabbing, while a lower pitch can feel heavier or more comedic. Brightness affects how well the cue cuts through speech and music without becoming piercing.
- For friendly apps: warm tone, reduced high-end bite
- For strict system errors: brighter tone with a clean transient
- For retro menus: simple waveforms and obvious pitch steps
Match tail length to the on-screen timing
Short tails keep UIs snappy, while slightly longer sequences can reinforce multi-step failures (like invalid input followed by reset). If the error state stays on screen, consider a bed with intermittent beeps instead of a single hit.
- Quick taps: compact decay so it does not smear into clicks
- Dialog scenes: shorter tails to avoid masking consonants
- Long holds: generate a low-level bed with occasional pulses
Avoid common error-sound pitfalls
Err cues often fail because they are too harsh, too loud, or too roomy. Keep them dry and controlled so they translate across devices and do not fight other UI sounds.
- Avoid long reverb tails that make the UI feel distant
- Avoid extreme clipping or painful resonances around the high end
- Avoid wide stereo tricks that disappear in mono playback
