A stream alert that freezes or stays on screen can be caused by the alert provider’s settings, an OBS source being hidden or covered, or the browser source failing to render correctly. Start by identifying where the problem appears and which provider supplies the alert; then check the provider settings and source visibility before refreshing anything or clearing a cache.
OBS does not create most third-party alerts itself: it displays them through a Browser Source. That distinction matters. If an alert plays in the provider’s preview but not in OBS, investigate the source; if it never plays in the preview, look first at the provider’s alert, pause or moderation settings.
Identify the symptom and alert provider
Write down what “frozen” means in your case. An alert may stop animating but remain visible, appear and never disappear, fail to appear at all, or be audible while hidden behind another source. These symptoms point to different checks, so do not begin by changing every setting you can find.
Also identify where you can reproduce the fault: the provider’s preview, OBS, or the YouTube stream itself. Note whether it happens with every alert or only one event type, and whether it is consistent. A test alert can help you separate an alert configuration issue from an event that did not reach the provider, but a successful test does not prove that every live event will follow the same path.
Check which provider created the alert: for example, a Streamlabs alert widget or a StreamElements overlay. OBS’s alerts FAQ explains that these are third-party overlays displayed as Browser Sources. Labels and menus can change, so use the provider’s current support page if an item is not where you expect it.
If you also operate a continuous channel, keep alerts separate from the video loop itself. An alert problem is not necessarily evidence that the video playlist has stopped; the checks in our guide to how many videos belong in a 24/7 YouTube stream playlist cover a different part of the broadcast.
Check the provider’s alert behaviour first
If a particular alert appears and then remains on screen, inspect that alert’s own behaviour settings before touching OBS. In Streamlabs, check its Animation controls and make sure both a “Show” and a “Hide” animation are selected. Streamlabs identifies a missing animation in either position as a possible reason an alert gets stuck; custom code can intentionally change behaviour, so account for that if you wrote or installed it.
Review the alert duration as well. A very short duration can make an alert disappear sooner than you expect, while an absent or unsuitable hide behaviour can leave its visual state on screen. Do not assume that every provider uses Streamlabs’ labels or offers the same controls. Follow the current instructions for the provider you actually use.
If the problem is that an alert does not play, check whether alerts are paused or muted and whether moderation is holding the event for approval. Streamlabs documents an Unlimited Alert Moderation Delay that requires someone to accept each event; an unaccepted event will not play. StreamElements users can check the Activity Feed for paused or muted alerts. These checks are more useful than rebuilding a browser source when the provider has not sent an alert to display.
For Streamlabs, temporarily disable an alert variation if you suspect that only a particular variation is misconfigured. Check custom HTML or CSS only if you deliberately use it, and preserve a copy before changing it. Streamlabs’ alert troubleshooting checklist covers animation, duration, moderation and related checks. Its interface may change, so use the current support guidance if the labels differ.
Verify that the alert source is visible in OBS
When the provider reports that an alert played but you cannot see it in OBS, check the Sources list in the scene that is actually live. Confirm that the correct alert Browser Source is present and visible. A source can be hidden, disabled, or placed below an opaque image, video, or other source that covers the alert.
Source order affects what appears on top. Move the alert source above anything that might cover it, then test again. If the alert is audible but invisible, covering sources are a particularly useful place to look; StreamElements’ overlay troubleshooting guide specifically advises checking source order in this situation.
Make sure you are testing the scene used by the broadcast, rather than a similar scene with a different source or URL. If you maintain separate scenes for a devotional loop, a local news layout, or a study channel, a fix in one scene will not automatically change another. The same care applies if you run a channel with OBS and a Hindi bhajan stream: verify the source in the scene that is actually on air.
If the alert source is visible and above covering sources, but its contents are stale or missing, move on to the Browser Source checks. Avoid changing several source properties at once; otherwise, a successful retest will not tell you which setting mattered.
Check Browser Source URL, dimensions and rendering
A provider overlay is loaded in OBS using a URL. If the provider’s overlay URL has changed, expired, or belongs to another overlay, the source may show the wrong content or fail to display the alert. For a StreamElements overlay, copy the current URL from the provider and replace the URL in the OBS source properties. Do not share a private overlay URL publicly; someone with access to it may be able to use the overlay.
Compare the source dimensions in OBS with the dimensions configured for the overlay. Use the overlay’s actual dimensions rather than assuming a standard canvas. StreamElements notes that 1920x1080 is common guidance, not a universal requirement. A mismatch can affect placement or cropping, but it does not by itself establish why an animation froze.
If the alert stutters or stops rendering, try changing OBS’s browser-source hardware acceleration setting from its current state: enable it if disabled, or disable it if enabled. Restart OBS after changing the setting, then run a controlled test. Streamlabs and StreamElements both include this as a troubleshooting step, but it is not a guaranteed repair; the effect depends on the rendering problem and the current setup.
Use the provider’s current directions for the exact OBS preference and restart sequence. Changing the acceleration setting may affect other browser sources as well, so note its original state and check the rest of your scene after restarting. If it does not help, restore the original setting before proceeding, rather than stacking changes whose effects are unclear.
Refresh the source or clear cache only when appropriate
After checking the provider configuration, source visibility, URL, dimensions and rendering setting, refresh the alert source if it still appears stuck. You can remove and re-add the Browser Source or recreate it using the current provider URL. This is a reasonable next step when the source’s loaded state may be stale; it is not the first response to an alert that is paused or awaiting moderation.
Streamlabs also documents clearing the OBS browser cache as a later troubleshooting measure. Its instructions involve closing OBS or Streamlabs Desktop, removing the relevant browser cache, reopening the software, adding the alert source again and testing. Follow the provider’s current directions carefully. Do not delete unrelated folders or files, and make sure you know which source you are rebuilding before removing anything.
Cache clearing is not a universal fix. If a wrong URL, hidden source, missing hide animation, paused alert or moderation delay caused the issue, deleting browser cache will not correct that underlying setting. Treat it as a targeted step after simpler checks, not a routine maintenance task. If the problem began immediately after a configuration change, consider reverting that specific change first.
For an always-on channel, plan source maintenance for a quiet period when you can observe the result. If you use a computer-based setup, restarting OBS or rebuilding a source can interrupt the live scene. Our guide to running a Malayalam devotional stream without a computer explains a different operating approach; whichever approach you use, schedule troubleshooting so a test does not unexpectedly disrupt viewers.
Test after each change
Make one change, run a test alert, and record what happened before changing the next setting. A useful note might read: “StreamElements test played in preview; OBS source was below the background; moved it above; test now visible.” That is enough to distinguish a successful source-order fix from a coincidental restart.
Test the symptom you are actually trying to fix. If the alert used to remain on screen, check that it both appears and leaves. If it was invisible, verify that it is visible in the live scene and not just the provider preview. If it stuttered, watch the full animation rather than deciding from a still frame. Repeat the same test event where practical so the comparison is meaningful.
A provider test is useful for checking the configured widget, but it cannot guarantee that a real event will arrive, be approved and display correctly in every case. If a test works while a particular live event does not, return to the provider’s event, moderation and variation settings rather than repeatedly changing OBS rendering options.
Keep a short change log for a long-running channel: the provider, the scene, the setting changed, whether OBS was restarted, and the test result. This is especially useful when more than one person manages the channel or when an overnight issue is found later. It also helps you reverse a change that caused a new problem.
When the alert still stays frozen
If the fault persists after the checks, capture evidence before another round of edits. Record the alert provider, OBS version, provider or plugin version where relevant, the exact symptom, whether it reproduces every time, and what changed just before it began. Include whether the provider preview and OBS behaved differently, and whether the alert was audible.
For StreamElements issues, its troubleshooting documentation asks for useful diagnostic details such as OBS and SE.Live versions, OBS logs, the activity that triggered the issue, exact error text and whether the fault can be reproduced. Share those details through the provider’s support route. Do not include a stream key or expose a private overlay URL in screenshots or public posts. See our explanation of who can see or use a YouTube stream key before sharing broadcast credentials with anyone.
If the problem is limited to one provider’s widget, report it to that provider with the evidence. If several browser sources are affected after a setting change, include that detail and the change you made. For a YouTube-only continuous broadcast, separate alert troubleshooting from the video feed: an alert rendering fault does not automatically mean the underlying stream has ended.
Choose the next action based on the symptom, not on a promise that one repair fits all cases. A visible alert that will not leave calls for checking show/hide behaviour; an alert that never plays calls for pause and moderation checks; an audible but hidden alert calls for source order; and stuttering rendering calls for URL, dimensions and browser-source checks. If those checks do not explain it, share reproducible evidence with the provider rather than deleting more files at random.
When the file and channel are ready, a managed broadcast can remove the need to keep your own computer running overnight; StreamNeo is designed to take away that specific ongoing computer-running task, not to change how a third-party alert provider configures its widget.
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
Why does an OBS alert stay on screen?
For a Streamlabs alert, check that both a Show and Hide animation are selected for the relevant alert, unless custom code intentionally controls it. Also check duration and whether the source is displaying an old or misconfigured state. Other providers may use different controls, so consult their current instructions.
Why can I hear an alert but not see it?
The alert may be hidden or covered by a higher source in OBS. Check that the correct Browser Source is visible in the live scene, then move it above sources that obscure it and test again.
Should I clear the OBS browser cache first?
Usually, check provider settings, source visibility, URL and rendering behaviour first. Cache clearing is a later step for a source that may have stale browser state, and it does not correct a paused alert, moderation hold or missing hide animation. Follow current support instructions and avoid removing unrelated files.
Does one fix work for every alert provider?
No. A persistent alert, a missing alert and a stuttering overlay can have different causes, and provider settings differ. Identify the provider and symptom, make one relevant change at a time, and test before moving to the next step.