If your stream alert is missing, visually broken or silent, first test it in the alert provider, then trace the result through the source, scene and audio settings. OBS Studio does not supply alerts itself: it displays third-party alert overlays, commonly through a Browser Source.
That distinction helps you locate the fault without changing everything at once. A failed provider preview points towards the alert configuration or account; a successful preview that never reaches your scene points towards the source or its placement; an alert you can see but cannot hear points towards sound settings. Some individual platform events may also be unavailable for reasons outside your streaming software.
Identify whether the alert is missing, broken or silent
Start by describing exactly what happens. “My alerts are not appearing in my stream” can mean the event never triggered, the widget did not receive it, the source is hidden behind another layer, or it appeared without sound. Those are different faults, and each needs a different first check.
Run a test event from the provider’s dashboard or alert manager. If there is a provider preview, watch that as well as your streaming-software preview. Write down which checks show the alert: provider preview, streaming-software canvas, recording or stream output. This simple sequence separates delivery from display and sound.
| What you observe | First place to investigate | What it suggests |
|---|---|---|
| No alert in the provider preview | Event settings and account connection | The provider may not be generating the test correctly. |
| Provider preview works, but the scene is blank | Browser Source URL, source state and scene order | The widget may not be installed or visible in the active scene. |
| Alert appears in the scene but not in a recording or broadcast | Source output and scene selection | The visible preview may not match the programme output. |
| Alert is visible in the output but has no sound | Muting, routing, monitoring and recording track | Visual rendering works; the audio path needs checking. |
| Only one event type is absent | Event support, event setting and account privacy | The issue may be specific to that event rather than the whole widget. |
Keep a note of the result after each change. If you replace a URL, adjust source order and alter audio routing together, a working result will not tell you which change mattered. Test one variable, then repeat the same provider test.
For a continuous YouTube channel, separate the alert widget from the video or programme feed in your diagnosis. An overlay can be missing while the underlying stream continues normally. Conversely, a general stream interruption is not necessarily an alert-widget fault; the checks in this guide to buffering on a live stream cover a different problem.
Check the alert widget and Browser Source
OBS does not create or send alerts on its own. As the OBS Project explains in its alert FAQ, OBS Studio does not directly provide stream alerts. You configure alerts with a platform feature or an alert provider, then add that provider’s output to the streaming scene. In OBS this is commonly a Browser Source; another application may offer a dedicated alert source type instead.
First confirm that the alert provider’s own test works. If it does not, check that the desired alert type is enabled, the provider account is connected, and the test is being sent to the correct alert set. If the provider offers separate widgets or themes, make sure you tested the same one intended for this scene. A provider test can confirm the widget is generating an alert, but it cannot prove that your broadcast scene contains the correct source.
Next confirm that the current widget URL is installed in the intended source. Twitch’s Alerts FAQ identifies a missing copied Browser Source as a common reason alerts do not appear. Compare the source you added with the URL or source instructions currently shown by your provider; do not assume an old source is still valid after replacing a widget or changing accounts.
Streamlabs Desktop may provide a dedicated Alert Box source, while a different streaming application may use a browser-based widget. Follow the provider’s instructions for the software you actually use. The Streamlabs guide to setting up alerts distinguishes its Desktop source from a browser source used in other software and recommends testing before going live.
If the source appears to be present but stale, use its refresh control if available. If refreshing does not help, remove and re-add the source using the current provider instructions, then run the test again. This is a useful repair when a URL was pasted incorrectly or a source stopped loading, but first record any dimensions or custom settings you need to restore.
Avoid resetting account credentials or an API token as an opening move. Some providers warn that widgets using an old token or URL will need updating after a reset. If you eventually take that step, expect to replace every affected widget URL, not just the one alert currently under investigation.
Verify source visibility and scene placement
A correctly configured widget can render behind another source or be disabled in the active scene. In OBS, inspect the source list for the scene that is actually on air. Confirm that the alert source is enabled, that its visibility icon is on, and that the source is above any video, image or browser layer that could cover it.
Check the canvas during a provider test. If the alert is visible there, but absent from the programme output, confirm that the correct scene is selected and that no scene transition or nested scene is putting a different composition on air. A preview that looks right is not enough if the broadcast is using another scene collection or a scene with a similarly named source.
Look at the source’s size and position. A widget can be loaded but placed outside the canvas, reduced to an unusable size, or cropped by a transform. For a test, temporarily move it to a clear area and use a conspicuous test alert. Restore the intended position afterwards; avoid using a real viewer event as your test method.
If you use multiple scenes, establish whether the alert source is shared or separately added in each scene. A change made to one copy may not affect another. This matters for channels that rotate between programme layouts, such as a live lesson and a break screen. The guidance on streaming lessons on YouTube is a useful reminder to test the scenes viewers actually see, not just the main teaching layout.
Change only one visibility or placement setting at a time, then test again. If you suspect browser rendering rather than layer order, hardware acceleration is one diagnostic variable: toggle the relevant browser-source setting if your software exposes it, restart the streaming application after changing it, and repeat the test. This is not a guaranteed fix, and if the display worsens, return to the prior setting.
Review alert settings and test events
Alert widgets often have separate controls for event types, appearance, sound and moderation. Open the provider’s alert set and check that the event you are testing is enabled. Then verify the chosen theme, text, image or animation and sound for that event. A provider may successfully display one alert type while another is disabled or configured with an empty asset.
Use the provider’s test function after changing each setting. If the provider preview is blank or shows the wrong design, the problem is still within the provider setup, not the OBS scene. If its preview is right but the scene is wrong, return to the Browser Source and visibility checks rather than repeatedly editing the alert’s appearance.
Moderation can delay or suppress an alert. Check whether alerts are held for manual approval, whether a moderation delay is configured, and whether the pending event was accepted. Custom HTML or CSS can also change or hide what the widget displays. If you did not intentionally write custom code, temporarily turn it off and test the default widget presentation before investigating the code path.
Make sure the correct widget or theme is associated with the scene and account you are using. Relinking an account can be appropriate if its connection has expired, but treat it as a deliberate step: verify which account is connected and re-run the provider test afterwards. Changing an account connection will not fix a source that is hidden or placed in the wrong scene.
Keep a short troubleshooting record: event tested, provider preview result, scene result, and the one setting changed. If the alert is for a channel welcome, membership or other audience interaction, confirm the associated event type is exposed by the connected platform and provider before spending time on layout. A membership welcome message has its own event configuration, separate from simply displaying a general alert box.
Trace audio routing and Browser Source sound
When the animation appears but is silent, do not start by replacing its URL. First confirm that the alert has a sound assigned and that the provider has not muted alert audio. Test with a sound you know is present, at an audible level, and repeat the event. A visual alert with no assigned sound is different from sound that is generated but sent to the wrong output.
In OBS, inspect the audio mixer while a test alert plays. If the alert source has an audio control, check that it is not muted and that its level is moving. Review the source’s audio routing options, the advanced audio properties and monitoring mode. Names and available controls vary with the source type and software version, so follow the instructions for the specific provider source rather than assuming every Browser Source behaves identically.
Monitoring and broadcast output are separate concerns. Audio set to monitor may be audible on your local headphones but absent from the stream mix; a source sent only to the stream may not be heard in your headphones. Check the intended destination and test the actual output, preferably with a short local recording or an unlisted/private test arrangement appropriate to your channel.
If the alert is heard live but missing from a recording, inspect which recording track is selected and whether the alert source is routed to that track. If it is absent from both monitoring and output, check the source mute state, provider sound setting and routing first. Avoid changing the microphone or music mix unless the test shows that those sources are involved.
Some alert tools expose an option such as “Route Audio to OBS”. If available, confirm that the alert sound is routed into the mixer before adjusting monitoring or track assignment. Streamlabs lists this as a troubleshooting step for its alert box, but the exact control depends on which source type and software you use. Change the route, test, and then check both the intended broadcast mix and any recording track you rely on.
Check local browser, network and platform limitations
If the provider test and source setup look right but the widget still fails to load, consider local software state. Refresh or re-add the source, then restart the streaming application if you changed browser hardware acceleration. Check that system date and time are sensible, and that security software or a firewall is not blocking the provider’s widget. If you suspect a cached or stale page, clear the relevant browser-source cache using the software’s supported controls.
Relink the provider account only after checking the simpler source and settings issues. A relink can repair an expired connection, but it does not establish that every platform event is available. Resetting a token is later still: it can invalidate multiple widget URLs, so plan to replace each old URL and test every source that depended on it.
If only one kind of alert is missing, look beyond the local scene. The event may not be supported by the connected platform/provider combination, may be disabled for that account, or may depend on privacy settings or user action. Streamlabs Support documents that Twitch resubscription alerts may depend on the subscriber sharing the resubscription in chat, and that YouTube subscriber alerts can be affected when subscriptions are private. Its troubleshooting page, updated 25 April 2025, reports that YouTube subscriber alerts may take up to four hours; check the current provider and platform guidance before treating that as applicable to your channel.
This is why a test alert and a real platform event are not equivalent. A provider test checks the widget’s display path; it does not prove that a particular viewer action will be exposed to that provider. If the test works and one event does not, check the current official event and privacy documentation before rebuilding the scene. Do not promise viewers that every event will trigger an overlay.
For a YouTube-only channel, alert widgets are supplementary to the programme rather than a substitute for a reliable stream. If your real difficulty is leaving a computer running to keep a video loop on air, StreamNeo removes that specific burden by letting you upload a file and run the YouTube broadcast without keeping your own computer on; it does not create viewer-event alerts or extend platform event coverage. If the computer-based broadcast itself is the concern, the practical trade-offs in keeping a church YouTube stream running when the internet drops are more relevant than changing alert settings.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does OBS Studio provide native stream alerts?
No. OBS Studio displays alerts configured through a platform feature or a third-party provider; the overlay is commonly added as a Browser Source. Check the provider’s current instructions for the source type used by your software.
Why does the provider test work but the alert not appear in OBS?
The provider test shows that the widget can generate an alert, but it does not confirm that the correct URL is installed in the active scene. Check the Browser Source, its visibility, its order above covering sources, and whether the scene on air is the scene you tested.
Why can I see an alert but not hear it?
Check that the alert has a sound and is not muted, then inspect its audio routing, monitoring mode and recording-track assignment. Test the actual output as well as local monitoring, since those paths can differ.
Can I make every platform event trigger an alert?
No local setting can guarantee that every event will be exposed to an alert provider. Event support, account settings, privacy choices and platform delivery behaviour can affect individual alerts, so check current official documentation when only a particular event is missing.