OBS Alerts: Complete Setup Guide

Which alerts to enable first

Start with the alerts that prove the workflow works: a donation alert, one subscription or follow alert, and a manual test event from the panel.

A useful alert answers three questions quickly: who triggered it, what happened, and whether the streamer can react without opening another dashboard.

Use one visual style, one audio level, and one display duration at first. Split alerts into advanced variants only after several live sessions.

Step 1: connect accounts and event sources

Confirm where events come from before tuning the design. Donations, subscriptions, follows, and panel test events should each have one active path into the alert layer.

Add the alert as an OBS Browser Source and name the source clearly. A practical starting size is 800-1000 px wide and 250-350 px high, with refresh-on-scene-activation enabled.

Run one panel test after adding the source. If nothing appears, refresh the browser-source URL or token before changing animation settings.

Step 2: set audio, timing, and readability

The alert should be audible without covering the microphone. A good starting point is between -12 and -8 dB with a short sound that does not linger.

Three to five seconds is enough for most alerts. Longer animations pull attention away from the stream and make overlapping events more likely.

Check the alert on both bright and dark scenes. Text that looks readable in a panel can disappear on a busy game feed.

Step 3: test before going live

Run a 0-to-1 test before every important stream: one donation alert, one subscription or follow alert, a scene switch, and a return to the main scene.

Measure the delay between triggering the test and seeing the alert. If it is above three seconds, refresh the browser source and remove transitions that delay rendering.

Record 30 seconds locally and listen back. The alert should not clip, hide the camera, or fire twice.

Emergency fixes

If the simulated alert does not render, check the active browser-source URL, integration permissions, and whether the event reaches the panel.

If the sound clips, lower the OBS mixer level and add a limiter. If it is too quiet, raise only the alert source instead of the whole desktop mix.

If the alert fires multiple times, look for duplicated webhooks, duplicate scene sources, or two integrations sending the same event.

What to enable after the first test

Once the basic alert is stable, connect it to a donation goal or recent activity widget so viewers see the context behind the event.

Save one production preset. Changing sound, animation, and position before every stream makes it impossible to know what improved viewer response.

After three streams, review whether alerts helped the conversation. If viewers ignore them, test copy and timing before adding more effects.

Preguntas frecuentes