Streamlabs Alert Box supports YouTube membership-gifting alerts, and Streamlabs Desktop lets you create variations with gift-specific conditions. To use one, add the Alert Box to the scene that will go live and test both its appearance and placement first.
Support for the alert does not mean gifting is enabled on every YouTube channel, or that every event will reach your alert. Confirm gifting is available for your channel, then use the steps below to configure and check the alert route you actually plan to broadcast.
Confirm Alert Box supports membership gifting
Streamlabs documents support for YouTube membership gifting in its membership-gifting alert guidance. The feature sits within Alert Box, the layer that displays alerts in a stream scene. A gifting event can therefore be represented visually on the broadcast, rather than relying only on viewers noticing a chat message.
Keep two separate questions in mind: whether Streamlabs supports the alert type, and whether YouTube has enabled membership gifting for your channel. The Streamlabs article was originally published in 2022 and updated in 2025; it described gifting as rolling out to a limited number of streamers at that time. That historical note is not a current eligibility guide. Check YouTube Studio and YouTube’s current official information for your channel rather than assuming that a configured alert means gifting is available.
Connect the correct YouTube account to Streamlabs before changing alert settings. Streamlabs’ alert setup instructions describe linking platforms through account settings. In Desktop, also make sure the intended YouTube channel is selected where platform-specific alert settings are shown. Alert types depend on the platforms linked to the account, so a missing Members setting may be an account or platform selection issue rather than a broken variation.
A useful distinction is that the alert responds to an event Streamlabs receives; it does not create or enable the YouTube membership feature. If your audience cannot gift memberships on the channel, there may be no real event to trigger the variation. Resolve that availability question separately before relying on the alert in a live session.
Open Alert Box variations in Streamlabs Desktop
Open Streamlabs Desktop and find Alert Box in the application’s alert or sources controls. In the Alert Box settings, select Open Alert Variations. This is where you can make a separate rule for a type of event, instead of changing the presentation of every membership-related alert.
The documented sequence is concise: open Alert Box, choose Open Alert Variations, then choose Add A Variation With Custom or Default Settings. Labels can shift slightly as software interfaces change, so if a control is not in the expected place, consult Streamlabs’ current instructions for adding live stream alerts and confirm you are in the YouTube Members alert settings.
Before creating a variation, verify the platform context. If several channels or platforms are connected, a rule in the wrong platform’s settings will not provide the intended YouTube membership-gift behaviour. Check the Members alert area and the account or channel selection before saving changes.
Variations are useful when one presentation does not suit every event. For example, you might want a restrained acknowledgement for ordinary membership activity and a more prominent visual for a gift event that meets a threshold. Keep the purpose of each variation clear; overlapping or hard-to-distinguish rules make it harder to tell what fired during testing.
Add a variation with custom or default settings
Choose Add A Variation With Custom or Default Settings. A default-based variation gives you a starting presentation, while a custom one gives you room to tailor how the selected gift condition is presented. The important decision is not which option sounds more advanced, but whether you can recognise the variation and confirm its trigger when you test it.
Once it is added, review the settings available for that alert. Streamlabs’ alert editor supports adjustments such as layout, image or GIF, sound, font, animation and duration; the settings available can vary by alert type. Make changes that suit the channel’s content and viewing context. A devotional stream may call for a modest visual that does not interrupt a bhajan; a local news loop may favour a short, legible acknowledgement that leaves the main information visible.
Streamlabs describes default gifting behaviour as showing the gifter’s name and the number of memberships gifted, with an alert for each new member. It also says Cloudbot automatically alerts chat. Those are descriptions of Streamlabs’ documented behaviour, not a promise that every YouTube event will arrive or that your specific scene is configured correctly. Use the variation settings and the Test control to check what your own setup displays.
Decide whether your variation should represent a gifting event as one grouped acknowledgement or whether you want an alert associated with each new member. Streamlabs’ gifting guidance describes options to show one alert per gifting event and to display the membership level. Consider the effect on people watching: repeated alerts can cover content, while a single alert may be easier to read during a busy scene. The preview tells you how the chosen presentation looks; a real event is needed to verify the end-to-end path.
If you run a continuous music stream, alert timing and visual footprint matter because the scene may be on screen for long stretches. Keep the overlay from obscuring lyrics, a schedule or the main visual. Our guide to creating a daily schedule for a 24/7 YouTube music stream covers the wider programming context; the alert should fit around that content, not replace it.
Choose gift-specific conditions
Open Condition in the variation and choose the gift-related condition that matches the alert you want. Streamlabs documents conditions for membership gift amount, a user gifting at least a given number of members at once, and membership gift level. The exact wording in the interface may present a value or level to select; use only the choices available in your current Streamlabs setup.
| Condition type | What it distinguishes | A sensible use |
|---|---|---|
| Membership gift amount | A gift amount that matches the condition | Make an alert recognisable for a chosen gift amount |
| Members gifted at once | A threshold for how many members are gifted in one event | Reserve a more prominent treatment for a larger simultaneous gift |
| Membership gift level | The membership level associated with the gift | Use level-specific wording or artwork where it is appropriate |
These are different ways to distinguish events, not a guarantee that each type will be available in every account or that a particular event will arrive. Choose one condition to express a clear intent. For instance, a channel might use a quiet treatment for most gifts and a more noticeable animation when an event meets its chosen at-once threshold. The number used in a condition is your configuration, not a platform benchmark.
Avoid building a maze of overlapping variations. If more than one variation could appear to match the same event, it becomes difficult to understand which presentation should be expected. Start with the one gift-specific rule that matters most to the audience, save it, then preview it. If you later add another, make its distinction easy to explain and test each one separately.
The condition controls when a variation is eligible to be used; it does not determine whether YouTube sends the underlying event to Streamlabs. Nor does a threshold prove that the live broadcast will receive all eligible events. Treat the setting as one part of the path: YouTube event availability, account connection, Streamlabs alert configuration, and placement of the widget in the broadcast scene all need to be checked.
Preview with the Test button
Use the Test button in the Alert Box settings to preview the alert after editing. In Streamlabs Desktop, Test Widgets can also be used to check the widget in the application. The preview helps you inspect the visual treatment and whether the alert occupies the intended place in the scene. It is a practical check, not a substitute for a real membership-gifting event.
Check the alert at the size and layout you will actually use. Confirm that text is readable, the image or animation does not cover essential information, and the sound is appropriate for your channel. If the channel uses a lower-third, lyrics, a devotional image or a news ticker, preview the alert against that material rather than evaluating the widget in isolation.
A test can reveal a misplaced source, muted sound, an unexpectedly long animation or a variation that is visually indistinguishable from the ordinary alert. Correct those issues before going live. If the test preview does not appear, check that the Alert Box is enabled and that you are testing the correct platform and scene; do not assume the setting is proven merely because it saved.
Streamlabs Desktop’s Recent Events area can show gifted memberships as they are received, according to Streamlabs’ alert guidance. During a real event, that can help you investigate whether an event reached the account. It does not replace the Test button for checking design and placement, and it cannot demonstrate how an event will behave before an event occurs.
Testing should be part of the pre-live routine, especially if you change scenes, edit the variation or switch software. Keep a short checklist: correct YouTube account selected, Members settings open, variation saved, Test preview visible, and Alert Box included in the outgoing scene. For advice on keeping visual elements readable in a continuously running channel, see how to switch between video playlists in an OBS YouTube stream; scene changes are another reason to verify where persistent overlays appear.
Add the Alert Box to your stream
A configured alert only appears in the broadcast if the Alert Box is included in the scene or layout being sent to YouTube. The route depends on the software you use. In Streamlabs Desktop, use the plus sign in Sources and choose Alert Box. Select the relevant widget and check that it is visible in the scene you intend to broadcast.
If you use OBS with the Streamlabs plugin, Streamlabs documents adding the widget through Streamlabs → Widgets, then choosing Alert Box. In other streaming software, copy the widget URL from the Streamlabs dashboard and add it as a browser source. Follow the current instructions for your application, because source names and controls can change between software versions.
| Broadcast software route | Where to add the alert | What to verify |
|---|---|---|
| Streamlabs Desktop | Sources plus sign → Alert Box | The source is visible in the live scene and test preview |
| OBS with Streamlabs plugin | Streamlabs → Widgets → Alert Box | The widget is included in the scene being broadcast |
| Other streaming software | Add the dashboard widget URL as a browser source | The browser source loads and is placed in the intended layout |
Keep the widget URL private if your software route uses one. It is a control link for the alert display, not a URL to publish for viewers. Add it as a source through the application’s browser-source controls and avoid pasting it into public descriptions or chat.
After adding the source, run the test again from the scene itself. A preview in the dashboard alone cannot confirm that the source is present in your broadcast composition. Check that it is above or below other sources as intended, not hidden behind a full-screen video, and not outside the canvas. A source can be configured correctly yet be absent from the scene that is actually live.
This matters if you operate a 24/7 channel with rotating material. A music playlist or scheduled programme can change the background while the alert source remains fixed, so choose a position that stays legible across the content you use. Keep the alert brief enough not to dominate the loop, and make sure any text can be read on a phone-sized screen as well as a desktop preview.
If maintaining a local computer and scene is part of a wider continuous-streaming workflow, map the alert checks to that workflow rather than treating alerts as an isolated task. The guide on streaming pre-recorded videos to YouTube 24/7 with FFmpeg on Linux discusses a different broadcast route; whatever route you use, the alert has to be available in the composed output, and this Streamlabs widget setup is not a universal event-delivery guarantee.
For a channel whose main operational concern is keeping a file-based live broadcast running while your computer is switched off, StreamNeo removes the specific burden of keeping a local streaming machine running for that broadcast; configure and test your separate alert workflow in the software that produces the live scene.
Before going live: verify the whole path
Use a final check after you have saved the variation and added the widget. Confirm that YouTube gifting is available for the channel, the right account is linked, the Members alert settings show the variation, and the condition is the one you intended. Then trigger the Test preview and watch it in the actual scene or layout that will go to YouTube.
The test verifies how the widget preview looks in your current setup; it does not establish that every real membership-gift event will be delivered. For that reason, avoid describing the alert as guaranteed or telling viewers that every gift will produce a particular on-screen result. If a real event does not appear, check the account/platform selection, the recent events display, the variation condition, and the widget’s presence in the broadcast scene before changing several settings at once.
Make changes one at a time and retest. If you alter the graphic, you can check appearance. If you alter the condition, verify that the variation remains selected and saved. If you change a scene or switch from Desktop to another broadcasting application, repeat the source check through that route. A simple record of the condition and scene can help another person on your team reproduce the setup without guessing.
Choose the alert treatment with the audience in mind. A channel with spoken commentary may want sound, while a quiet lofi or study stream may rely on a small visual. A local news channel may need to keep headlines visible. There is no single correct style; the useful outcome is an alert that communicates the event without interrupting the channel’s main purpose.
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 Streamlabs Alert Box support YouTube membership gifting?
Streamlabs says its Alert Box supports YouTube membership gifting. That does not mean gifting is enabled for every YouTube channel, so confirm availability for your own channel and test the configured alert before going live.
Which conditions can I use for a gift-specific variation?
Streamlabs documents conditions based on membership gift amount, a threshold for members gifted at once, and membership gift level. Use the conditions presented in your current interface; do not assume an option is available if it is not shown.
Does the Test button prove a real gift will appear on stream?
No. The Test button previews the alert’s presentation, while a real event also depends on the event reaching Streamlabs and the widget being present in the broadcast scene. Use the test to catch presentation and placement problems, but do not treat it as a guarantee of delivery.
Where do I add the Alert Box in OBS or other software?
In Streamlabs Desktop, add Alert Box from the plus sign in Sources. With the Streamlabs plugin in OBS, use Streamlabs → Widgets → Alert Box; other software can use the dashboard widget URL as a browser source. Test again in the scene or layout you will actually send to YouTube.