A now-playing overlay is a webpage layered over your gameplay in OBS. Add it as a Browser Source, position it clear of the game’s important information, then test the composed output before streaming; the overlay will appear in a VOD only if it was part of the broadcast recording.
For a channel intended to run around the clock, plan the archive separately from the live channel. YouTube says streams longer than 12 hours may not be captured as archives, so use shorter sessions when you need VODs and keep a local recording as a backup.
Plan the label and where its information comes from
Start by deciding what “now playing” means for your channel. A gaming stream might show a game title, a current map, a session name, or the track playing underneath the game. These are different kinds of information, and an overlay can display only what its source provides or what you enter yourself.
A hosted overlay usually gives you a URL that you add to OBS. Before choosing one, check what information it can read, whether it updates automatically, and whether you can customise its appearance. Do not assume that a music overlay can identify your game, or that it can hear arbitrary computer audio and infer a song. For example, Now Playing documents track information through its desktop app connected to DJ software; that is a specific input path, not universal game or audio detection (setup guide).
If you only need a fixed label, such as “Minecraft survival — Day 12”, a text source in OBS may be enough. You can edit it between sessions, but it will not change by itself when you switch games or maps. If the text needs to update during a broadcast, you need a source that can actually supply those changes, whether that is a supported integration or a process for updating it manually.
Consider what the viewer needs at a glance. A short game or track name is usually easier to read over moving footage than a sentence. A label that includes a title, artist, session status and social handle may compete with the game itself, especially on a phone screen. Check the overlay at the size viewers are likely to see it, not only while it fills your desktop preview.
A hosted webpage also has trade-offs: it depends on that page loading in OBS, the provider’s update mechanism, and an accessible URL. A manually managed OBS text source has fewer moving parts, but changes require your intervention. Neither route is automatically more reliable in every setup. Decide which matters more for your stream: automatic updates, simple editing, control over styling, or fewer external dependencies.
If the URL is tied to your account, treat it as private. A person with access to an account-specific link may be able to use it. Now Playing’s documentation describes resetting a leaked overlay URL and replacing the old URL in OBS; check the provider’s current instructions if you use that tool (customisation guide).
Add the webpage as an OBS Browser Source
Open the OBS scene that you use for the YouTube broadcast. In the Sources panel, choose + → Browser, create a source, and paste the overlay webpage URL into its URL field. OBS describes Browser Source as a way to place a webpage in a scene, including for overlays and chat boxes (OBS Sources Guide).
Give the source a clear name, such as “Now playing”, so you can find it later. Keep it in the same scene, or in a scene nested into the broadcast scene, that actually feeds your stream. Adding an overlay to a scene you do not use on air will not put it in the broadcast.
The source order matters. In OBS, sources higher in the list appear above sources lower in the list. Place the Browser Source above gameplay if you want the label drawn over the game. If you have a frame, webcam, or alerts, check their order too; another opaque source placed over the overlay can hide it.
Enter the overlay’s URL exactly as provided and use any setup controls the provider documents. Some overlay services offer a simulated track or preview state so you can confirm that the page renders before relying on it. Follow those directions, but do not treat a provider’s preview as proof that the page will continue to update during a long live session. Test the actual scene and output you intend to use.
Browser Source has page dimensions separate from the OBS canvas. Set its width and height to the overlay provider’s recommendation or the dimensions needed by the webpage. For a 1080p canvas, Now Playing gives 1920 × 1080 as a standard example and advises matching a different canvas where applicable (dashboard guide). The correct setting depends on the overlay’s layout: a full-canvas transparent page and a small, tightly sized label are not the same design.
Once the page is loaded, inspect the OBS preview. If the text is missing, clipped, or incorrectly scaled, check the URL, the Browser Source dimensions, and any layout settings on the provider’s side. Refreshing a Browser Source can help when a page appears stuck, but check that the refreshed page returns to its intended state before going live.
Set dimensions and position the overlay
A Browser Source can be sized and moved in the OBS canvas. For a full-screen webpage, its dimensions may match your output canvas; for a compact overlay, the provider may specify different dimensions. Avoid changing the source’s proportions casually, as stretching a designed layout can make text or artwork look wrong. Use the preview and OBS transform handles to place the source where it belongs.
Keep the label clear of the game’s critical HUD: health, map, inventory, objectives, subtitles, and controls can occupy different parts of the screen depending on the game. A position that works in one title can obscure useful information in another. The bottom edge can be a sensible starting point for a gaming layout, as the overlay provider suggests, but inspect the actual game rather than treating any corner as universally safe.
Leave room around the label. Text placed flush against the edge can look cramped or be cut off on some screens. Also check whether the game has changing scenes or menus where the same area has a different purpose. If you rotate between games, test each layout or keep a separate OBS scene for each game so you can place the label deliberately.
If the overlay has a background, consider whether it remains readable over both bright and dark scenes. A translucent panel, outline, or shadow may improve legibility, but it should not cover more of the game than necessary. Check the provider’s styling controls and preview the result over representative gameplay. A design that looks clear against a static settings screen may disappear against a bright action sequence.
For vertical or non-standard output, do not blindly use a 1920 × 1080 page size. Match the Browser Source and overlay design to your actual OBS canvas and the provider’s documented requirements. Then check the final preview at its intended output dimensions. If the overlay is designed for a wide canvas, it may need a separate layout to fit a narrower scene without covering the game.
Check the composed stream output
The OBS preview is useful for checking composition, but a preview alone does not establish what YouTube receives or what a later VOD contains. Make a local test recording or a private or unlisted test stream if you need to confirm the encoded picture. Watch the recording back, including a moment when the overlay should change, and confirm the text is legible, correctly placed, and actually updating.
Check the full composition, not only the overlay in isolation. Does the label overlap an important game element? Is it visible against a bright scene? Is its text large enough when the video is viewed at a smaller size? Does a webcam, alert, or other source cover it? Make adjustments in OBS, then record again if the change affects placement, scaling, or source order.
A test should also cover the information path. If a provider has a test-track control, trigger it and verify that the expected label reaches the OBS scene. If you expect automatic updates, arrange a real change in the source data and check that the overlay changes too. A static label that appears in the preview confirms only that the page rendered at that point; it does not show that a later update will work.
YouTube’s live DVR and its finished archive are separate matters. DVR lets viewers pause or rewind during a live broadcast, but YouTube says its availability may be limited or unavailable for streams longer than 12 hours (DVR guidance). The later archive is subject to its own capture caveat, discussed below. Do not use successful live rewind as proof that a complete VOD will be available.
For a 24/7 channel, a short test cannot prove every future update will work throughout a day-long run. Check the overlay when starting each session and after changing its URL, design, game scene, or information source. If the overlay is essential to the content, include a way to notice a stale or missing label while the broadcast is running, and keep a fallback such as a static OBS text source you can enable if needed.
Test what appears in the VOD
The overlay must be included in the video sent to YouTube to appear in a VOD. A label visible only in an OBS panel, a separate local window, or a scene that is not on air will not be part of the stream’s composed picture. Make a short recording from the same scene and output settings you plan to use, then watch the file rather than relying only on what you saw while setting up.
Review more than the opening frame. Look at the start, a point after the overlay should have updated, and a point after a scene or game change. Confirm that the label is not clipped, covered, or left showing stale information. This is also a good time to check whether your game audio and any music are audible as intended.
If you use music metadata, remember that displaying a track title is not permission to broadcast the track. YouTube’s live-stream terms place responsibility for necessary rights, including music licensing rights, on the provider of the live content (YouTube livestream terms). An attribution label does not cure missing rights. Check YouTube’s current official guidance and make sure your content is cleared for the way you intend to stream and archive it.
A local recording and a YouTube VOD answer different questions. The local file can show whether OBS composed the overlay into your output; the YouTube archive shows what was available after YouTube processed the session. Check both when the VOD is important to your channel. If you are building a prerecorded channel rather than playing a game live, the broader workflow in guidance on always-on product video channels may help with planning the broadcast, but it does not replace testing this overlay in your own scene.
Plan around the 12-hour archive caveat
YouTube Help says a live stream under 12 hours can be automatically archived, but a stream that exceeds 12 hours may not be captured at all. This is a possibility, not a promise that every shorter stream will produce a complete archive. Read YouTube’s current Archive live streams guidance before building an archive workflow around a long continuous broadcast.
If you need a dependable sequence of VODs, plan sessions comfortably below the stated threshold. End each broadcast cleanly, check that its archive is available, and start the next session as a new broadcast. A continuous 24/7 presence and a single uninterrupted 24-hour-plus VOD are different goals; do not assume the latter follows from the former.
Shorter segments also give you natural points to check whether the overlay is still working. Before each session, verify the scene, the URL, and the displayed label. After ending, inspect the resulting archive and confirm that the overlay and its updates are present. YouTube’s documentation does not guarantee archive capture even for streams below 12 hours, so retain another copy if the footage matters.
There is an operational trade-off. More frequent session boundaries mean more starts, stops, titles or descriptions to manage, and archive checks to perform. A single long live channel may be simpler for continuous viewing, but it is a poor assumption to treat it as one reliable archive. Decide which outcome matters for your channel and make the process fit that need.
The overlay itself is not what determines whether YouTube archives the stream. It is part of the composed picture, while archive capture is a separate YouTube behaviour. If a complete record is important for a gaming series, schedule shorter broadcasts and make sure your recording plan remains active independently of YouTube’s archive processing.
Keep local recordings as backup
OBS can record locally while it streams, giving you a copy to check and retain if the YouTube archive is missing or incomplete. Set up recording deliberately before the live session: choose a destination you can find, confirm that the recording is enabled, and make a short test file that you can play back. A recording that was never started cannot serve as a backup.
Local files take storage and require attention. Long gaming sessions can create large files, so check available disk space and decide how you will move, keep, or delete recordings. Do not assume that the drive you normally use has room for repeated sessions. If the recording is valuable, test that it opens and contains the composed overlay before removing other copies.
When your computer is responsible for OBS, local recording also depends on that computer and its storage remaining available. If the machine sleeps, runs out of space, or stops, the local file may be incomplete. Keep the computer’s power and sleep settings appropriate for the session, and check the recording status during setup. These steps reduce avoidable surprises, but they do not guarantee a complete recording.
If keeping the broadcasting computer on overnight is the pain point, StreamNeo turns an uploaded video into a YouTube live stream that can run with your own computer switched off. That addresses the need to leave a personal machine running for a file-based broadcast; it does not replace the need to test an OBS overlay workflow or keep a local backup when a VOD matters. It is YouTube-only, so make sure that suits your destination.
For a conventional OBS gaming broadcast, this article’s overlay method still relies on the scene and output you configure in OBS. If your wider question is how to run a prerecorded channel without maintaining a home machine, compare the practical trade-offs described in choosing a cloud service for a prerecorded YouTube channel. For a desktop that must remain part of your setup, checking the bitrate and resolution settings is relevant to the output, though it does not address overlay data or VOD capture.
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 show the name of the song playing on my YouTube gaming stream?
Yes, if your chosen overlay receives track information from a supported source and you add its webpage to OBS as a Browser Source. Check the integration it actually supports; a music tool may rely on DJ software and should not be assumed to identify arbitrary system audio. Showing a song title does not give you rights to broadcast the song.
Will the overlay appear in the finished YouTube VOD?
It should be in the video if it is part of the composed OBS output sent to YouTube, but test rather than assume. Record a local sample or run a private or unlisted test, then inspect the result. YouTube’s archive capture is a separate issue, especially for streams longer than 12 hours.
Can I leave one stream live for 24 hours and get a complete archive?
YouTube says streams longer than 12 hours may not be captured at all. For VODs, plan shorter sessions and keep a local recording; even a shorter session is not a guarantee of archive capture. Check YouTube’s current archive guidance before relying on it.
What should I do if the label stops updating?
Check whether the source information is changing, whether the overlay page is still loaded, and whether the Browser Source is in the scene being broadcast. Refreshing the source may help, but verify the label afterwards with a test recording or output check. If you need the label during a live session, have a manual fallback ready.