Streamlabs Alert Box messages are customised in the dashboard after you choose a platform and an alert event. The event’s own settings control its supported message and presentation choices; general settings and Global Editing work more broadly, while variations apply a different alert when a supported condition is met.
Twitch and YouTube do not offer identical alert events or variation conditions. Set up only the events you need, make platform-specific choices, and preview and test the result in the scene where it will run before you go live.
Add the Alert Box to your setup
The Alert Box is a widget that displays alerts in your stream when an event occurs. In Streamlabs Desktop, add it from Sources. If you use another streaming programme, the route may instead involve the Streamlabs integration or adding a browser source from the dashboard. Follow the instructions for your software rather than assuming that every setup uses the same steps.
Start by deciding where the alert should appear. For example, you might want subscriber alerts over a YouTube music stream but keep them away from a lower-third used for local news. Add the widget to the relevant scene, then check its position and size against the content. A message can be well written and still be hard to read if it covers a face, a title, or the important part of a video.
The guide to choosing a playlist or OBS loop for a 24/7 meditation stream can help when you are deciding how a continuous YouTube scene is organised. The alert widget is one layer in that scene, not a replacement for the underlying video or audio setup.
If you have already added the widget but cannot find expected controls, first confirm that you are editing the intended Alert Box and active theme. Streamlabs themes can change widget and alert settings when switched. A theme change may explain why an alert looks different from the one you previously configured; check the active theme before rebuilding each event from scratch.
Choose Twitch or YouTube first
Connect or select the platform whose alerts you intend to configure. The dashboard’s available categories depend on the selected or connected platform. Streamlabs’ cross-platform alert guide describes alerts for several platforms, while its YouTube alert guide covers YouTube-specific choices.
Do not plan around the assumption that one event list will appear for both services. YouTube’s guide covers events such as subscribers, members and Super Chats. Twitch has its own event types, and its variation conditions can differ too. What you can configure depends on the platform, the event and the options currently shown in your dashboard.
If you stream to both platforms, treat each platform’s alerts as a separate pass through the setup. Check the destination before editing an event, and avoid writing a single generic message that implies the wrong action or relationship. A YouTube membership message should make sense to a YouTube viewer; a Twitch subscription message should make sense to a Twitch viewer. Keep the wording accurate to the event name shown in the tool.
This distinction matters for more than terminology. If a message, sound or animation is available for one event but not another, that is not necessarily a fault in your account. It may simply be an event-specific option. Use the controls actually offered for that platform and event instead of trying to force a matching configuration.
Select the alert event
Within the chosen platform’s Alert Box settings, select the event you want to customise. Work one event at a time. That makes it easier to understand which message and visual belong to a particular action, and it reduces the chance that a broad edit changes several alerts unintentionally.
Give each event a clear purpose. A brief acknowledgement may suit a subscriber or member alert, while a larger contribution might call for a more prominent treatment if the event supports one. Do not assume every event exposes the same text fields, media choices or timing controls. The dashboard is the authority for what is editable in that event.
Before changing anything, note what the event currently does. Check its message, image or GIF, sound, font, animation and duration where those options are available. If you are working on a live channel that already has an audience, this quick inventory helps preserve useful behaviour while you change one part at a time.
For a multi-platform channel, record the event and platform together in your own notes, such as “YouTube — Super Chat” or “Twitch — subscription”. This is especially useful if you return later to tune a message or if someone else helps with the stream. It also prevents a common source of confusion: editing an event under one platform, then checking the other platform and expecting the same result.
Customise event-specific messages and presentation
An event’s own settings are where you make choices for that alert, within the options the event supports. Depending on the event, the controls may include alert text or layout, image or GIF, sound, font, animation and duration. Text-to-speech is available only for supported alert types; it is not a universal setting for every alert.
Keep the message short enough to read while the stream continues. A useful message identifies what happened without making viewers parse a sentence over moving content. If you use a name or other event detail in the text, preview with realistic examples so you can see whether a longer name causes crowding or wraps awkwardly. Do not judge a layout only by the shortest possible test message.
Sound and motion need the same practical check. An alert may be visible but still distract from dialogue, a devotional track or a lesson if its sound is too prominent or its animation lasts too long. Conversely, a quiet visual treatment can be easy to miss over bright or fast-moving footage. Preview the alert over the sort of scene where it will appear, rather than on an empty canvas alone.
If the default artwork does not fit your channel, you can use an image or GIF where the event allows it. Keep text legible against the art and avoid putting essential words inside a moving image where they may be difficult to read. A simple, consistent visual system is often easier to maintain than a different style for every event. Streamlabs also offers pre-made widget themes; check what is included and how a theme affects the active widget settings before switching.
For a YouTube channel where viewer contributions are central, keep alert wording distinct from the payment or account controls themselves. The guide to setting up UPI details for YouTube Super Chat in India concerns those details; an Alert Box message is the on-stream response and does not configure them.
Use TTS with moderation in mind
For supported tips and bits alerts, Streamlabs documents controls for choosing a minimum amount and voice, as well as spam and profanity controls. Its text-to-speech guide says TTS is off by default. Check the current event settings rather than expecting speech to play automatically.
TTS changes the moderation workload as well as the sound of an alert. A threshold can limit which supported contributions trigger speech, but it does not make every submitted message suitable for broadcast. Review the spam filter, profanity controls and custom blocked words where offered, then test with representative alerts. Consider whether spoken messages fit the stream’s content and whether a moderator will be available to respond if a message is disruptive.
Use general settings for broad changes
General settings affect alerts more broadly than the settings for one event. Streamlabs documents controls that can include alert delay, moderation approvals, profanity filtering and custom blocked words. The exact controls available to you may depend on the setup and current interface, so read each label before changing it.
These controls solve different problems. An alert delay changes when an alert appears; moderation approval affects whether an alert waits for review; profanity filtering and blocked words affect message handling. They are not substitutes for one another. If viewers need immediate acknowledgement, a delay may not suit the channel. If messages can include free-form text or speech, moderation options may be more important than reducing the delay.
Set a broad rule only when it makes sense for the whole Alert Box. For instance, a blocked word that is inappropriate in every scene may belong in a general control. A delay that is useful for one event but not another may need an event-level treatment if the dashboard provides one. Check how a setting applies before assuming it affects only the alert currently on screen.
Make one change, save it, and preview more than one relevant event. This is a simple way to spot whether a broad setting changed an alert you meant to leave alone. If you have multiple platforms connected, verify the intended platform too; a general change should not be taken as proof that platform-specific event settings are identical.
Apply Global Editing carefully
Global Editing is for applying selected shared choices across alerts and variations, rather than editing just one event. Streamlabs’ cross-platform guide describes it as a way to update alerts and variations with the same settings. Depending on the controls available, shared choices can include font, TTS, animations, layout or duration.
Use it when you have a deliberate channel-wide style to apply. For example, if you want all supported alerts to use the same font and animation, a global change can save you from repeating the work. It is also useful when you have decided that a shared duration or layout should be consistent across the set.
The trade-off is scope. An individual alert may have a reason to look or behave differently: a major event might need a more visible treatment, while a routine acknowledgement should stay unobtrusive. Applying a shared setting can overwrite distinctions you have built into events or variations. Before using Global Editing, decide which properties should genuinely be common and which should remain event-specific.
After applying a change, inspect the individual events that matter most. Global Editing does not mean that every event supports every choice, nor that a shared setting will be appropriate in every context. Where individual settings remain adjustable, use them for deliberate exceptions and preview those exceptions separately. If a result seems unexpected, verify the active theme as well as the scope of the edit.
Set up variations for supported conditions
A variation changes an alert when an event meets a condition. It is not simply another platform-wide event. The available conditions depend on the platform and event, so create a variation only after confirming that the dashboard offers the condition you need.
Streamlabs’ variation guide describes conditions including subscription and bits conditions for Twitch, raid size, YouTube membership conditions and Super Chat amounts. These examples are not a shared menu available to every event on both platforms. Check the options presented for the particular event you selected.
A practical workflow is to add a variation under the relevant event, choose a supported condition, customise its message and presentation, then preview and save it. Make the distinction understandable. For example, a higher-value contribution might receive a more prominent acknowledgement if the event offers an amount-based condition; do not build the rest of your workflow around an amount condition if it is not available for that platform and event.
Variations can make a channel feel more responsive, but too many can be difficult to maintain. Keep a short note of what each one is intended to do, especially if you use separate Twitch and YouTube configurations. After an edit to a variation, test the variation itself as well as the base alert. A good-looking default does not prove that the conditional version still has the right message, sound or timing.
Preview and test before going live
Preview while editing, then test the finished alert in the destination setup. Streamlabs Desktop includes Test Widgets; if you use other streaming software with a browser source, Streamlabs says to test from its dashboard. The official cross-platform setup guide explains the general workflow, but the final check should use the software and scene you will actually run.
Check the whole alert, not just the wording. Confirm that the correct event fires, text remains readable, the image or GIF appears as intended, sound is audible at a sensible level, and animation and duration do not interrupt the content. For TTS, test a representative message and listen for both intelligibility and moderation behaviour. For a variation, verify the condition and the resulting version rather than testing only the base event.
Test against a realistic background. An alert that looks clear on a plain preview canvas may disappear over a bright video, overlap a logo or cover captions. If you run a playlist of different videos without a gap, remember that the composition can change from clip to clip; place the alert where it will not obscure essential information across the playlist.
If something is wrong, change one setting at a time and test again. This helps you distinguish a text issue from a theme, sound or scope issue. Keep a record of the working configuration before making wider edits, and recheck alerts after switching themes or changing the stream scene. A test done in a different scene or on the wrong platform is not a reliable check of the setup viewers will see.
If a continuous YouTube channel also needs attention when a broadcast drops, alert styling will not solve that separate operational problem. The automatic restart guide for a disconnected YouTube live stream covers that issue; keep the alert test and stream-continuity test as distinct checks.
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
Can I use the same Alert Box messages on Twitch and YouTube?
You can aim for a consistent style, but the available events and settings differ by platform. Configure and test each platform’s events separately, and use the options shown for the event you selected.
Does Global Editing replace event-specific settings?
Global Editing applies selected shared settings across alerts and variations, while individual settings can remain adjustable. Use it for choices you genuinely want to share, then inspect events where you intend to keep a distinct treatment.
Can every alert have text-to-speech or a variation?
No. Message, presentation and TTS options depend on the event, and variations depend on the supported platform and event conditions. Check the dashboard controls and preview the result rather than assuming an option is universal.
How should I test a browser-source Alert Box?
Use the Streamlabs dashboard test when the widget is running as a browser source in other streaming software, then check it in the intended scene. Confirm the message, layout, sound and any variation or TTS behaviour before going live.