%20{%20%23logo%20{%20fill:%20%23ffffff;}%20}%3c/style%3e%3cg%20id='favicon'%20stroke='none'%20stroke-width='1'%20fill='none'%20fill-rule='evenodd'%3e%3cpath%20d='M43.506217,35.09997%20C50.8374542,35.09997%2060.3999374,38.6741338%2060.3999374,46.6167098%20L60.3999374,77.0368965%20L50.4390249,77.0368965%20L50.4390249,70.8416073%20C49.6421363,73.303703%2046.5343217,77.7514952%2039.9999732,77.9899948%20C29.8796709,78.3076943%2024.7,71.0003071%2024.7,64.4876185%20C24.7,56.0684333%2031.6328078,50.9057423%2040.079653,50.9057423%20L46.2952821,50.9057423%20C48.7655678,50.9057423%2050.5187047,49.4759448%2050.4390249,47.649248%20C50.2796351,44.5516334%2047.7296396,42.9631062%2043.506217,42.9631062%20C40.7171519,42.9631062%2038.1671564,44.6310733%2037.2906179,46.6961197%20L27.3296844,46.6961197%20C29.1624922,38.1975846%2036.4937293,35.09997%2043.506217,35.09997%20Z%20M76.1400098,37.7574554%20L66.314427,37.7574554%20L69.3729217,23.3222607%20C69.9084207,20.4313937%2072.6993158,18%2075.3180112,18%20C78.1089064,18%2079.7337035,20.4313937%2079.1985044,23.3222607%20L76.1400098,37.7574554%20Z%20M50.4390249,63.1373209%20L50.4390249,57.2597312%20C49.0843172,57.8156302%2047.49057,58.1333296%2045.8968228,58.1333296%20L41.6734002,58.1333296%20C39.1234047,58.1333296%2035.0593418,58.9277282%2034.5812327,63.1373209%20C34.1828034,66.6320147%2037.0515483,69.7295093%2041.6734002,69.7295093%20C46.0562126,69.7295093%2050.4390249,66.6320147%2050.4390249,63.1373209%20Z'%20id='logo'%20fill-rule='nonzero'%3e%3c/path%3e%3c/g%3e%3c/svg%3e)
Feedback sounds
Brief responses to user actions. They can acknowledge a successful operation or indicate that an input has been received. The exact meaning should be clear within the interaction.
Example — Confirmation after a completed action.
UX Sound Guide
What is UX sound?
UX sound is the deliberate use of sound within a product experience. It can communicate an event, confirm an action or direct attention to a relevant state.
The design includes both the sound itself and its behavior: when it plays, what triggers it, how often it repeats and how it works with other feedback.
UX sound and UI sound
UI sound usually refers to individual acoustic elements within an interface. UX sound considers the wider experience around those elements, including the user's task, environment and expectations.
The terms overlap. A useful project brief defines the intended interactions rather than relying on terminology alone.
Common sound types
Notification sounds
Signals that bring an event or status change to attention. Their design should reflect the importance of the event and the likely frequency of playback.
Example — An incoming message or a relevant live update.
Identification sounds
Cues associated with a product, service or transition, such as startup or connection. They can help establish a familiar acoustic identity.
Example — A device welcome sound.
Warnings and alarms
Signals associated with conditions that need attention. Urgency and required action depend on the application. In safety-related systems, terminology and signal behavior must follow the applicable requirements.
Example — A defined device fault or hazardous condition.
Voice cues
Spoken messages that convey information explicitly. They introduce language, intelligibility and localization considerations alongside the usual sound-design questions.
Example — A spoken instruction at a self-service terminal.
UX SoundPlay with sound
FeedbackSound example
A short cue acknowledging a completed action.
UX SoundPlay with sound
ConfirmationSound example
A sound marking the end of a process — here, a download.
UX SoundPlay with sound
WarningSound example
Urgency and behavior follow the applicable requirements.
Earcons and auditory icons
An earcon is an abstract acoustic cue whose meaning is established within a system. An auditory icon draws on a recognizable real-world sound to suggest an event or action.
Both need to be evaluated in context. A familiar sound in one setting may suggest something different in another.
UX SoundPlay with sound
Auditory metaphorSound example
A real-world reference suggesting meaning beyond the interface.
Principles for purposeful UX sound
Define the purpose
State what the user should learn from the sound and whether sound is useful at that moment.
Establish relationships
Related events should share understandable acoustic features. Important differences should remain distinguishable.
Match attention to importance
Duration, rhythm, timbre and playback behavior contribute to perceived prominence. Evaluate whether that prominence fits the message.
Consider repetition
A pleasant sound heard once may become distracting when repeated. Evaluate likely exposure during normal use.
Design for the real playback system
Review sound on the intended hardware and in representative environments. The delivered file is only one part of the listening experience.
Provide complementary information
Sound should work with the information users can access through other channels. Plan for people who cannot hear it or are using the product silently.
Respect user control
Define appropriate settings and playback behavior. Safety-related signals may have separate restrictions on muting or adjustment.
When silence is the right choice
An interaction does not automatically need a sound. If another channel already communicates the event clearly, an additional cue may add little value. Use sound where it supports the task.
From individual sounds to a system
A useful sound system defines meaning, relationships and behavior. It also explains how new elements can be added as the product develops.