An event list adds a small, persistent record of recent interactions to your YouTube livestream. You can add one as a direct source in Streamlabs Desktop, or add a provider’s widget or overlay URL as a Browser source in OBS Studio.
An event list is different from a pop-up alert: the list remains visible and accumulates recent items, while an alert appears briefly when something happens. The exact event types depend on the provider and the platforms connected to it, so check the current options in your provider’s dashboard before arranging your scene.
What an Event List Shows
An event list displays recent interactions, usually as a short stack of names and event labels. Depending on the provider and the account connections, entries might include follows, subscriptions, tips, hosts or other supported activity. OBS Project describes an events list as a listing of the most recent events; Streamlabs’ documentation gives examples including follows, tips, subscriptions and hosts. Neither description means every provider supports every event type on YouTube.
Think of the list as a modest record rather than a complete activity log. It has limited space, and its purpose is to help viewers see recent activity without waiting for a particular moment. If your devotional stream receives a new subscriber while a bhajan is playing, for instance, the event might appear among the recent entries and remain there while later activity replaces older entries.
Whether that example is available depends on the provider’s supported events and how your YouTube account is connected. Do not assume an event type shown in a tutorial for another platform will be available for your channel. Check the provider’s current event-selection controls and its connection status for the YouTube account you intend to use.
An event list is an overlay element, not a setting in YouTube’s live control room and not a built-in event feed in OBS. OBS is the scene-composition and streaming application here; the event data and its visual presentation come from the provider. The provider’s source is then placed into your scene like other visual elements.
If your stream is a pre-recorded loop rather than a presenter-led broadcast, consider whether a visible list adds anything for your viewers. On a local news playlist or a quiet study channel, a list can be useful if people regularly interact; otherwise it can compete with the programme. The same judgement applies to a 24/7 playlist scheduled in Castr: distinguish between the programme that runs continuously and the overlay that reports viewer activity.
Event List Versus Pop-Up Alerts
A pop-up alert is designed to call attention to an event as it happens. It appears over the scene for a limited time, then disappears. An event list is designed to stay on screen and show a selection of recent events. Depending on the widget, the two may use similar visual styling, but they serve different purposes.
| Feature | Event list | Pop-up alert |
|---|---|---|
| What viewers see | A continuing list of recent supported events | A temporary visual or audio cue for an event |
| When it appears | Remains visible as part of the scene | Appears when a configured event occurs |
| Best suited to | Keeping recent activity legible over time | Drawing attention to a moment |
| Main layout consideration | Persistent screen space | Short-lived interruption of the programme |
You can use both, but check how they behave together. If the list and alert occupy the same corner, an alert may cover names in the list. If a long alert animation obscures a face, a news ticker or a lyric line, move the elements apart or reduce the visual weight of one. For a music stream, you might prefer a compact list with no sound, while a presenter-led stream may benefit from a brief alert as well.
The distinction matters for audience expectations. A viewer who joins later can still see entries that remain in the list, but will not see an alert that has already finished. Conversely, viewers may notice a pop-up more readily at the moment it occurs. Neither element should be treated as proof that every interaction has been captured or that the provider has received data successfully.
Choose an Event-List Provider
Start with the software and overlay provider already in your setup. Streamlabs documents a direct Event List source in Streamlabs Desktop and a Widget URL route for OBS Studio. StreamElements documents overlays that you add to OBS through a Browser source; an overlay can contain several widget types, so you may need to edit the overlay itself to show only the elements you want.
The provider-specific steps are not interchangeable. A Streamlabs Widget URL belongs to its Streamlabs widget, while a StreamElements overlay URL refers to an overlay configured in StreamElements. Choose the appropriate instructions for the source you have created rather than pasting one provider’s URL into another provider’s editor.
| Your setup | Documented route | Check before adding it |
|---|---|---|
| Streamlabs Desktop | Add the Event List as a source in the scene | Confirm the desired events and style in the Streamlabs dashboard |
| OBS Studio with Streamlabs | Copy the Event List Widget URL and add it as a Browser source | Keep the URL private and check the widget’s settings |
| OBS Studio with StreamElements | Copy the overlay URL and add it as a Browser source | Check which widgets are included in the overlay and its dimensions |
The choice is mainly about fit and control, not a claim that one provider is more reliable, less expensive or better connected to YouTube. The documentation does not establish a controlled comparison on those points. Streamlabs documents event-type and appearance controls for its Event List; StreamElements provides overlay and widget editing, with controls varying by widget. If you want a single overlay that combines several components, StreamElements describes overlays that can include multiple widgets. If you want a direct Event List source in Streamlabs Desktop, Streamlabs documents that route.
For a plain OBS setup, the Browser source is the important mechanism: it displays a web-based overlay in a scene. OBS’s own guide explains Browser sources in the context of alerts and names Streamlabs and StreamElements as provider examples. That does not make an event list a live YouTube feature built into OBS; OBS is displaying the provider’s source. See the OBS black-screen checks if you are separately troubleshooting a video source, but do not confuse that issue with an event-list connection.
Use the provider’s official documentation for the current interface: Streamlabs’ Event List setup guide, StreamElements’ overlay guide, and the OBS Project’s guide to alerts and Browser sources. Menus can change, so treat those guides as a route to confirm against the controls currently shown in your account.
Add the Source in Streamlabs Desktop
In Streamlabs Desktop, open the scene where you want the list, add a source and choose the Event List widget. The list then belongs to that scene. If you have separate scenes for a full-screen song, a presenter and a break slate, decide whether the list should appear in all of them or only selected scenes; adding a source to one scene does not by itself make it appear in every scene.
After adding it, open Streamlabs’ Event List dashboard to configure the widget. The documented controls include theme, colour, included event types, animation, number of visible events, background, text colour, font, font size and animation speed. The available controls and event choices are provider-specific, and may change over time. Use the current dashboard rather than relying on a screenshot from an old tutorial.
A useful first pass is to set the list’s location and size in the scene, then choose a restrained theme that remains readable against your content. For a bright devotional image, for example, light text may disappear over a pale background; a simple background or outline can improve contrast. On a news loop, check that the list does not cover the ticker or a key caption. Do not make the list larger simply because its text is difficult to read: first check whether there is a clearer place for it.
If you use multiple scenes, test the source in each one in which it should appear. Confirm that it sits above the background video but does not cover a logo, lyrics or other essential information. Scene order matters: a source hidden behind an opaque element will not be visible even if it is configured correctly.
Add a Widget URL in OBS
For OBS Studio, obtain the source URL from the same provider that created the widget or overlay. With Streamlabs, sign in to its dashboard, open All Widgets, select Event List and copy its Widget URL. In OBS, open the intended scene, choose + in the Sources panel, select Browser, and paste the URL into the source properties. Save the source and check that it appears in the preview.
With StreamElements, copy the overlay URL from its dashboard or overlay editor. In OBS, add a Browser source and paste that URL into its properties. Set the Browser source’s width and height to match the overlay and your scene layout. StreamElements’ guide uses 1920 by 1080 as its default example unless the source resolution has been changed; use the dimensions appropriate to your own layout rather than treating that example as a requirement. Position and size the source in the scene after saving.
An overlay URL can contain a sensitive token. Treat it like a private access link: do not post it in a public chat, screenshot or forum. If you think it has been exposed, check the provider’s current account controls for a way to replace or reset it. This is a practical precaution because the URL identifies access to your overlay; it is not a reason to avoid using the Browser source.
A StreamElements overlay may include more than an event list. If the Browser source displays chat, alerts or other elements you did not intend to add, inspect the overlay editor and remove or disable the unwanted widgets there. Changing the size of the Browser source in OBS does not necessarily change the contents configured in the provider’s overlay.
StreamElements’ guide also discusses Browser source frame-rate settings, with 30 or 60 FPS depending on stream settings and computer capability. That is a configuration choice, not a promise of better performance. If the list is static most of the time, choose a setting consistent with your existing setup and test the scene; do not increase settings without a reason. You can find other OBS scene considerations in this guide to playing a video playlist in random order, though the event-list source itself is a separate overlay element.
Choose Events and Customize Appearance
Set the list to show only event types that make sense for your channel and that your provider actually supports for the connected platform. A dashboard might offer controls for follows or tips, for example, but the available options depend on provider and platform. A setting visible in one person’s account is not evidence that it will appear for every YouTube channel.
Keep the display useful rather than exhaustive. A small list with clear labels is easier to understand than a crowded one that competes with the main programme. If you are running a lofi station, a quiet corner with a few recent entries may suit the pace. A local news loop may need more clear space for headlines, so you could keep the list smaller or omit it from scenes where it overlaps text. These are layout choices; they do not alter which events the provider receives.
Check legibility at the size viewers are likely to see it. Text that looks readable while editing at full screen may be too small in a mobile view or compressed livestream. Give names enough room, use contrast against changing footage, and avoid placing the list where captions, a clock or essential lyrics appear. If a theme provides animation controls, use motion sparingly so the list remains secondary to the programme.
If your overlay includes alerts as well as a list, review both sets of settings. StreamElements notes that conflicting alert variations can stop an alert from playing as intended; if you use variations, check their conditions and settings in the provider’s current interface. Do not assume that changing the event list’s appearance also changes pop-up alert behaviour. They are separate elements even when they are managed from the same overlay.
Preview the List Before Going Live
Check the source in the scene before you start the public broadcast. First confirm that the Browser source or direct widget is visible, fits within the canvas and is not behind another source. Then check whether the text and background remain clear over the actual video or image content, not just over a blank scene. If you use multiple scenes, switch through each relevant scene and check placement again.
Next, confirm that the provider is connected to the intended YouTube account and that the desired event types are selected in its dashboard. Use the provider’s preview or test tools if they are available in the current interface. This is a practical check, not a guarantee that a real event will appear or that all event data will be delivered. The documentation does not establish a universal rule for when YouTube makes an event visible to a provider.
If the list is empty, work through the parts of the setup separately. Check the scene source and its visibility first; then inspect the URL or direct widget settings; then verify the account connection and selected event types. A Browser source that does not appear at all suggests a different problem from a source that is visible but has no entries. Avoid changing several settings at once, so you can tell which adjustment affected the result.
If it works in preview but not in the scene you use for the broadcast, check that you added it to the correct scene and that no scene-specific source is covering it. If it appears but is hard to read, adjust its position, dimensions or styling. If you are preparing a channel intended to run continuously, keep the event overlay separate from the playback plan: the Telugu music stream setup guide covers a different part of the job, while this guide concerns the visible event element.
If you do not want a computer running the video file simply to keep a long-running YouTube broadcast active, StreamNeo turns an uploaded video into a YouTube live stream that continues with your computer switched off. That addresses the playback side of a continuous channel; an event list still needs to be configured with its overlay provider and added to the scene you use.
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 an event list built into YouTube Live or OBS?
No. In these setup routes, a provider supplies the event-list widget or overlay, and OBS displays it through a Browser source. Streamlabs Desktop also documents a direct Event List source in its own application.
Can I show every YouTube event in the list?
Not necessarily. Event types vary by provider and connected platform, so check the options and account connection in the provider’s current dashboard. Do not assume a feature shown for another platform is available for your channel.
What is the difference between an event list and an alert?
An event list remains on screen and shows recent supported interactions. A pop-up alert appears temporarily when a configured event occurs; you can use both, but place them so one does not obscure the other.
Why is my OBS Browser source empty?
Check that the URL came from the provider that created the widget or overlay, that the source is visible in the correct scene, and that its dimensions suit the layout. Then verify the provider connection and event selections, and use its preview or test tools if available.