If Streamlabs donation alerts are not appearing on your stream, first send a test alert from the streaming application and check whether it reaches the scene viewers see. If it does not, troubleshoot the Alert Box and scene; if it does, check whether the real tip used your Streamlabs donation link and appears in your donation history.
A test alert only checks the alert path into your scene. It does not prove that a real payment succeeded, or that a payment made through another route qualifies for a Streamlabs tip alert. Work through the checks below in order, changing one thing at a time.
Start with a test in the streaming application
Save your Alert Box settings, then use the test control in Streamlabs Desktop, the Streamlabs OBS plugin, or the Alert Box dashboard. For diagnosis, the important question is whether the alert reaches the scene in your streaming application—not just whether an animation appears in a dashboard preview. A dashboard preview can show that a widget preview is available while the source in your live scene is missing, hidden, or not rendering.
If possible, watch the program output or make a short private recording of the scene while sending the test. This helps distinguish an alert that never reaches the scene from one that appears in the scene but is obscured or inaudible in the final output. Do not send a real payment just to test the visual alert path.
Record the result before changing anything:
| What you observe | Where to look next |
|---|---|
| No test alert in the streaming scene | Alert Box source, active scene, source visibility, layer order and browser rendering |
| Test appears in the scene, but not in the programme output | Scene or output selection, source position and rendering |
| Test appears, but a real tip does not | Donation link, transaction status and donation history |
| Alert is listed or delayed but does not play | Moderation, alert settings, filters and custom widget design |
This split prevents you from trying payment fixes for a rendering fault, or clearing browser cache when the tip itself has not arrived in the applicable account. Streamlabs’ alert setup instructions describe the available setup routes; interface labels can change, so use the current instructions if your version looks different.
If the test is missing, check the Alert Box source
The streaming application needs an Alert Box source connected to the correct Streamlabs widget. The exact method depends on the software you use:
- In Streamlabs Desktop, check that an Alert Box is present in the Sources panel.
- With the Streamlabs plugin for OBS, check the plugin’s Widgets menu and add its Alert Box to the scene.
- In OBS Studio without that plugin, or another compatible programme, use the Streamlabs Widget URL as a Browser Source.
For a Browser Source, confirm that the URL is the current Widget URL for your Streamlabs account, rather than a donation page URL or an old URL copied from another account. Treat the URL as private: anyone who can use it may be able to display your widget. If you have replaced or reconfigured the widget, update the source in the streaming application as well.
Check that the source is enabled and belongs to the scene you are actually using. Streamers often prepare an alert source in a starting scene and then switch to a different scene for the live programme. If the test appears in one scene but not another, add or copy the appropriate source into the scenes where it should be visible, or use a scene arrangement that keeps the source available. If you need to rebuild a longer-running broadcast rather than manage scene changes manually, the practical considerations in keeping a YouTube 24/7 stream running are a separate issue from whether this alert source is present.
If you are unsure whether the source connection is the problem, avoid deleting several widget sources at once. First note which source is in the active scene and which integration it uses. Then correct that one source, save, and send another test through the application.
Check scene visibility, layer order and rendering
A valid Alert Box can still be invisible. In the active scene, check the source’s visibility toggle, its position within the layer stack, and its on-screen bounds. A source below an opaque image or video may be running but covered. Move it above sources that should not cover it, then test again. Also check whether the alert is positioned outside the canvas or scaled to dimensions that make it hard to see.
Confirm that the scene you are inspecting is the one sent to the audience. If your streaming application has a separate preview and programme output, compare both. A test visible in a preview scene does not help viewers if the live output is showing a different scene. Keep the alert within a part of the layout that is not covered by captions, a logo, or other scene elements.
If the alert animation is visible in the scene but seems absent from the final broadcast, check the actual output or a local recording before changing the widget. This is a useful distinction for any live scene issue: as with diagnosing audio that goes out of sync in a YouTube live loop, identify whether the fault is in the source itself or in what reaches the output.
For an external Browser Source, check its width and height, and make sure the source is not cropped or constrained to a tiny region. The widget may render beyond its visible bounds if dimensions were changed during layout work. Adjust the source rectangle in the scene and test; do not assume that changing the size of the stream canvas will fix a widget that is simply positioned off-screen.
If nothing renders, restart the streaming programme after saving the scene, then test again. A restart is a useful check for a stalled browser component, but it should not replace confirming that the right source is in the right scene. If the source remains blank, move on to browser rendering and cache after the event and scene checks.
If tests work, verify the donation link and transaction
When an in-application test reaches the scene but a real tip does not produce an alert, check the event source before altering the overlay. Streamlabs says its tip alerts are tied to donations made through the creator’s Streamlabs donation link. A payment sent using a separate PayPal link or another donation service’s link does not become a Streamlabs tip event merely because the same person is streaming with Streamlabs.
Open the donation page you shared and confirm that it is the Streamlabs link for the account whose Alert Box is in the scene. Streamlabs donation links commonly use a creator-specific /donate/ or /tip/ address, but check your own current page rather than relying on an old message, profile description, or saved browser bookmark. If you recently changed accounts or links, check which one viewers can still access.
Then check the donation history in Streamlabs. A chat message saying that someone donated is not confirmation that a transaction completed or reached your account. Review the payment status and, if it is absent or pending, follow the payment provider’s own record as well as the relevant Streamlabs support guidance. A pending bank-account or eCheck payment may not appear as a completed donation until it clears. Check that the payment account and accepted currencies are configured for your intended route; if the status is unclear, use Streamlabs’ current support page rather than promising a viewer an alert will appear.
The useful comparison is between the two paths below. A successful test isolates the scene path; it does not certify the payment path.
| Check | What it can tell you | What it cannot tell you |
|---|---|---|
| Test alert reaches the live scene | The configured test event can reach and render through that source and scene | That a viewer paid, or that the donation used the Streamlabs route |
| Donation appears as completed in Streamlabs history | Streamlabs has registered the donation in the relevant account | That the scene source is visible or configured to show that event |
If you run a devotional or community channel and also accept support through more than one route, label each link clearly. That does not make one service’s events appear in another service’s widget; it helps viewers choose the route that matches the alert system you have configured. Keep a note of the exact link you tested so that you can distinguish a stale link from a missing overlay event.
Review alert settings, moderation and filters
If the test works but a qualifying tip is in the history without a visible alert, inspect the settings for the donation or tip alert type. Confirm that it is enabled and that you saved the edited settings. If you use alert variations, test the relevant variation rather than assuming a general test exercises every condition. A variation may use a different layout, sound, or rule, so one working test does not rule out a fault in another variation.
For a Browser Source, check whether event filtering was applied to its Widget URL. Streamlabs documents that this filtering applies to Browser Source Widget URLs; it does not change the Alert Box source in Streamlabs Desktop or the plugin. Make sure that the event has not been excluded by a filter intended for another scene or purpose. Do not copy a filtered URL into a different setup without understanding which events it omits.
Consider whether moderation is holding the alert. Streamlabs’ troubleshooting guidance notes that with Unlimited Alert Moderation Delay enabled, an alert that has not been accepted will not play. Check the moderation queue and the setting before treating a delayed event as a failed transaction. If a viewer submitted a message along with a tip, the message may also be affected by profanity settings or custom bad-word entries. Check whether the alert is hidden entirely or whether only its text has been filtered.
If the wrong design appears, confirm the selected Widget Theme for the scene collection you are using. A theme change can make an alert look different from the one you expect, while custom HTML or CSS can change or break its display. If you did not intentionally customise the widget, temporarily disable custom code and send a test. Make a note of the setting you changed and restore it if it was not the cause.
For account-level symptoms, Streamlabs’ troubleshooting guide includes logging out and back in and relinking the account among its checks. Treat that as a later step if the source, event type, and history point to an integration issue. Changing account connections can affect more than one part of your setup, so record the current account and source configuration first. Streamlabs’ widget troubleshooting guide is the appropriate primary reference for the settings and rendering checks; follow its current steps for your application.
Refresh the browser source and clear cache only if needed
A Browser Source can stop rendering correctly even when its URL and scene placement are right. Start with the least disruptive action: refresh the source from your streaming application if that option is available, or close and reopen the programme after saving your scene. Test again. If the problem persists, Streamlabs lists toggling browser hardware acceleration, restarting the streaming programme, and refreshing or re-adding the widget source among its troubleshooting checks.
Do not change browser acceleration, remove the source, and clear cache all at once. Make one change, then send a test alert and check the output. Otherwise, if the alert starts working, you will not know which action helped—and may not know what to reverse if another source is affected.
Clearing a browser-source cache is a more targeted step for a persistent rendering fault, not a first response to a missing real donation. Streamlabs documents separate cache locations for OBS Studio and Streamlabs Desktop on Windows, and those locations can vary by application version. Use the current instructions for your installed programme rather than deleting guessed folders. Close the streaming application before following cache-clearing steps, then reopen it and test the Alert Box.
If you use Streamlabs Desktop or the OBS plugin rather than an external Browser Source, cache guidance for OBS Studio may not apply in the same way. Follow the relevant product instructions for the integration you actually use. Likewise, if the event is missing from donation history, clearing a display cache will not make a payment complete or turn an event from a separate donation route into a Streamlabs alert.
Keep the fault isolated while you test
A short record of what you observe makes repeated troubleshooting less confusing, especially if you change scenes or use different routes for support. Note the active streaming application, whether the test was sent from the application or dashboard, whether it appeared in the live scene, and whether a real event is present in Streamlabs history. This is enough to identify the branch without recording private payment details in a public chat or support post.
After each relevant adjustment, repeat the same test under the same conditions. If you change the source URL, verify the source; if you change moderation, test the relevant alert type; if you change browser rendering, retest the output. Avoid sending a real transaction as a routine test. The goal is to distinguish source delivery, event eligibility, and payment state—not to make more changes than the evidence supports.
For a stream that also relies on a stable encoder, keep alert troubleshooting separate from stream transport faults. An invalid stream key, for example, is a broadcast connection problem rather than an Alert Box problem; the checks in fixing an FFmpeg invalid stream key error apply to that separate failure. Keeping the categories distinct helps you avoid changing a working alert widget while solving an unrelated stream issue.
If the file or channel setup itself is what you are preparing, choose the operating approach based on how you need to manage scenes and interactions. A cloud-run video loop does not replace a live interactive scene with alerts and moderation; make sure the workflow you choose actually includes the alert behaviour you need.
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 a test alert prove a viewer’s donation succeeded?
No. A test alert checks whether a test event reaches the configured scene, not whether a payment was made or completed. Check the payment status and Streamlabs donation history separately.
Why does the dashboard preview show an alert when the stream does not?
A dashboard preview is not the same as an alert rendered in the active streaming scene. Confirm that the right Alert Box source is present, enabled, and visible in the scene sent to the audience, then test from the streaming application.
Will every PayPal donation trigger a Streamlabs alert?
No. Streamlabs tip alerts depend on the applicable Streamlabs donation route; a separate direct PayPal link does not automatically create a Streamlabs tip event. Check the link used and whether the donation is recorded in Streamlabs history.
Should I clear cache as soon as an alert disappears?
Not usually. First test the alert in the application, verify the source and scene, and check whether the event exists in history. Clear the relevant browser-source cache only if a persistent rendering problem remains, using the current instructions for your application.