Five steps. No installer, no extension. A dedicated WES Alert scene with a Browser Source pointing at your private overlay URL, reused across every scene that needs alerts. Three minutes, end to end.
In the Dashboard, find the Overlay URL block. Click Show to reveal the URL, then Copy. Keep this URL private. It carries your license key.
Shared it by accident? You can rotate the URL anytime from Advanced Settings → Security. See the Security guide for what to do after a regeneration.
Don't drop the Browser Source straight into your gameplay or BRB scenes. Make one standalone scene that holds the overlay, and reuse it as a source everywhere else. One place to update, no duplicates fighting each other.
Two clicks, in order:
The Browser Source properties dialog opened when you added the source. Set it up like this. These are the values WES Alert is built and tested against:
Why 60 FPS? WES Alert animations are tuned for smooth 60 fps motion. OBS defaults to 30, fine for a logo, choppy for our alert animations. Always force 60 with Use custom frame rate.
Why audio off the OBS mixer? Sound plays directly through the browser engine. The Dashboard's volume slider and Smart Volume cascade control the level. Routing through OBS would add a second mixer to debug for no gain.
In each of your other scenes (game, IRL, BRB, ending…), add the WES Alert scene as a source: click + in Sources → Scene → pick WES Alert. OBS treats it as a transparent passthrough: alerts fire on top, nothing else.
This is the OBS pattern for shared overlays: one source of truth, mirrored across every scene with a single click. Update the URL or swap the pack later, every scene follows.
Back in your Dashboard, open the Test Alerts panel. Pick an event type (follow, sub, donation) and click Send. The alert should play in OBS within a second.
If nothing happens, check OBS → View → Docks → Stats: the Browser Source should report no errors. If it does, see Troubleshooting below.
Need to position it? The transparent overlay makes blind placement in OBS tricky. In the Dashboard, click Pack Settings (next to Change Pack), then in 01 · Placement / Alert position, tick Freeze a test alert in OBS to dial in position & size. A test alert stays on while you drag and resize the Browser Source in OBS, so you can see exactly where it will land.
First, check the toggle. In your Dashboard, Core Settings is always visible. Confirm Sound Effects is on.
If it is, it's Chromium's autoplay policy. The overlay needs a user interaction before audio can play. The Dashboard banner tells you which state you're in:
Setup done?
Pick a pack, tweak the palette, set your alert position. Everything lives in the Dashboard.