How to Make Notification and Alert Sounds for Apps and Games

There is a specific moment in the life of a notification sound that determines whether it works or fails. It is not the first time the user hears it. It is the four hundredth time, when the user is trying to concentrate on something else and the sound interrupts them again. A notification that is pleasant once can be intolerable by the four hundredth playback, and the design decisions that make the difference are made long before that moment.

Notification and alert sounds are a distinct category from general UI sounds. A button click is triggered by the user's own action, so the user expects it and is prepared for it. A notification arrives unsolicited, at a moment the user did not choose, and it has to justify the interruption. That asymmetry is what makes notification design its own problem.

The general design principles for UI sounds are covered in How to Design Game UI Sounds, and this article assumes you already know the basics of short tonal sounds. What follows is specific to notifications and alerts: how they differ from other UI sounds, why the same two-note pattern shows up everywhere, and the parameter ranges that determine whether a sound survives the four hundredth playback.

Why Most Notification Sounds Are Two Notes

Open any operating system, any messaging app, any game with achievement notifications, and play the notification sounds one after another. A striking number of them are two-note patterns. Not one note. Not three. Two.

The reason is structural. A single note reads as a signal: something has happened. Two notes read as a phrase: something has happened, and here is what it means. The first note captures attention, and the second note delivers the emotional character. That two-stage structure is what allows a notification to be both noticeable and informative at the same time.

A one-note notification is faster, but it carries no emotional information. Every one-note notification sounds approximately the same regardless of what it is announcing. The two-note pattern is what allows a system to distinguish between a message from a friend, a calendar reminder, and a system alert without using three completely different sound designs.

Three notes are possible but rare. A three-note notification takes longer to complete, and the additional note rarely adds information that the two-note version did not already carry. The three-note pattern is more common in game reward sounds, where the longer phrase is part of the reward, than in notifications, where brevity is the whole point.

The Two Parameters That Define the Character

Once the two-note structure is in place, the character of the notification is determined almost entirely by two parameters: the interval between the notes, and the direction of the movement.

Interval is the distance in pitch between the first note and the second. It determines the emotional weight of the notification.

• A minor second or major second (one or two semitones) sounds tense and slightly unstable. It reads as an alert rather than a notification, closer to a warning than a message.
• A minor third or major third (three or four semitones) sounds soft and neutral. This is the range most messaging apps use, because it is distinct without being emotionally loaded.
• A perfect fourth or perfect fifth (five to seven semitones) sounds bright and clear. It reads as a positive announcement: an achievement, a completion, a confirmation.
• A major sixth, minor seventh, or octave (nine to twelve semitones) sounds celebratory. This is more common in game notifications than in utility apps, because it carries more emotional weight than a routine message requires.

Direction is whether the second note is higher or lower than the first.

• Upward movement reads as positive, informational, or expectant. Something is being received, added, or unlocked.
• Downward movement reads as negative, concluding, or cautionary. Something is being dismissed, lost, or flagged.
• A repeated pitch with no movement reads as neutral and clinical. It works for system messages that should not carry emotional weight, but it is also the least distinctive option.

The combination of interval and direction produces the entire emotional palette of notification sounds. A major third upward is a friendly message. A minor second upward is a warning. A perfect fifth downward is a dismissal. A major third downward is a soft negative confirmation.

Duration, Spacing, and the Difference Between Noticeable and Annoying

A notification sound has two jobs that pull in opposite directions. It has to be noticeable enough to interrupt the user's attention, and it has to be brief enough that the interruption is short.

The individual notes should each be short: 60 to 120 milliseconds. The first note is often the shorter of the two, functioning as an attention-getter. The second note can run slightly longer, up to around 200 milliseconds, to deliver the emotional character.

The gap between the two notes is the parameter that most people get wrong. If the second note starts immediately after the first, the two blur together into a single rough tone. If the gap is too long, the sound becomes a melody and starts to feel slow. A gap of 60 to 120 milliseconds is the range that keeps the two notes distinct while keeping the whole sound under 400 milliseconds.

The total duration of a notification should almost always be under half a second. A sound that takes longer than that stops being a notification and starts being an event. The exceptions are notifications that are designed to be acknowledged—a completion fanfare, an achievement unlock—which can afford to be longer because the user is expected to stop and listen.

Waveform: Why Most Notifications Avoid Square Waves

The waveform determines the basic texture of the sound, and for notifications there is a strong preference for smooth waveforms.

Sine waves are the standard for system notifications and messaging apps. They are smooth, clean, and non-fatiguing. A sine wave notification played four hundred times produces far less fatigue than a square wave with the same pitch and duration, because the square wave has more harmonic content in the high frequencies, which the ear finds more tiring over time.

Triangle waves are slightly brighter than sine waves but still smooth. They work for notifications that need to cut through ambient noise without the harshness of a square wave.

Square waves are used in game notifications, especially in retro-style games, but they are rare in utility apps. The reason is the same one that makes them useful in games: the harshness is part of the aesthetic. In a game, the harshness is a stylistic choice. In a productivity app, it is a defect.

Noise-based sounds are almost never used for notifications. A notification needs to be recognizable at a glance, and noise has no clear pitch identity. There are exceptions in games, where a noise-based alert might signal a specific event, but for apps the tonal approach is nearly universal.

Three Notification Archetypes and How to Build Them

Most notification sounds fit into one of three archetypes, and each has a specific design that works.

The Informational Notification

Used for messages, calendar events, routine system updates. The sound needs to be noticeable but emotionally neutral.

The standard design is a two-note upward pattern with a minor third or major third interval. Sine wave, first note around 70 milliseconds, second note around 120 milliseconds, gap around 80 milliseconds. Total duration around 300 milliseconds.

The pitch should sit in the upper midrange, around 800 to 1400 Hz. Lower than that and the sound competes with background audio; higher than that and it becomes piercing. A small pitch variation across repeated playbacks is not necessary for a notification, because notifications usually play one at a time and the user does not consciously hear them back to back. This is a difference from game sounds, where variation is essential.

The Positive Alert

Used for achievement unlocks, task completions, confirmations of significant actions. The sound is allowed to have more emotional weight.

The standard design is a two-note upward pattern with a perfect fourth or perfect fifth interval. The waveform can be sine or triangle. The second note can be longer, up to 200 milliseconds, to let the positive resolution land. The total duration is still under half a second.

In games, this is the same shape as a coin sound effect or an achievement unlock sound. The two-note structure and the upward motion are the same; the difference is in the duration and the surrounding context.

The Warning or Error Alert

Used for error messages, connection failures, invalid input. The sound needs to be distinguishable from notifications at the very first note.

The standard design is a two-note pattern with a minor second or major second interval, or a downward movement. The waveform can be slightly harsher—a triangle wave or a filtered square wave—to give the sound more edge. The first note is often longer than the second, which creates a sense of something ending rather than beginning.

The error alert is the one place where a notification sound is allowed to be slightly unpleasant. The point is to interrupt the user's flow, and a sound that is too pleasant does not accomplish that.

The full set of design considerations for error sounds is covered in How to Design Game UI Sounds, and the same logic applies to app notifications.

What Changes for Game Notifications

Game notifications have a different relationship with the player than app notifications have with the user, and three things change as a result.

Frequency. A game notification may fire dozens of times per session, and the player is already paying attention to the game. The sound does not have to fight for attention; it has to avoid becoming an annoyance. This pushes the design toward even shorter sounds and lighter waveforms.

Context. A game notification plays alongside other game audio, including music and effects. It has to sit in the mix without being buried, which means its frequency range needs to be considered relative to the rest of the game's sound. A notification in the same range as the footstep sound will disappear under the footsteps.

Variation. Game notifications that fire repeatedly benefit from pitch variation, the same way footsteps do. Small random shifts of a semitone or two keep the sound from becoming mechanical when it plays multiple times in a session. This is the same principle covered in How to Design Footstep Sounds for Different Surfaces, applied to notifications instead of footsteps.

Building a Notification in the Browser

A browser-based generator can produce a working notification sound in a few minutes, and the output can be used in apps, games, or any other context where a short tonal notification is needed.

The parameters that matter for a notification are the same ones that matter for any short tonal sound: pitch, duration, waveform, and envelope. A starting point for an informational notification:

• Waveform: sine or triangle
• First note pitch: around 900 Hz
• Second note pitch: a major third above the first, around 1130 Hz
• First note duration: 70 ms
• Second note duration: 120 ms
• Gap between notes: 80 ms
• Attack: under 5 ms
• Decay: fast, no sustain

This produces a two-note sound around 300 milliseconds long. Adjusting the interval widens or narrows the emotional character; adjusting the waveform changes the texture. The general approach is the same one used for game sound effects, just tuned to a different set of priorities.

Common Mistakes

• Making the sound too long. A notification that runs longer than half a second becomes an interruption rather than a signal. The exception is a completion sound the user is meant to acknowledge.
• Using a square wave in a utility app. The harshness that works for a retro game is fatiguing in a productivity app. Sine and triangle waves are the safer choices.
• Choosing an interval that is too large. An octave or more sounds celebratory, which is inappropriate for routine notifications. The minor third to perfect fifth range covers most needs.
• Forgetting the gap between notes. Without a gap of 60 to 120 milliseconds, the two notes blur into a single rough tone and lose their phrase structure.
• Using the same sound for everything. Notifications, alerts, errors, and completions all need to be distinguishable. Reusing one sound across all categories removes the information the audio is supposed to carry.
• Not testing at high repetition. A notification that sounds good once can become irritating after a hundred playbacks. The design has to be tested the way it will be heard, not in isolation.

Testing a Notification Sound

A notification is not evaluated the way a music track or a sound effect is evaluated. It is evaluated by whether it survives repetition without losing its usefulness.

Play the sound twenty or thirty times in a row. If it becomes irritating before the thirtieth playback, it will become irritating within a day of real use. The sounds that survive this test are usually the ones with clean waveforms, moderate pitch, and a short total duration.

Then play it in the actual environment it will be heard in. A notification that sounds clean in a quiet room can become fatiguing in an office, or disappear under traffic noise on a commute. The pitch and level need to be appropriate to the listening context.

Finally, verify that the sound is distinguishable from other sounds the user is likely to hear. If the notification sounds similar to the user's phone ringer, their alarm, or their calendar reminder, they will not be able to tell which device is alerting them. The sound needs to be distinctive within the user's overall audio environment, not just within the app's own sound set.