Stream alerts are the pop-up graphics and sounds that fire when someone follows, subscribes, cheers, or donates. Done well, they reward your audience in the moment and nudge lurkers to interact. Done badly, they blast ear-splitting sounds over your game or spam the screen. This guide walks through building alerts that feel exciting without wrecking your audio or your pacing.
How alerts reach your stream
Alerts are served as a browser source. You sign into an alert service, it gives you a unique browser source URL, and you paste that URL into OBS as a source layered on top of your scenes. When an event happens on your platform, the service pushes the animation and sound to that URL in real time, usually within one to three seconds.
Browser source settings that matter
Set the browser source resolution to match your canvas, commonly 1920×1080, so the alert positions correctly. Enable “Refresh browser when scene becomes active” only if alerts fail to load, and leave “Shutdown source when not visible” off so alerts do not miss events while the scene is hidden.
Tuning alert volume and length
The most common mistake is alerts that are far louder than the game. Set a target loudness and keep every alert near it.
| Element | Recommended range | Why |
|---|---|---|
| Alert sound peak | -12 to -6 dB | Noticeable but not startling |
| Alert duration | 3 to 6 seconds | Long enough to read, short enough to not stall |
| Follower alert queue | 1 to 2 second gap | Prevents raid spam pile-ups |
| Text on screen | 2 lines max | Readable at a glance on mobile |
Different alerts for different events
Give bigger events bigger reactions. A follow might get a soft chime and a small banner, while a gifted-subs bomb deserves a louder sound and a full animation. This hierarchy trains viewers to recognize the value of each action without you saying a word. Keep follows subtle because they fire most often; if every follow triggered a five-second fanfare, a busy raid would bury your gameplay.
Handling raids and hype trains
During a raid you can receive dozens of follows in seconds. Enable an alert queue with a short delay, or set a “raid” alert that summarizes the incoming viewers in one animation instead of firing hundreds of individual pop-ups. Most services let you cap the queue so a burst does not lock up your overlay for minutes.
Testing before you go live
Every alert service includes a test button. Fire each alert type at least once while watching your audio meters and your on-screen layout. Confirm the sound sits below your game and voice, the text is not clipped off the canvas edge, and the animation clears before the next event. Five minutes of testing prevents an embarrassing surprise during your first big moment.
Frequently asked questions
Why are my alerts delayed by several seconds?
Some delay is normal because the event travels from the platform to the alert service to your browser source, typically one to three seconds. Longer delays usually mean a slow browser source, too many overlay sources competing for resources, or an upload connection near its limit. Trim unused browser sources and confirm your upload speed is stable.
Can viewers hear alert sounds if I only hear them in headphones?
Only if the alert audio is routed into the stream. Set the browser source’s audio monitoring to “Monitor and Output” so both you and your viewers hear it. If it is set to “Monitor Only,” you will hear the sound but your audience will not.
Keeping alerts fresh over time
Alerts that never change fade into background noise for your regulars. Rotating a variant sound or a seasonal animation every few months keeps them feeling special without confusing your audience. Many creators also add milestone alerts, a bigger celebration for a hundredth subscriber or a large gifted-subs bomb, so rare events feel genuinely rare. Just keep the loudness discipline consistent: a milestone can be more visually dramatic without being louder than your other alerts. It is also worth building a personal reaction routine. Alerts do the visual work, but your spoken thank-you is what actually converts a one-time viewer into a regular, so leave a beat after each alert to acknowledge the person by name. Treat the alert as a cue for you, not a replacement for you. The graphics get attention; your genuine response is what makes people want to support you again.
Bottom line
Good alerts are a layered browser source with sounds kept around -12 to -6 dB, durations of three to six seconds, and a clear hierarchy that makes subs feel bigger than follows. Add an alert queue for raids, test every event type before going live, and your alerts will celebrate your community instead of blowing out their eardrums.
