A now-playing overlay can show a podcast episode title or a music track on your YouTube live stream. The usual method is to add either a manually updated OBS Text Source or an overlay webpage as an OBS Browser Source.
These are different metadata tasks. A track overlay may update when its connected music source changes, but it will not automatically discover the podcast episode you are discussing unless the overlay provider has a suitable episode data source.
Decide what “now playing” should show
Start by writing the exact label you want viewers to see. “Now playing” may mean the podcast episode currently being discussed, the music underneath the conversation, a devotional track, or a short status such as “Live discussion”. Each one needs a different source of information.
For a podcast episode, the useful fields might be the episode title, series name, guest name, or release date. For background music, the useful fields are usually artist and track title. A provider that receives music-track changes may know the latter but have no connection to your podcast feed or player.
This distinction matters because an attractive overlay can still display the wrong information. If the page is connected to a music player, it cannot be expected to identify an episode from your podcast unless that episode is reported through the same supported data source.
Before choosing a tool, answer three questions:
- What should the main line say: an episode title, a track title, or fixed text?
- Who or what will update it when the content changes?
- What should viewers see if the source stops updating?
For example, suppose you broadcast a recorded devotional discussion with a bhajan underneath it. You may want the episode label to remain “Morning Prayer: Episode 12” while the music label changes several times. Treat these as two separate labels rather than asking one overlay to infer both.
A long-running channel also benefits from a fallback. If the connected page fails, viewers should still see a sensible fixed label, or the overlay should disappear cleanly without covering the host. This is more useful than relying on a blank box that remains on screen after its data has gone stale.
If your video includes a visual loop as well as audio, keep the label consistent with the rest of the scene. The guidance in this complete guide to 24/7 aquarium and relaxation visual loops is also relevant to keeping overlays readable without disturbing a calm background.
Choose a text label or an updating track overlay
There are two practical routes.
An OBS Text Source is the simpler choice when you are labelling the podcast episode itself. You type the title into OBS, style it, and change it when the episode changes. OBS describes Text Sources as customisable text sources in its official sources guide. This gives you direct control over the wording and does not require an external metadata connection.
The trade-off is producer effort. Someone must edit the text before or during the relevant segment. That may be fine for a scheduled podcast with a small number of episode changes, but it is less convenient when music tracks change frequently during an unattended stream.
An updating overlay is a webpage supplied by a provider. You add its URL to OBS, and the page changes when the provider’s connected track source reports a new track. The reviewed Now Playing setup documentation describes this workflow and says its overlay can be added to OBS as a Browser Source without plugins or scripts. See the provider’s OBS overlay setup guide for its account-specific process.
That route reduces manual editing for supported music metadata, but the important phrase is “for supported metadata”. It does not establish automatic podcast episode detection. Before using a music-oriented overlay for a podcast, confirm that its connected data source actually reports the episode title you need.
| Requirement | OBS Text Source | Updating overlay webpage |
|---|---|---|
| Podcast episode title | Suitable when you type the title yourself | Suitable only if the provider receives episode metadata |
| Music track changes | Requires manual editing unless you use another process | Can update when the connected track source changes |
| Setup | Built into OBS | Requires an overlay URL and provider account or connection |
| Visual control | Direct control in OBS | Depends on the provider’s page and its available settings |
| Failure behaviour | Text remains until you change it | Page may stop changing, show old data, or fail to load |
| Preview | Check the OBS scene before broadcast | Use the provider’s preview or test mode, then check OBS |
A third-party widget can also be added as a Browser Source. Streamlabs documents adding a widget URL to OBS or another supported streaming application, followed by setting its dimensions and position. Its overlay instructions describe the general route, but you still need to verify that the selected widget exposes podcast episode metadata rather than only alerts or decorative elements.
Choose the manual route when accuracy and predictable wording matter more than automatic changes. Choose an updating route when the provider’s data source is clearly compatible and you have a way to detect a stale label.
Get the overlay URL and verify its data source
If you are using an updating service, find the overlay URL in its dashboard rather than copying the address of an ordinary account page. The overlay URL is normally a dedicated webpage intended to be displayed inside streaming software.
The Now Playing dashboard documentation says its overlay area supplies the URL and recommended Browser Source size, and that its preview can send a sample track to check the result. Its dashboard guide is the appropriate place to confirm the current controls, because provider interfaces can change.
Before adding the page to OBS, test the data path. Change or simulate a track if the provider offers a sample function, then check whether the overlay shows the expected title and artist. If you need an episode title, test an episode-shaped value, not just a music track, and confirm that the source is documented to support it.
Do not treat a page that loads as proof that the metadata is correct. A browser page may open successfully while showing a placeholder, an old track, or a generic message. The useful test is whether the intended field changes when the connected source changes.
Check these points before moving to OBS:
- The URL is the overlay URL, not the provider’s dashboard address.
- The connected source is the player, feed, or integration that reports your intended data.
- The visible fields match your requirement, such as episode title rather than artist and track.
- The page has a usable fallback when no data is available.
- The provider’s preview displays the same content you expect to send to viewers.
For a manually maintained episode title, you do not need an overlay URL. Prepare the exact text in advance, including capitalisation and any series or guest information, then create the Text Source directly in OBS. If your episode titles contain long names, decide where you will shorten them before broadcast rather than allowing an important word to run behind another element.
If you are not yet able to create a live broadcast, resolve that separately from the overlay. This guide to YouTube verification, two-step verification, and live feature unlocks covers channel access issues that can prevent a stream from starting, but it does not supply podcast metadata.
Add a Browser Source in OBS
Open the OBS scene that will contain the podcast video, camera, or visual loop. In the Sources panel, choose the option to add a Browser Source, then give it a name that identifies its role, such as “Podcast episode label” or “Music now playing”. Clear names make later troubleshooting easier when a scene contains several text and media layers.
Paste the overlay URL into the Browser Source address field. Set the width and height using the provider’s recommendation as a starting point. If the provider gives no useful recommendation, choose dimensions that leave enough room for the longest expected title and then adjust them while viewing the scene.
OBS’s sources documentation explains the general source model: a Browser Source displays a webpage inside the scene, while a Text Source supplies editable text. The source itself is separate from the YouTube broadcast. OBS captures the page as part of the scene and sends the combined output to YouTube.
Click to apply the source and look at the canvas. If the page is blank, first check the URL by opening it in an ordinary browser. Then check whether the overlay needs an active account session, whether the provider’s preview has data, and whether the Browser Source is hidden behind another source.
The source order matters. In OBS, sources higher in the list are generally rendered above sources lower in the list. Place the label above the video or background layer, but below any frame or graphic that should sit over it. If a label appears to be missing, use the eye control and source order to rule out visibility and layering before changing the provider settings.
For a manual episode label, add a Text Source instead. Enter the title, choose the font and colour, and apply the source. You can update the wording later without rebuilding the scene. Keep the source name specific so that you do not accidentally edit a lower-third, location label, or other text element.
Size and position the overlay
Treat the Browser Source dimensions as the page’s working area, not automatically as the size that should occupy the whole canvas. An overlay can have transparent space around its text, so a large source box may be correct even when the visible label is small.
Place the label where it does not cover the host’s face, subtitles, episode artwork, a guest name, or information that viewers need to follow. For a devotional or study stream, a lower corner may be quieter than the centre. For a local news loop, leave the ticker, headline, and station identity unobstructed.
Use OBS’s transform handles or source properties to adjust the box. Resize proportionally when the provider’s layout depends on a particular aspect ratio. If the letters become too small after scaling, increase the source area or return to the provider’s recommended size instead of repeatedly shrinking the same page.
Check the label against the actual output resolution. A title that looks clear on a large editing monitor may become difficult to read in the delivered stream. Look for thin fonts, low contrast, and long lines. White text over a bright video area is especially easy to lose, while a modest background panel or shadow can make it readable without dominating the scene.
For an episode label, consider the longest title you will use, not only the short test title. If the provider’s layout wraps text, confirm that the second line does not collide with the bottom of the source. If it does not wrap, decide whether to shorten titles consistently or use a wider source.
A fixed Text Source often gives more control over this problem because you can set a predictable line length. An external page may offer theme and typography controls, but those controls differ by provider. Do not assume that a Browser Source gives you the same styling options as text created inside OBS.
Keep separate labels separate when their update rules differ. A static episode title can occupy one area while an updating track label sits beneath it. This makes it clear which text is meant to remain constant and which text should change when the music changes.
Preview the scene before going live
Preview the complete scene, not only the overlay page. Start with the background, camera or recorded video, audio visual elements, episode label, and track label together. Then check what happens during the transitions you expect to use.
For an automatic overlay, send a sample or cause a known track change through the connected source if the provider supports that test. Confirm that the displayed value changes, that the old value is replaced, and that the new value is not truncated. The provider’s preview is useful, but the final check must happen inside the OBS canvas because scale, source order, and other graphics can change the result.
For a manual episode title, edit the Text Source with a second test title. This confirms that you know which source to change and that the wording remains readable when it is longer. Return it to the correct title before broadcast.
Watch for a stale-state problem. If the provider stops receiving data, the last track may remain visible even though it is no longer playing. That is not necessarily an OBS fault. Decide whether an old value is acceptable for your channel. If it is not, use a provider feature or manual process that lets you show a neutral message such as “Music information unavailable”.
Also test the page after restarting OBS or reopening the scene. A layout that appears during initial setup may behave differently when the source reloads. Confirm that the URL is still present, the source is visible, and the page can obtain its data without a manual browser login that will not be available during an unattended broadcast.
If the long stream itself develops audio drift or a timing mismatch, the overlay is not the only thing to inspect. This guide to audio out of sync on long streams and permanent fixes covers a separate problem, but it is worth checking because viewers experience the label and audio as one broadcast.
Make a short private or unlisted test if your workflow allows it. Watch the result as a viewer rather than only through the OBS preview. Check whether the label remains legible at the player size you expect, whether it covers important content, and whether the audio and displayed track appear to agree.
Make the overlay dependable for a long stream
A now-playing overlay adds another dependency to the scene. The video may continue while the external page is unavailable, or the page may remain visible while its data source stops reporting changes. Plan for both situations.
For a manual episode label, write down the update point in the running order. If an episode changes after an advertisement, intro, or scheduled segment, make the text change part of that hand-off. A simple written cue is often more reliable than expecting someone to remember it during a busy broadcast.
For an automatic track overlay, record the name of the connected data source and the provider’s expected behaviour when no track is available. Check it after a source change and after a restart. If the overlay is important to the channel, keep a simple Text Source behind or beside it as a fallback, but hide it during normal operation so the scene does not become crowded.
Keep the design restrained. The label should answer the viewer’s question without competing with the podcast. A title, artist, and small provider mark may be enough; extra animations can make a long stream harder to follow and harder to test.
If your main goal is an always-on YouTube channel rather than a live production desk, StreamNeo removes the need to keep your own computer running by taking an uploaded video, your YouTube stream key, and the broadcast workflow into the cloud, with monitoring and automatic restarts when the stream drops. The overlay still needs a verified data source and a scene that displays it correctly, so test those parts before relying on an unattended schedule.
Do not confuse stream continuity with metadata accuracy. A broadcast can remain live while the episode label is wrong, frozen, or unrelated to the audio. Include metadata checks in your pre-flight routine alongside the title, thumbnail, audio, and privacy setting.
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 a music overlay automatically show my podcast episode title?
Not by default. A music-oriented overlay can update when its connected track source reports a new track, but that does not prove it can read podcast episode metadata. Use an integration that documents support for your episode source, or update an OBS Text Source manually.
Should I use a Browser Source or an OBS Text Source?
Use a Browser Source when a provider supplies a compatible overlay webpage and you want its connected data to update. Use an OBS Text Source when you need a dependable, manually controlled episode label or when no suitable metadata integration exists.
Why is my Browser Source blank in OBS?
Check the URL, the provider preview, the source visibility, and the source order in the scene. Also confirm whether the page requires an account connection or data from a player that is not currently reporting anything.
How do I know the overlay will work during a long broadcast?
Test a known title or sample track in the provider preview and then check the same change inside OBS. Reopen or restart the scene, confirm the source reloads, and decide what viewers should see if the connected data source stops updating.