An alert variation is an alternate alert selected when a supported event condition is met; a widget theme changes the broader look of your alerts and other widgets. In Streamlabs, you configure variations against an event type, then display the alert box in OBS through a Browser Source.
The available conditions depend on the platform and event, so use the choices shown in your connected account rather than expecting every option everywhere. The steps below use a tip amount as a concrete example, and explain how to preview the result before relying on it in a live scene.
Alert variations and widget themes are different
The word “variation” can describe two different jobs. A conditional variation is an alternate version of one event alert: for example, a tip above a chosen amount can use a different animation from an ordinary tip. Streamlabs selects it according to the condition attached to that event. The point is to reserve a particular treatment for a particular kind of event without changing all your widgets.
A widget theme is broader. It is a profile of alert and widget settings that you can switch when you want an overall style change, such as moving from a quiet study stream look to a more celebratory gaming layout. Streamlabs also documents using widget links from different themes in streaming software to combine widgets. This is a different decision from asking which alert should fire for a qualifying event.
| If you want… | Use… | Selection happens… |
|---|---|---|
| A different alert for a qualifying tip or other event | An event variation | Automatically, when the configured supported condition matches |
| A different general visual style for several widgets | A widget theme | When you switch or arrange the theme and its widgets |
| An alert layout different from the rest of a chosen theme | A variation, or a separately chosen widget link if appropriate | According to the relevant event rule or widget selection |
Before changing settings, decide which of those outcomes you actually need. If all alerts should simply have a new colour scheme, a variation may be unnecessary. If only larger tips should have a longer animation or distinct sound, a theme switch would affect more than that one event. Streamlabs explains the two controls in its guide to alert box variations and introduction to widget themes.
Choose an alert event in Streamlabs
Sign in to the Streamlabs dashboard and open Alert Box. Select the event type you want to change, such as tips, follows, or another event offered for your connected platform. The list of event types is not a promise that each type is active or available in every account: the platform connection and provider setup matter, and the dashboard’s actual options are the useful guide.
Start with one event and one outcome. For this example, choose tips and plan to give a tip of at least $10 a distinct treatment. Streamlabs’ documented example uses that threshold. It is an example, not a universal recommendation or a claim about what amount suits your audience. You can pick a different amount that has a clear meaning for your channel, provided the condition selector offers it.
Look at the options displayed for the selected event before designing the alert. Depending on platform and event type, Streamlabs documents conditions such as minimum or exact Bits amounts and raid party size for Twitch; membership duration, level, gift amount and Super Chat amount for YouTube; and minimum or exact tip amounts, largest tip of the stream, or recurring tips. These are examples of the range, not a checklist available for every event.
If you run a devotional stream, you might want a restrained special alert for a larger contribution, while keeping ordinary alerts unobtrusive. A local news loop may instead avoid noisy alerts during a quiet segment. The event condition only decides when a variation is eligible; your use of sound, animation, and on-screen text still needs to suit the channel and the people watching.
Add and name a conditional variation
With the event selected, find its variation controls and choose the option to add a variation. The exact labels can change, so follow the variation controls shown for that event. Give the entry a name that describes both its trigger and intent, such as “Tips at least $10 — longer thank-you”. A name like “New alert” is harder to review later, especially when you have several entries.
Choose a condition from the supported controls. For the example, set a minimum tip amount of $10 if that condition appears for your connected tip event. Read the selector carefully: an exact amount and a minimum amount mean different things. An exact value would target that value; a minimum would cover amounts at or above it. Do not assume that an option available for one platform or event is available for another.
Keep the logic readable. If one variation begins at a minimum amount and a second variation uses a range that overlaps it, it may be unclear to you which special treatment is intended. The dashboard’s matching behaviour is governed by the available configuration; the practical safeguard is to avoid designing confusing overlaps and to review the conditions together. Write down the event, threshold, and intended distinction before adding multiple rules.
For instance, a channel might reserve one variation for a larger tip and use the regular alert for other tip events. The reason for the alternate could be a longer thank-you message, not a louder sound. If you create several tiers, make the boundaries unambiguous in the controls and in their names. Your labels are for your own maintenance; they do not change the underlying matching rules.
After creating it, use the event’s variation controls to review, edit, enable, disable, or delete entries as needed. A variation you no longer want should be disabled or removed rather than left as a mystery for a future moderator. Keep the regular alert as a useful baseline so you can compare the special treatment against it.
Customize its visuals, sound, and text
Open the new variation and customise only what helps viewers recognise the event. Streamlabs’ configuration describes options such as image or animation, sound, layout, text, and other settings; the exact controls presented can vary by event and platform. Treat the controls actually shown in the dashboard as authoritative, rather than expecting all of them for every alert.
Choose visual assets that fit the size and pace of the channel. A small animated mark and a short message may be enough for a music stream. A business stream might use a clear label that identifies a customer action without covering the product demonstration. Keep text short enough to read while the stream continues; a long sentence can disappear before someone finishes reading it or obscure the content beneath.
Check the sound in the context of your ordinary alert. A distinct sound can help a viewer notice a qualifying event, but repeated loud or long sounds may become tiring on a continuous channel. If the stream is intended for study or sleep, mute or soften the special treatment where the available controls allow. Do not make sound the only meaningful distinction: some viewers watch muted.
Text should be accurate for the event and understandable without private context. Use a message that makes sense if the alert appears over a looped video several hours into a broadcast. Avoid promises, sensitive personal details, or a sentence that suggests a viewer has received a benefit you have not actually provided. If event data can populate text, inspect the available fields and make sure the result remains readable with longer names or amounts.
The purpose is not to make every variation more elaborate. A special alert can be distinguished by one change—such as a different image or a longer message—while keeping its position and general style familiar. That makes it easier to preview and easier for you to recognise if the wrong alert appears. If you edit the general theme later, check whether the variation still fits the revised appearance.
Preview and save the alert
Use the dashboard’s preview controls to inspect the variation before saving. Where a preview lets you choose an event or test state, use it to review the text, timing, animation, image, and sound together. A preview helps catch presentation problems, but it does not prove that the real event connection or trigger will work in your stream.
Check the alert against a normal viewing scene, not only against a blank editor background. Is the text legible over the content? Does the animation draw attention without hiding the important part of the video? Is the sound appropriate at the level your audience hears? If a name or message wraps awkwardly, simplify it or adjust the available layout controls.
Save after you are satisfied, then return to the event’s variation list and confirm the entry is present and enabled if you intend to use it. Reopen the variation if necessary to verify its condition and visual choices. This small review prevents a polished alert from remaining an unsaved draft or being disabled when you move on to OBS.
It can help to keep a note of the event, condition, and design intention outside the dashboard, particularly if someone else helps manage the stream. The note is not a substitute for checking the live configuration, but it gives you a simple reference when a threshold or sound needs changing. If you are also planning a long-running broadcast, it is worth separating alert changes from stream reliability checks; the guide to finding the cause of an OBS playlist stream going offline after a scene change addresses a different problem, but reinforces the value of testing a scene change deliberately.
Add the Alert Box to OBS
OBS Studio does not itself supply alert events. The alert provider supplies the alert or widget URL, and OBS displays it as a Browser Source. OBS Project’s alerts and chat box tutorial describes configuring alerts with a provider, copying the URL, and adding it to a scene; its alert FAQ also explains that OBS Studio does not directly provide stream alerts.
In Streamlabs, locate the Alert Box widget link or URL for the configuration you intend to use and copy it. Keep the URL private: it is a control link for your widget, not something to publish in a public chat or show on screen. The Streamlabs alert setup guide can help orient you to the provider-side setup, but use the current dashboard for the exact controls in your account.
In OBS, select the scene where alerts should appear, add a Browser Source, and paste the provider’s URL into its URL field. Set the source width and height to suit the overlay design and your canvas; there is no single dimension that suits every layout. If the alert is meant to sit in a corner, position the source and check the placement against the content viewers need to see.
Give the source a clear name, such as “Streamlabs Alert Box”, so it is not confused with a browser source for a chat panel or other overlay. If several scenes use the same alert box, decide whether to add or reuse the source according to your OBS scene setup. For a 24/7 channel, document which scene contains the alert source, because an alert configured correctly in a scene that is not live will not be visible to viewers.
If a scene collection or stream layout changes, verify the source in the active scene collection as well. A source can be hidden, placed behind another element, or sized for a different canvas. This is separate from whether Streamlabs has a valid event condition. For a continuous channel, a clear scene naming convention is useful in the same way that the OBS startup checklist for a 24/7 lofi stream is useful for checking which scene and sources should be active after a restart.
Test the trigger and troubleshoot display
Test in two stages: first the display path, then the event condition. Use the provider’s preview or test controls if available to confirm the Browser Source can render an alert in the intended OBS scene. Then check the actual configured trigger through a supported test method or a real eligible event, taking care not to assume that a preview has exercised the condition logic.
If nothing appears in OBS, confirm that the Browser Source contains the intended provider URL, is visible in the active scene, and is not covered by another source. Check its dimensions and position, then recheck the provider’s connection and saved settings. If the source is blank or stale, reload it in OBS where appropriate and consult the current provider and OBS guidance. Do not treat a working browser preview as proof the OBS source is correctly configured.
If the ordinary alert appears but the variation does not, inspect the event type and condition in Streamlabs. Verify that the selected platform is the one connected for that event and that the trigger you tested meets the configured rule. A test for an exact amount cannot be assumed to satisfy a minimum or different condition; match the test to the setting. Also verify that the variation remains enabled and saved.
If the wrong look appears, review whether the relevant variation is active, whether conditions overlap, and whether the alert box URL in OBS points to the intended widget configuration. A theme switch may explain an overall change in style, while a variation should account for an event-specific alternate. Change one setting at a time and preview again, rather than altering the theme, source, and trigger simultaneously.
For a channel that also runs from a computer overnight, alerts are only one part of the operating setup. Check that the intended scene is live and that the broadcast itself remains online; a Browser Source displaying a perfect alert is not evidence that the whole stream is healthy. If your concern is instead a pre-recorded programme that keeps running while your own computer is off, the guide to running a devotional stream from a VPS in India discusses that distinct operating choice. StreamNeo can remove the need to keep your own computer running for an uploaded video stream, but it does not configure Streamlabs alerts or remove the need to set up and check those connections.
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
Is a variation the same as a widget theme?
No. A variation is an alternate alert tied to a supported event condition, while a theme changes a broader set of widget settings. Choose based on whether one kind of event should look different or the overall style should change.
Can every alert event use the same conditions?
No. Available conditions depend on the platform and event type, and not every customisation is offered for every event. Review the controls Streamlabs shows for the connected event before planning a trigger.
Does OBS create the alert for me?
No. OBS displays an alert supplied by a provider, commonly through a Browser Source. You need to configure the provider and use its alert URL in the relevant OBS scene.
Why does the preview work but the variation not trigger?
A preview checks how the alert looks, not necessarily whether a real event satisfies the configured condition. Confirm the event type, platform connection, threshold, saved state, and enabled status, then test through a method that matches the rule.