The Streamlabs Chat Box adds viewer messages to a livestream as an on-screen source. You can add it through Streamlabs Desktop, the Streamlabs Plugin for OBS, or a browser source using the widget URL; choose the route that fits the software and theme you already use.
The widget is configured in Streamlabs and displayed in your scene by your streaming software. Its settings and scene behaviour are not identical across routes, so check the result in the software and scenes where you intend to use it rather than assuming one setup carries over unchanged.
What the Streamlabs Chat Box Does
A Chat Box is an overlay that displays chat messages on your stream. It is a visual source in a scene, not a replacement for the chat window you use to read and moderate messages. You can position it over a video, background, or other scene elements, then adjust its appearance and behaviour through Streamlabs settings.
The important distinction is between configuration and display. Streamlabs provides the widget settings and, for the browser-source route, a widget URL. Streamlabs Desktop and the Streamlabs Plugin for OBS also provide direct widget-source workflows. Your streaming software determines where that source sits in a scene and how it behaves when you switch scenes.
This makes the widget useful for a YouTube channel that needs visible messages over a devotional video, local news loop, study stream, or other live programme. It also means the chat box should not be treated as a single setting that automatically appears everywhere: each scene and source setup needs to be considered.
Before adding it, decide whether messages should be prominent or secondary. A small box in a corner may suit a music stream where the main video should remain clear; a discussion-led broadcast may give chat more room. Think about message length as well as the background, since a box that looks tidy with short messages can obscure more of the picture when viewers write longer ones.
Choose a Setup Route
Use the route that matches your existing workflow. The direct Streamlabs Desktop source is the straightforward fit if you already build scenes there. The OBS Plugin adds Streamlabs’ widget integration to OBS, while the browser-source method works by pasting a widget URL into a browser source in OBS or compatible software. A browser source does not require the plugin.
| Route | A sensible fit when | Main consideration |
|---|---|---|
| Streamlabs Desktop widget source | You already make and manage scenes in Streamlabs Desktop | Direct widget sources use the active Streamlabs widget theme. |
| Streamlabs Plugin for OBS | You use OBS and want its Streamlabs widget integration | You need to install the plugin and sign in. |
| Browser source with widget URL | You use OBS or compatible software, or need a theme that is not active | You copy the URL and set the source dimensions to suit the scene. |
These are alternative ways to put the widget into a scene, not three promises of identical controls. In particular, theme activation matters for the direct Desktop and Plugin sources; a browser source can use a copied URL for a theme that is not active. Streamlabs explains its widget theme behaviour, and its Chat Box setup guide describes the direct routes and widget controls.
A practical choice is to start with your current software, then consider whether you specifically need a different theme or prefer not to add a plugin. Avoid changing streaming software just to add this overlay unless you have another reason to change. If you are still choosing a broader setup for a continuous YouTube stream, the trade-offs in comparing 24/7 streaming services with a free plan are a separate decision from how a chat widget is installed.
Add Chat Box in Streamlabs Desktop
Open Streamlabs Desktop and go to the scene where you want the messages. Use the add-source control, choose Widgets, then select Chat Box and add it. The precise wording or placement of controls can change between versions, so if the editor differs from what you see, refer to Streamlabs’ current guide rather than searching for an identical screen from an older walkthrough.
After adding the source, adjust its size and position in the scene preview. Drag it clear of any titles, logos, lower thirds, or important parts of the video. If you are asked whether to add an existing source or create a new one, choose the existing source when that is the same widget you already use and intend to share. Creating another can leave duplicate boxes or duplicate notification sounds in the scene.
Open the Chat Box settings to adjust its look and message behaviour. The source placement in the editor and the widget’s settings are related but distinct: resizing the source changes the space it occupies in your scene, while the widget settings control how the chat content is presented. Preview both, especially if you have changed a theme or message style.
If the appearance does not match your intended design, check which widget theme is active and whether the scene collection has a theme override. Streamlabs documents that direct Desktop widget sources use the active theme. A theme selected elsewhere may therefore not be the one this source displays. If you need a particular inactive theme, consider the browser-source route and its URL instead of repeatedly adjusting the wrong direct source.
Before you move on, look at the complete scene at its normal output size. The editor preview can make a chat box feel larger or smaller than it will look to viewers. Leave room for a long username or message, and check that the bottom or side of the source is not cut off by the scene boundary.
Add Chat Box with the OBS Plugin
If you use OBS and want Streamlabs’ direct widget integration, install the Streamlabs Plugin for OBS and sign in. Then open the plugin’s Widgets tab and use Add beside Chat Box. Open the widget’s settings button to configure the box. Streamlabs’ official Chat Box instructions are the reference for the current plugin workflow.
Once added, treat it as a source to place and size in the intended scene. Keep it away from scene elements that need to remain legible. Check the source in OBS’s preview and, if possible, with an actual stream preview before relying on it for a scheduled broadcast. A source can be present in one scene without being present in another, and plugin settings should not be assumed to fix that scene structure automatically.
The Plugin route is useful when you want integration inside OBS rather than copying a URL. Its trade-off is the extra installation and sign-in step. If plugin installation is not desirable or a specific theme is not active, the browser-source method is a distinct alternative; it does not depend on the plugin.
As with Streamlabs Desktop, direct plugin widget sources use the active widget theme. If the theme you expect is missing, verify the active theme and any scene collection override first. Do not assume that choosing a theme in one place necessarily changes a direct source that is following another active selection.
Use a Browser Source
The browser-source route puts the Chat Box into OBS or another compatible application without using the Streamlabs OBS Plugin. In the Streamlabs Dashboard, open Chat Box and copy its Widget URL. In your streaming software, add a Browser Source, paste the URL into its address field, and confirm. Streamlabs describes locating and using widget URLs in its widget URL support guide.
Set the browser source’s width and height to suit the area you want it to occupy. If the preview does not fit or update as expected, check those dimensions and the source’s FPS setting. These are source properties, not a universal recommended size: a box intended for a narrow corner needs different dimensions from one spanning a wide portion of the screen. Adjust them against your actual canvas and preview.
A widget URL is tied to its widget configuration. Treat it as specific to your setup: do not publish a personal URL in a guide, screenshot, or public message. If the URL has been copied from the wrong configuration, the displayed theme or settings may not be the ones you meant to use. Go back to the Dashboard, confirm the intended Chat Box, then copy its URL again.
This method can also be useful when the theme you want is not active for direct Desktop or Plugin sources. Streamlabs’ theme guidance describes using a widget URL for an inactive theme. That flexibility comes with a little more manual work: you must keep the URL and source dimensions aligned with the appearance you want. If you change the widget configuration later, check the browser-source preview rather than assuming the scene has updated in the way you expect.
Configure and Position the Widget
Start with the visual settings, then decide how messages should behave. Streamlabs documents controls including Hide Message After, Always Show Messages, Chat Delay, Hide Chatters, and Custom Bad Words. Dashboard labels can change, but their purposes are practical: control how long a message remains, keep messages from fading, delay when they appear, suppress common bots or commands, and filter selected words.
Use persistence settings with the rhythm of the stream in mind. A fast-moving conversation may become difficult to read if each message disappears quickly; a quiet devotional or ambience stream may have little chat, so leaving messages visible can make the overlay feel stale. Try the setting that suits your programme, then review the result with representative messages rather than judging it from an empty box.
A chat delay can give moderators time to act before a message appears on the stream, but it also means the overlay no longer reflects the conversation immediately. Hiding common bots or commands can reduce clutter, while custom word filtering can exclude terms you do not want shown. These controls are not a substitute for moderation or a guarantee that every unsuitable message will be caught.
Place the box where it has a clear background and does not cover important content. For a video loop, avoid covering faces, captions, or the subject of the shot. For a study stream, keep it away from the text viewers came to read. If the background changes between scenes, test the box against each one; a style that is legible on a dark background may be difficult to read on a bright one.
Keep the visual design restrained enough that a long message remains readable. If the box is too wide or too tall, it can dominate the picture; if it is too small, messages may wrap or disappear from view. Adjust the source bounds and widget settings together until the overlay fits the scene, then check at the resolution and layout that viewers will actually see.
For an always-on YouTube channel, the overlay is only one part of the broadcast. It is worth considering how it fits alongside the video source and recovery plan: for example, planning a backup for a 24/7 YouTube live stream helps you think about what happens when the main broadcast setup needs attention. StreamNeo can remove the need to leave your own computer running for a file-based 24/7 broadcast, but it does not configure this chat widget or replace checking the scene in your streaming software.
Check It Across Scenes
A source that works in one scene may not be present in another. After adding Chat Box, inspect each scene where you want visible chat and confirm the source is included, correctly positioned, and layered above the background but below any element that should cover it. If you copy a scene, verify the resulting source arrangement rather than assuming every source setting was inherited as intended.
For browser properties, Streamlabs recommends turning off Shutdown source when not visible for the Chat Box. The vendor’s guide says this helps avoid interrupting timed settings and having chat cleared when you switch scenes. This is a useful setting to check when the box is expected to persist across scene changes, though it does not mean every route or scene will behave identically. Confirm the behaviour in your own setup.
Notifications need separate attention. If you use Chat Notifications and want their sounds in more than one scene, Streamlabs recommends including the Chat Box in each scene where you want those notifications. If you do not want the box visible in a particular scene, you can place it beneath a full-screen visual element. The source can then remain part of that scene while the visual element obscures the chat display.
Make a short scene-change check before a long broadcast: show a scene with chat, switch to one without visible chat, then return. Confirm the messages and timing behave as expected, and listen for unintended duplicate sounds. Repeat after changing themes, replacing a source, or updating the scene layout. For a continuous channel, interruptions can be inconvenient at any hour; related planning for recovering a 24/7 stream after an internet outage covers broadcast recovery rather than widget setup, but both checks belong in a reliable run-through.
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 the Streamlabs Chat Box built into every OBS setup?
No. OBS users can add it through the Streamlabs Plugin or by creating a browser source with a Streamlabs widget URL. A browser source does not require the plugin, and the plugin route does require installation and sign-in.
Do I need the OBS Plugin to use the Chat Box?
No. The plugin is one documented route, not a requirement. You can also use Streamlabs Desktop’s direct widget source or add the widget URL as a browser source in OBS or compatible software.
Why does my widget theme look different from the one I chose?
Direct Streamlabs Desktop and Plugin sources use the active widget theme, so check the active selection and any scene collection override. If you need an inactive theme, Streamlabs documents using its widget URL in a browser source instead.
Will chat and notifications continue when I change scenes?
That depends on source presence and properties. Streamlabs recommends unchecking Shutdown source when not visible in the browser properties, and including Chat Box in every scene where you want Chat Notifications; check the behaviour in your own scenes.