Start by identifying whether the problem is an upload or gallery error, an alert that looks wrong or does not play, or missing alert audio. Confirm the platform and event, save the change, and test it before moving on to more disruptive steps such as relinking or clearing a browser cache.
Streamlabs alerts can be configured in its dashboard and then displayed through Streamlabs Desktop, an OBS plugin, or a browser source in compatible software. The names and locations of controls can vary by version and setup, so use the current interface as your guide rather than assuming every application has the same options.
Classify the Alert Problem
Before changing settings, write down what you expected and what happened instead. Did the image or sound fail to upload? Does the alert trigger but appear in the wrong place, with the wrong animation, or not at all? Does the visual appear while the sound is silent, doubled, or routed somewhere you cannot hear? These are different fault paths; changing an audio mixer setting will not repair an invalid image file.
Use the dashboard preview or the relevant test-alert control to reproduce the issue. Note which platform and event you selected, such as a follow or subscription alert, and whether the problem occurs in the preview, in your streaming software, or only during a live broadcast. A failure in the preview points towards the alert configuration or asset; a preview that works while the scene does not points towards the source, scene, or audio routing.
Keep the first pass reversible. Inspect settings, save, and test before removing sources or changing account connections. If more than one event type is affected, compare their settings: a shared theme, common image, or audio route may be the useful clue. If only one event fails, focus on its individual configuration and any variation that applies to it.
For a channel that also runs for long periods, keep alert troubleshooting separate from stream continuity. They are different problems with different causes; the notes in this guide to why a YouTube live stream may stop after several hours cover a different failure path.
Check the Selected Platform and Event
Open the Streamlabs alert configuration and verify that you are editing the intended platform and event. A change made to one platform-specific alert may not affect another. Check that the event is enabled and that the expected image, message, and sound are attached to that event rather than only to global styling or a different alert type.
After editing, save before navigating to another settings area. Streamlabs’ setup documentation specifically tells users to save settings before moving between menu items. Then test that same platform and event. A preview for a different event is not evidence that the one giving you trouble is fixed. See Streamlabs’ official alert setup guide for the current setup flow; labels and screens may change over time.
If the dashboard test works but the alert in the scene does not, identify how the alert is being brought into the streaming application. It may be a Streamlabs Desktop source, an OBS plugin source, or a browser source using the Alert Box widget URL. Do not follow instructions for a different route without checking that it matches your setup. Inspect the source in the scene where the issue occurs, and test again there.
A practical example: if a follow alert displays correctly in the dashboard but not in the OBS scene, first check that the intended Alert Box source is present and visible in that scene. If you also use separate scenes for a starting screen and a main broadcast, test where you expect the alert to appear. A source present in one scene may not be present in another.
Fix Image or Sound Upload Issues
If an image will not upload or does not appear in the gallery, check the format and file size against Streamlabs’ published specifications. Its customization-errors guidance lists GIF, JPEG, PNG, WebM and MP4 for images, and MP3, Ogg and WAV for sounds, with a stated file size range of 200 KB to 45 MB. These are specifications from Streamlabs’ article, last updated 14 June 2024; check its current customization-errors guidance in case the published requirements have changed.
Check the actual file, not just its name. Renaming a file extension does not convert its format. If a file falls outside the stated range, export or convert it using software you trust, then try the resulting file. Do not assume that a file that plays on your computer will necessarily be accepted by the alert gallery; the gallery has its own supported formats and requirements.
If the gallery controls are missing or fail to render properly, try the current version of Chrome or Firefox, which Streamlabs recommends for this situation. This is a browser-side diagnostic, not a reason to clear every cache or reset the streaming application as a first step. If a sound is being changed, Streamlabs documents using an audio URL, uploading an audio file, or selecting an item from its Sounds Library. Confirm the chosen asset and save the change before testing.
Streamlabs’ guide also describes using an external direct file URL when a file is too large to upload directly. Treat that as conditional: a page that displays a media player, a sharing page, or a sign-in screen may not be a URL that points directly to the media file. If the link does not load the asset, try a supported upload or another direct media link rather than assuming all file hosts work with the alert editor.
When an upload appears to succeed but the old image or sound remains, check whether you saved the event you are testing and whether it uses a variation with its own asset. Reopen that event’s settings, confirm the selected file, save, and test again. Avoid replacing every copy of a shared asset at once; change one relevant event first so you can see whether the test result changes.
Check Appearance, Theme, and Animation
For an alert that triggers but looks wrong or stays invisible, first check source order in the scene. The alert source needs to be visible and not covered by another source above it. Temporarily moving it higher in the source list is a simple test. If that makes the alert visible, restore the intended layout by adjusting the covering source or the alert’s position rather than leaving a broken scene arrangement.
Then check the active widget theme and the settings for the specific event. A theme may define styling that differs from an individual alert’s settings, and a variation can apply only under its own conditions. Temporarily disabling variations can help establish whether the base alert works. If it does, restore the variations and inspect their conditions and assets one at a time. Do not delete variations as a first response; they may be intentional parts of your setup.
Check both show and hide animations, along with the alert’s duration. A missing animation selection or a duration that is too short can make an alert appear to flash or seem absent. Test a single alert after changing one setting. If you use custom HTML or CSS and did not create or maintain it, temporarily disable it to isolate the cause. Restore only code that you intend to use and understand.
If the alert arrives late or appears not to play, check whether alerts are paused and whether a moderation delay is holding the event. Streamlabs notes that an unlimited moderation delay requires an authorised moderator to accept alerts; an unaccepted alert will not play. Confirm the moderator workflow and pending alerts before changing the delay. For current controls and terminology, consult Streamlabs’ alerts troubleshooting instructions, since settings can vary with the interface and integration you use.
If a scene is assembled from repeated video segments for an always-on channel, do not confuse a gap in the main programme with a broken alert. The alert source and the video playlist are separate elements; a black gap between videos in an FFmpeg playlist needs a playlist diagnosis, not a new alert animation.
Check Alert Duration and Variations
When an alert is stuck on screen, or the wrong one appears, investigate what controls whether it is triggered and how long it remains visible. Check the event’s duration, show and hide animation selections, and whether a moderation delay or paused-alert state is preventing it from completing its normal sequence. Change one control at a time, save, and use the same test event after each change.
Variations deserve their own check because they can override the base alert under specified conditions. Review whether a test event meets a variation’s condition and whether that variation has a complete image, message, sound, and animation setup. A temporary test with variations disabled can distinguish a base-alert problem from a variation problem. If the base alert behaves as expected, re-enable variations and check their conditions individually.
For a stuck alert, verify that the hide animation is selected and that the duration is not so short that the display seems to vanish before you can inspect it. For an alert that never appears, verify that it is enabled and not awaiting moderation. These checks are more informative than repeatedly triggering tests without recording what changed. Keep a brief note of the setting and result so you can undo an unhelpful adjustment.
Troubleshoot Audio, Mixer, and Routing
If the visual is present but the sound is missing, begin with the alert’s own sound selection and volume. Confirm that the intended sound or URL is attached to the event you are testing, save it, and trigger a test. If the test is silent in the dashboard as well as the streaming software, concentrate on the asset and alert settings before adjusting scene audio.
If the dashboard test has sound but the broadcast scene does not, check the recent-events mute control and the audio mixer in the application. Review whether the alert audio is enabled, which monitoring choice is selected, and whether it is assigned to an audio track used by the stream or recording. Monitoring and output are not necessarily the same path: hearing a sound locally does not by itself confirm that viewers receive it. Make a short test recording or private test where appropriate to check the output you actually intend to use.
In Streamlabs Desktop, check the Alert Box source properties for “Route Audio to OBS” when that control is available and relevant to your setup. The setting and its location can differ by software version; do not assume the same switch exists in OBS Studio or in every compatible application. Check the application’s own audio-track and source settings for the route you use. A guide to audio drifting out of sync in a long ambient stream addresses timing drift, which is distinct from an alert that is silent or routed to the wrong output.
If you hear duplicate alerts, look for more than one active path. The same widget may have been added twice, a pop-out window may still be running, or separate sources may be playing audio for the same event. Disable one candidate at a time and test. For browser-source echoes, Streamlabs’ OBS-specific troubleshooting recommends checking “Shutdown when not active” on the browser source in each relevant scene, then recreating the source if the problem persists. Apply that advice only if it fits your OBS browser-source setup.
Refresh or Relink if Needed
Only move to refreshes after you have confirmed the event, saved its settings, and checked the relevant asset, display, or audio route. If the source shows stale content, refresh the browser source. If that does not help, remove and re-add the widget source, taking care to preserve or record the current scene configuration first. A refresh can address stale display state; it will not fix an unsupported file or a muted mixer channel.
If the problem appears tied to the account connection—for example, platform events are not arriving even though the configured alert tests work—log out of Streamlabs services and back in, or relink the account as appropriate. Check that you are reconnecting the account associated with the platform and channel you mean to use. Account relinking can affect connected services, so it belongs after the basic configuration checks, not before them.
Clearing the streaming software’s browser cache is another later step when a browser-based widget remains stale or fails to render after simpler checks. Streamlabs’ troubleshooting article gives a Windows-specific browser-cache location for OBS and Streamlabs Desktop. Do not apply a Windows path on macOS, and close the broadcasting application before following platform-specific cache instructions. Use the current official guide for your software and operating system rather than deleting unrelated browser data.
Streamlabs also lists toggling browser hardware acceleration and restarting the streaming software as troubleshooting steps. Treat this as a diagnostic, not a guaranteed fix: record the existing setting, change it temporarily, restart as instructed, and test. If there is no improvement, restore the previous setting. When the alert is still failing, capture the software version, platform, event, source type, and what you have already tested before contacting support; that makes the remaining problem more concrete.
For a 24/7 channel, an alert fault is not a reason to make broad changes to the continuous programme while it is running. Test changes in a controlled scene or during a planned maintenance window if the alert matters to viewers. StreamNeo can remove the need to keep your own computer running the underlying video loop by turning an uploaded video into a YouTube live stream, but it does not configure or repair Streamlabs alerts; keep these as separate jobs.
A Safe Order for Retesting
Use a short, repeatable sequence after making a change. Save the alert configuration, trigger the same platform and event in the dashboard, then test it in the specific scene and software where it will be used. For an audio change, listen locally and verify the intended stream or recording output. For a visual change, check placement and whether another source covers it. Avoid changing several unrelated controls between tests, since you will not know which adjustment mattered.
Keep a small record of the original setting and the test result. If a temporary diagnostic—such as disabling variations or custom code—does not alter the result, restore it before trying another branch. This prevents a troubleshooting session from quietly removing a feature that was working. If a fix cannot be confirmed in the actual context where alerts will play, describe it as unresolved rather than assuming a successful dashboard preview guarantees the live scene will behave the same way.
When the file and channel are ready, choose the operating setup that suits the rest of your broadcast workflow.
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 won’t my Streamlabs alert image upload?
Check the file format and size against Streamlabs’ published customization specifications, and confirm that the gallery is loading in a current Chrome or Firefox browser. Its article lists GIF, JPEG, PNG, WebM and MP4 images and a 200 KB to 45 MB range, but those specifications are dated and may change. If you use an external URL, confirm it points directly to the media file.
Why is my Streamlabs alert not showing?
Confirm the correct platform and event are selected, enabled, saved, and tested. Then check source visibility and stacking order, theme and variations, moderation delay, paused alerts, and show/hide animation and duration settings. A dashboard preview and a scene test check different parts of the setup.
Why is my Streamlabs alert sound not working?
Check the selected sound, volume, recent-events mute control, and the mixer’s monitoring and track settings. In Streamlabs Desktop, inspect “Route Audio to OBS” when applicable; other software may use different controls. Test the audio in the output path viewers or a recording will use, not only through local monitoring.
Should I clear the browser cache or relink my account first?
No. First check the event, save and test, then inspect the relevant asset, source, or audio route. Refresh or recreate a stale browser source, relink if the issue appears account-related, and clear the application’s browser cache only if simpler checks have not resolved a rendering problem. Use instructions for your operating system and software version.