How to Add Sound Effects to Your Twitch Stream Alerts

A Twitch alert sound is the only audio in a stream that interrupts the streamer mid-sentence without apology. It fires when a viewer follows, subscribes, donates bits, or raids, and it plays over whatever is already happening. That makes alert sound design a different problem from game sound design. The sound has to be recognizable, brief, and loud enough to register without being loud enough to hurt.

This guide covers the full process: choosing a platform, configuring the alert, adding it to OBS, sourcing or creating the sound itself, and getting the volume balance right so the alert does not blow out your microphone or your viewers' headphones.

The sound design principles behind short, clear alert sounds are the same ones that apply to UI and interface sounds. An alert is a notification, and it follows the same rules: short, distinct, and consistent with the channel's identity.

Step 1: Choose Where Your Alerts Live

Twitch does not have a built-in alert sound system. The alerts come from a third-party service that connects to your Twitch account and delivers the visual overlay and the audio together through a browser source in your streaming software.

The three services that cover most streamers are:

• Streamlabs is the most widely used. It offers an Alert Box with a built-in sound library, custom upload, and per-event configuration. The free tier covers follows, subs, donations, and bits, and the settings are available both from the web dashboard and from Streamlabs Desktop.
• Sound Alerts is a lighter alternative focused specifically on sounds. It integrates with OBS through a browser source and provides a community library of alert sounds, plus a soundboard feature for viewer-triggered effects.
• StreamElements offers an AlertBox widget with similar configuration options, integrated into its broader overlay editor.

For a streamer who is setting this up for the first time, Streamlabs is usually the simplest starting point because the workflow is well documented and the free tier covers the common alert types. The platform choice is not permanent; the alert sound files themselves can be moved between services if the streamer switches later.

Step 2: Configure the Alert Sound in the Dashboard

The alert sound is configured per event type. A follow alert can use a different sound from a subscription alert, which can use a different sound from a bits alert. This is deliberate: the sound communicates the importance of the event, and the importance varies.

In Streamlabs, the configuration flow is:

1. Open the Alert Box settings from the Streamlabs dashboard.
2. Select the event type to customize. Twitch Follows, Twitch Subscriptions, Twitch Bits, and Twitch Raids are the common ones.
3. Scroll down to the Sound section.
4. Click the upload arrow icon to open the sound gallery. There are two options: select a stock sound from the built-in library, or upload a custom file.
5. For a stock sound, use the search bar or category filters to find a suitable sound. The library includes both free and premium options.
6. For a custom sound, select Uploads and drag the file into the upload area, or browse for it on the computer. WAV, MP3, and OGG are the common supported formats.
7. Click Save Settings at the bottom of the page.

The same process applies to Sound Alerts, though the interface is organized differently. The sound is selected from the community library or uploaded as a custom file, and then assigned to a specific alert event type.

The critical detail that streamers miss is that the Save Settings button is at the bottom of the page, below the visible area on most screens. Changes that are not saved do not apply, and the alert will continue using the previous sound.

Step 3: Add the Alert to OBS as a Browser Source

The alert audio is not a separate file that gets imported into OBS. It is delivered by the browser source widget that also contains the visual overlay. When the browser source is configured correctly, the audio comes with it automatically.

The steps in OBS are:

1. Copy the alert widget URL from the streaming service's dashboard. In Streamlabs, this is the Widget URL under the Alert Box section.
2. In OBS, click the plus sign in the Sources panel and select Browser.
3. Name the source something recognizable, like "Alerts."
4. Paste the widget URL into the URL field.
5. Set the width and height to match your canvas, usually 1920 by 1080.
6. Check the box labeled Control audio via OBS. This is the step that makes the alert audio appear as its own channel in the OBS audio mixer. Without it, the audio plays but cannot be adjusted independently.
7. Click OK.

The browser source is the entire mechanism. There is no separate audio source to create, and the alert sound will not appear as a file in the OBS media sources. Getting the browser source right is the whole job.

After the source is added, right-click the browser source in the audio mixer and open Advanced Audio Properties. Set the Audio Monitoring to Monitor and Output if you want to hear the alert in your headphones as well as sending it to the stream. Setting it to Monitor Only will mute the alert on stream, which is useful for testing but wrong for normal operation.

Step 4: Source or Create the Alert Sound

The sound itself is where most of the design decisions happen. The alert has to be recognizable, brief, and consistent with the channel's tone.

There are three sources for alert sounds.

Built-in library sounds. Streamlabs and Sound Alerts both provide stock sounds that are free to use. These are the fastest option and they are professionally produced. The tradeoff is that they are widely used, and a viewer who watches several streams may recognize the same alert sound on multiple channels.

Downloaded royalty-free sounds. Free sound libraries offer alert-appropriate sounds with clear licensing. The free sound effect sources guide covers the licensing terms to check. The advantage over built-in libraries is that the sound is less likely to be recognizable from other streams.

Custom generated sounds. A browser-based generator like SfxMaker produces a short, unique alert sound that no other streamer is using. The design follows the same principles as a UI notification: a short tone, a fast attack, a quick decay, and a pitch or interval that matches the intended emotional character. A follow alert might use a two-note upward interval, like a coin pickup, while a subscription alert might use a slightly longer three-note phrase.

The design considerations for these short sounds are covered in How to Make Game Sound Effects and How to Create a Coin Sound Effect. An alert is essentially a reward sound for the streamer, and the same shape that makes a game reward feel satisfying makes an alert feel satisfying.

Step 5: Design Considerations Specific to Alerts

An alert sound has a different job from a game sound effect, and a few design rules follow from that.

Keep it short. Three seconds is the practical maximum for most alerts. Longer than that, the sound is still playing after the streamer has already acknowledged the alert and moved on. For high-frequency events like follows, one to two seconds is better.

Start with the sound, not with silence. An alert that fades in over 300 milliseconds feels late. The sound should begin immediately at full attack, the same way a game notification does.

Use a distinct pitch range. The alert needs to be distinguishable from the game audio and the streamer's voice. A sound in the upper midrange cuts through a mix better than a low-frequency one, which means it can be quieter while still being audible.

Match the emotional weight to the event. A follow is a small event. A large donation or a raid is a larger one. Using the same sound for both flattens the feedback. A simple two-note interval for follows, a longer ascending phrase for subscriptions, and a more celebratory sound for large donations or raids is a reasonable hierarchy.

Avoid sounds that are annoying at the tenth playback. An alert sound that is charming once can become grating after twenty follows in an hour. The sounds that survive repetition are the ones with clean tones and no harsh high-frequency content. A square wave alert is more likely to fatigue than a sine or triangle wave one.

Step 6: Set the Volume Correctly

Alert volume is the most common source of problems. An alert that is too quiet disappears under the game audio. An alert that is too loud spikes over the microphone, startles viewers, and can clip the stream's audio.

The target is a level where the alert is clearly audible against the game audio but does not exceed the loudest point of the streamer's voice. In the OBS audio mixer, the browser source channel that carries the alerts should sit noticeably below the microphone channel.

A reasonable starting point is:

• Microphone: peak around -6 dB.
• Game audio: peak around -12 dB.
• Alert sounds: peak around -15 to -18 dB.
• Background music: peak around -20 dB.

These are not universal values. Every stream has a different audio balance depending on the game, the microphone, and the streamer's voice. The important point is that the alert sits in its own place in the mix, and that place is below the microphone.

The alert volume can be adjusted in two places: the volume slider on the browser source channel in OBS, and the volume setting inside the alert platform's dashboard. Adjusting at the OBS level is faster for quick fixes, but adjusting at the dashboard level is the right approach for a permanent change, because it applies across all the scenes where the alert might appear.

Step 7: Test Before Going Live

Every alert platform has a test button. Use it. The test button fires the alert exactly as a real event would, which means the visual overlay appears, the sound plays, and the audio meter on the browser source channel moves.

Watch the meter when the test fires. If the meter does not move, the audio is not being routed correctly, and the most likely cause is that Control audio via OBS was not checked when the browser source was created.

Listen to the alert through the same headphones that will be used during the stream. A sound that is audible in a quiet room at full volume can disappear during gameplay with commentary. The alert needs to be tested under conditions that approximate the stream.

Test each event type separately. A follow alert and a subscription alert may have different sounds and different volume settings, and a problem with one does not necessarily apply to the other.

The final test is a simulated stream. Start OBS, play a game with audio, and talk over it. Then trigger a test alert and listen for whether it cuts through. If the alert is audible but not jarring, the balance is right. If it makes you flinch, it is too loud.

Common Problems and Fixes

The alert appears but there is no sound. The most likely cause is that Control audio via OBS was not checked when the browser source was created. Delete the source and recreate it with the checkbox enabled. The second most likely cause is that the alert sound was muted in the platform's dashboard, which some services expose as a separate mute toggle.

The alert sound is too quiet on stream but audible in headphones. The Audio Monitoring setting in Advanced Audio Properties is set to Monitor Only instead of Monitor and Output. Monitor Only routes the audio to the headphones but not to the stream.

The alert sound plays twice. The browser source has been added to OBS more than once, or the alert is being delivered both through the browser source and through a separate desktop audio capture. The fix is to remove the duplicate source.

The alert sound is not the one that was configured. The Save Settings button was not clicked after changing the sound. Go back to the dashboard, confirm the sound is selected, and save the settings.

The alert volume changes between scenes. The browser source has different volume settings in different scenes, or the scene has a different audio mixer state. The alert should be added to a scene that is consistent across the stream, or the audio settings should be checked for each scene.

What to Check Before Going Live

The checklist before a stream with new alert sounds:

• Each event type has the intended sound assigned. Follows, subs, bits, raids and donations should be checked individually.
• Each sound has been tested through OBS, not just through the platform's preview. The platform preview does not reflect the OBS mix.
• The alert volume is below the microphone level. An alert that is louder than the streamer's voice will spike the stream audio.
• The browser source appears in the OBS audio mixer. If it does not, Control audio via OBS is not enabled.
• The sound does not clip or distort. A sound that was normalized to 0 dB can clip when played through the browser source. Leave headroom.
• The sound is short enough not to overlap with the next event. In a busy stream, alerts can fire in quick succession. A sound that is still playing when the next alert fires will overlap.

Alert sounds are a small part of a stream's audio, but they are the part that the audience associates most directly with the channel's identity. A distinctive alert sound becomes recognizable, and a well-designed one reinforces the channel's tone every time it plays. The technical setup is not complicated, but the design decisions about the sound itself are worth the same care that goes into any other audio the audience hears.