A live-stream event list keeps recent channel activity visible as a continuing part of your scene. An alert box is different: it is designed to show an event briefly in a popup, so adding one does not automatically give viewers a chronological history.
For a documented list-style setup, use a StreamElements overlay that displays its recents data, then add that overlay to OBS as a browser source. The exact events shown depend on the widget and the platform’s current support, so preview the specific activity you care about before relying on it during a broadcast.
Event list or alert box: what viewers see
An event list is a piece of the scene that remains on screen. It can show recent activity in sequence, so a viewer joining partway through a stream may still see earlier entries. StreamElements describes its recents data as a chronological list of the last 25 events. That is a documented behaviour of this feature, not a claim that every widget keeps the same history or that every event type appears in every account.
An AlertBox serves a different purpose. StreamElements documents it as a native widget that displays live events from the queue in a popup-like behaviour. That makes it useful when you want an event to call attention to itself and then disappear, but a popup alone is not a persistent recent-events panel. You can use both, provided each has a clear role and they do not compete for the same part of the screen.
Before choosing a widget, write down what a viewer should be able to see. “A new event should briefly appear” points towards an alert. “Viewers should be able to read a short list of recent events while they watch” points towards a list-oriented display. If you are building a YouTube channel around recurring recorded material, the layout decisions in a 24/7 recorded lecture stream setup offer a useful context for thinking about what needs to remain on screen.
Do not assume that a label such as “events” means a widget will show every activity you have in mind. The available event types and history can vary by tool and platform. Confirm the current documentation for the particular service and channel you use, then test the result in your scene.
Choose a recent-events widget
In StreamElements, open the Overlays area and create an overlay, or choose one you already use. Its getting-started guide describes creating an overlay and choosing a canvas resolution. Within that overlay, decide whether an existing widget meets the need or whether you require a custom widget that renders recent events as a list.
A built-in AlertBox is a sensible choice when the aim is a temporary notification. It is not, by itself, evidence that a persistent event list has been added. For a continuing list, look for a list-oriented widget or a custom widget that uses the documented recents data. The StreamElements widget-events reference explains the chronological recent-event data; check the current page for the event names and fields relevant to your configuration.
| Choice | What it is suited to | What to check |
|---|---|---|
| AlertBox | A brief popup when a live event arrives | Whether a separate persistent list is needed |
| Recent-events list | A continuing chronological view of recent activity | Which event types are represented and how entries are formatted |
| Custom widget | A tailored design or behaviour when a built-in widget does not fit | Whether you can maintain the code and verify its event handling |
A custom widget gives you more control over presentation and behaviour, but it also creates more places to troubleshoot: the code, event handling, text formatting and overlay rendering. StreamElements documents a first custom widget workflow, including a widget that responds to a follower event. Treat that as an example of event-driven customisation, not proof that all desired event types are available on every platform.
If you only need a simple list, start with the least complicated widget that documents the behaviour you want. If a channel has a particular visual style or needs different event formatting, a custom widget may be justified. In either case, verify the output rather than inferring capabilities from a preview image or a similarly named feature.
Connect the widget to your channel
A recent-events widget needs access to the event data it is meant to display. Follow the overlay tool’s documented connection steps for the channel and platform you use, and review any account authorisation prompt before approving it. The order and availability of options can change, so use the current StreamElements interface and documentation rather than relying on a click sequence from an old screenshot.
Keep the scope specific. This guide is about placing an event list in a YouTube live scene; it does not mean that every StreamElements widget or every event type has identical coverage on YouTube and other platforms. If your intended list includes a specific kind of channel activity, find that activity in the current platform-specific documentation or widget settings. If you cannot confirm that it is supported, do not design the scene as if it will definitely appear.
Once connected, check the overlay editor for the selected widget and its data source. If you use a custom widget, confirm that it is listening for the event type you intend to render and that the display code puts the event into the list. The custom-widget guide can help with the pattern, but the code and event data must match your own intended setup.
This is also the point to choose what belongs in the list. A compact recent-events panel can become hard to scan if it mixes several event labels, long names and additional text. Decide whether the viewer needs the event type, the account name, or both; leave out decoration that does not help them understand the entry. That makes later sizing decisions more straightforward.
Add the overlay to OBS as a browser source
When the overlay is ready, copy its overlay URL from StreamElements. In OBS, add a Browser Source to the scene where you want the list to appear, then enter that URL and set the source width and height to suit the overlay canvas. StreamElements’ YouTube SE.Live tutorial shows a browser source configured at 1920 by 1080 pixels. Those are the dimensions in that tutorial’s example, not a universal requirement.
Use dimensions that make sense for your scene. If the overlay canvas is made to match the stream resolution, it can be easier to position elements against the full scene. A smaller canvas may be more convenient if you want to treat the overlay as a smaller source and position that source within OBS. StreamElements’ overlay setup guidance covers choosing the canvas; the right choice depends on how you are composing your scene.
In OBS, use a clear source name such as “Recent events” so it is easy to identify if the scene contains several browser sources. Check that the source is visible in the scene’s source list and sits above the background video or image it needs to appear over. If it is below an opaque layer, the browser source may be working but hidden. Keep the overlay URL private in the same way you would treat other account-linked control links; share only what is necessary with people helping you set up the scene.
If you are new to OBS, make this change in a copy of the scene or while you can inspect the output before going live. A list should not be tested for the first time after the channel is already broadcasting. A change to the source dimensions, visibility or position can be checked in the OBS preview without changing your underlying video content. If you are also assessing how OBS fits into a long-running YouTube workflow, this comparison of YouTube Premiere and OBS for a Hindi news replay channel discusses the broader format choice rather than the widget itself.
Position and size the list
Place the list where it can be read without covering the important part of the stream. For a devotional channel, that may mean keeping text clear of the lyrics or the main image; for a study or ambience stream, it may mean avoiding the area where a timer or track title appears. There is no universally correct corner. Use the composition of your own scene as the guide.
In OBS, select the browser source and position and resize it in the preview. If you are using a full-canvas overlay, its elements may be positioned in the overlay editor while the source itself remains aligned to the scene. If you use a smaller overlay canvas, resizing and positioning the source in OBS may be part of the intended workflow. Be consistent about which canvas you are editing; otherwise, an element can appear offset or be clipped even though its settings seem reasonable.
Make the text large enough to read at the size viewers actually see, not only while the OBS canvas fills your monitor. A long channel name or event label may wrap, push other entries down or extend beyond the area allotted to the list. Allow some clear space around the text and avoid putting it directly over bright, patterned or moving imagery. If the background changes, check the list against the most visually busy part of the video as well as a quiet frame.
For a simple replay or music channel, other persistent elements may already occupy the screen. Before adding the list, look at the whole scene: title, logo, lyrics, captions and any information that helps viewers follow the programme. The YouTube end-screen guide for 24/7 streams covers a different viewer-facing element, but it is a useful reminder that overlays should have a defined purpose and not crowd the content.
Preview events and check readability
Preview the overlay in StreamElements and in OBS. Check both the placement and the information itself: do entries fit within the visible region, is the newest one easy to distinguish, and can you read the text against the actual scene? A screenshot of an overlay in an editor does not prove that the finished browser source will look the same at your stream’s output size.
Confirm the specific event types you expect to appear. The StreamElements documentation describes the recents list and custom widgets, but a reader should still verify the selected widget’s current event support for their channel. If the tool offers a preview or test mechanism for the chosen widget, use it to inspect layout and formatting. Do not assume that a preview event demonstrates that a real event from the connected YouTube channel has been received.
Think about what happens when entries vary in length. A short name may fit neatly, while a long one may wrap or make the list taller. Check whether the widget shows more than one entry at once, how it handles a new item, and whether older entries remain visible or move out of the frame. The documented recents behaviour refers to the last 25 events in its data; the number that can be legibly displayed on your scene depends on the widget and its dimensions.
If you intend to leave the stream running for long periods, previewing is part of preparation rather than a guarantee that the overlay will never need attention. Check it again after changing the scene, overlay, browser-source dimensions or channel connection. A small alteration to the video layout can make previously readable text disappear against a different background.
Troubleshooting missing or stale events
If the list is blank, work from the source towards the event. First check that the Browser Source is visible in the intended OBS scene, that it is above any covering source, and that the URL points to the overlay you edited. Then inspect the overlay itself: the widget should be present, enabled and configured to display the intended list rather than only a popup alert.
Next check the channel connection and event scope. A connected account does not establish that every event type is supported, and an alert widget receiving one event does not demonstrate that a separate recent-events widget is configured correctly. Revisit the current documentation for the chosen widget and platform. If a custom widget is involved, inspect its event handler and display logic against the documented event data; avoid changing unrelated code before you know which part is failing.
If entries appear but look stale, confirm whether the source is showing stored recent-event data or waiting for a new live event. Do not treat an unchanged list as proof of a broken OBS source until you have checked how the widget is supposed to update and whether an applicable event has occurred. Conversely, do not infer that a fresh item will appear merely because the browser source loads successfully.
When the Browser Source appears wrong after an edit, compare the canvas size in the overlay editor with the source dimensions in OBS. Also confirm that the correct source and scene are selected. A change made to one overlay will not alter a different URL already loaded in another scene. If you need to rebuild or adjust the wider broadcast workflow, the guide to keeping a YouTube stream connected when OBS reports a server disconnect is relevant to stream transport, though it does not diagnose event-widget data.
Make one change at a time and inspect the preview again. That gives you a clear way to tell whether the issue was source visibility, dimensions, the widget, or account/event configuration. If the current official documentation does not establish that your desired event type is supported, contact the tool’s support or choose a documented alternative rather than assuming a setting will make it available.
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 the same as an alert box?
No. An event list stays on screen as a continuing view of recent activity, while StreamElements documents AlertBox as a popup-like display for live events. If you need both a brief notification and a readable history, set up and preview the two behaviours separately.
How many events does StreamElements recents show?
StreamElements describes recents as a chronological list of the last 25 events. That describes the data feature, not how many entries will fit legibly in your scene or what every widget and platform supports.
Does an event list work for every YouTube event type?
Do not assume so. Check the current documentation and settings for the particular widget and channel connection, especially if you need a specific event type to appear. Preview the result before broadcasting.
Why is my browser source visible but the list empty?
A loaded source only shows that the overlay is rendering; it does not prove that the widget is receiving or displaying the event data you expect. Check the widget choice, account connection, event support and any custom-widget handling, then inspect the preview again.