StreamElements Alerts Not Working in OBS? How to Fix Them
If your StreamElements alerts suddenly stop showing up in OBS, the good news is that the problem is usually pretty simple.
Most of the time, you do not need to rebuild your entire alert setup. The issue is usually something small like the wrong overlay link, unsaved changes, a hidden Browser Source, or StreamElements being connected to the wrong account.
Here are the quickest things to check.
1. Copy Your StreamElements Overlay URL Again
This is the first thing I would check.
Go to your StreamElements overlays and copy the URL for the overlay that contains your AlertBox again.
Then open OBS, right-click your StreamElements Alerts Browser Source, choose Properties, and replace the URL with the fresh one.
Make sure there are no extra spaces before or after the URL.
I have had alert problems come down to something this simple.
If you need the original setup process, see my guide on how to set up StreamElements alerts in OBS.
2. Make Sure You Saved Your Changes in StreamElements
If you recently changed an alert, image, sound, or other setting, make sure you actually clicked Save in the StreamElements Overlay Editor.
It is very easy to make changes, switch back to OBS, test the alert, and wonder why nothing changed.
Save first, then test again.
3. Make Sure You're Using the Right StreamElements Account
This one can sneak up on you if you stream from more than one account or channel.
For example, if you normally stream from one Twitch profile but switch to another, the StreamElements overlay URL connected to your original account may not be the one you need.
Check which account you are currently logged into on StreamElements and make sure the overlay belongs to the correct channel.
4. Check That the Browser Source Is Visible in OBS
Look at your Sources panel in OBS.
Make sure the eye icon next to your StreamElements alert source is turned on.
Also make sure another full-screen source is not sitting on top of it.
OBS displays sources in layers. If your AlertBox is underneath your gameplay, camera background, or another full-screen source, the alert may technically be working while completely hidden.
Move the alert Browser Source higher in the Sources list and test it again.
5. Make Sure the Browser Source Size Matches Your Overlay
If your StreamElements overlay is 1920 × 1080, the Browser Source should normally use the same dimensions.
Right-click the alert source in OBS and choose Properties.
Check:
Width: 1920Height: 1080
or whatever dimensions you used when creating the overlay.
StreamElements currently recommends matching the Browser Source dimensions to the overlay itself.
6. Check That Your Alerts Aren't Paused or Muted
StreamElements allows alerts to be paused or muted.
Check your StreamElements Activity Feed and make sure alerts have not accidentally been paused.
If the alert appears but you cannot hear anything, check whether alerts are muted and make sure the Browser Source audio is actually being routed through OBS.
You can also right-click the Browser Source, open Properties, and enable Control audio via OBS if you want the alert audio available in the OBS Audio Mixer.
7. Test the Alert in StreamElements
Go back to your StreamElements Overlay Editor and use Emulate to trigger a test alert.
Try something simple like a follow or subscriber event.
If the alert works in StreamElements but not in OBS, that narrows the problem down considerably.
At that point, focus on the Browser Source URL, source visibility, dimensions, and OBS itself.
StreamElements Alerts Still Not Working In OBS?
Delete the StreamElements Browser Source from OBS and add it again using a freshly copied overlay URL.
Sometimes rebuilding one Browser Source is faster than hunting for one tiny setting that got changed somewhere along the way.
And if your alerts are working but you want to replace the default graphics with your own designs, see my guide on how to create custom StreamElements alerts and install them in OBS.
Most StreamElements alert problems are not catastrophic. Start with the URL, make sure your changes are saved, confirm you're using the correct account, and then check the Browser Source in OBS.
Nine times out of ten, the problem is hiding somewhere in that little group.
Comments