Skip to content
streamneo.
Tools12 min read

How to Display Now-Playing Track Titles on a YouTube Radio Stream

Compare OBS overlays, Windows media controls and metadata files to show current track titles on a YouTube radio stream.

sn.
StreamNeoPublished 4 October 2026
Worth sharing?

A YouTube livestream does not automatically turn the music playing on your computer into a changing title graphic. To show the current track, you need to capture its metadata in the playback environment, then render that information in your OBS scene.

The right method depends on where the audio plays: a YouTube page in a browser, YouTube Music in a browser, and the YouTube Music desktop app are different sources. Match the overlay or metadata reader to that source, then test track changes, long titles and competing audio before you rely on it overnight.

Why YouTube does not add track labels to the video

Your stream has two separate parts: the audio and video you send, and the information YouTube associates with the live broadcast. The broadcast title and description identify the stream as a whole; they are not a feed of the song currently playing on your computer. The YouTube Live Streaming API documentation describes broadcast resources and their metadata, not an automatic per-track graphic.

A track name can be available to the operating system or music app without being part of the video sent to YouTube. OBS has to receive that information somehow and draw it as a text or image element in the scene. Think of the overlay as a small bridge between the audio player and the picture viewers see.

That separation is useful when you choose a workflow. A title typed into the YouTube description will not update itself as a playlist advances. Likewise, adding the YouTube playback page to OBS is not the same as adding an overlay that reads the page's metadata. Use a method documented for the playback source you actually use, rather than assuming every browser or app exposes track details in the same way.

A title graphic also says nothing about whether you have permission to use the music in a livestream. Metadata display and music-use permissions are separate questions; check the applicable current guidance and permissions for your tracks.

Locate the metadata where audio plays

Start by writing down exactly how your radio audio reaches the stream. Is it a playlist playing on YouTube in Chrome or another browser? Is it YouTube Music in a browser tab, the YouTube Music desktop app, or a separate internet-radio player? That small distinction often determines whether an overlay sees the right title at all.

Then choose one metadata route:

  • Browser overlay: a compatible overlay or extension reads supported playback information and displays it through an OBS browser source.
  • Operating-system media controls: a companion tool reads media information exposed to Windows and supplies an overlay for OBS.
  • App metadata files: a bridge associated with a particular player writes the title and artist to files that OBS reads as native text or image sources.

The OBS forum resource Music on stream describes support for YouTube and YouTube Music, including using YouTube chapters or a playlist in the video description as title inputs. That is a source-reported capability, not a reason to skip testing: confirm the specific playback page and input mode you plan to use.

If you are building an always-on music station, this is one part of the broader operating plan. The guide to starting a 24/7 lofi music stream covers the channel and stream setup around the playlist; here, the concern is how to put each track name into the picture.

Use an OBS browser-source overlay

A browser-source overlay is a web-based graphic that OBS places on top of the scene. It is not the YouTube playback page itself. The overlay gets track information from a compatible capture method, then renders text, and sometimes artist or artwork, as a separate visual layer. This keeps the title independent of the video source and lets you position it like any other scene element.

A practical setup sequence is:

  1. Pick an overlay that explicitly supports your playback source, such as the relevant YouTube page or YouTube Music mode.
  2. Follow its instructions for enabling the metadata reader or extension and connecting it to OBS.
  3. In OBS, add the overlay as a Browser source, using the URL and options supplied by that overlay's own documentation.
  4. Place it over the part of the scene reserved for track information. Style the title and, if available, artist name so they remain legible against both dark and light parts of the background.
  5. Start audio in the intended player and check that the overlay changes when the next track starts.

The Music on stream resource describes a theme editor and CSS customisation, which can help you fit the title into a devotional, lofi or local-radio layout. If you use YouTube chapters or description playlists as its title input, make sure the chapter or playlist labels match the track sequence you are actually broadcasting. A mismatch is not a display bug; it is inaccurate input.

Do not infer that embedding a YouTube video in an OBS browser source will isolate its title or reliably expose playback details. Those are separate workflows. Use the overlay's documented metadata route, and make sure the browser source is layered above your background graphics rather than obscured behind them.

Browser overlays are attractive when you want a ready-made layout and your playback source is supported. Their trade-off is dependence on the overlay's capture method: if the source changes, an extension stops working, or playback is moved to another app, the text may stop updating even while viewers still hear music. Keep a note of which browser and player combination you tested.

Use OS media controls or metadata files

If you prefer a local toolchain, there are two useful alternatives. One reads media information that the operating system exposes; another writes metadata to files that OBS can load. They suit different playback apps and have different failure modes, so do not treat them as interchangeable versions of one universal overlay.

A community project called NowPlaying-Universal documents a route using Windows Media Control with the OBS TUNA plugin. Its README lists browser YouTube and YouTube Music among its verified sources, and its setup calls for Windows, OBS, TUNA and a local web server. You can read the project's setup notes before deciding whether those requirements fit your machine.

The useful feature of a media-control approach is that it can pick up a title exposed by a supported browser without relying on chapter labels. The limitation is source selection. The project documentation notes that when more than one browser audio source is active, the most recently active one may be selected. When it stops, an earlier source may not return until a track-change event. Close unrelated audio tabs and test that hand-off rather than trusting the first successful title.

For the YouTube Music desktop app, a separate community bridge, ytmusic-obs-nowplaying, writes title and artist information to files for OBS text and image sources. Its project README describes enabling the app's plugin, running the receiver, then pointing OBS sources at the generated files. This is specifically an app-based route, not a guarantee for the YouTube website or every operating system.

File-based sources fit a scene where you want OBS's native text styling or separate artwork and title elements. They also make the path from metadata to graphic visible: if the title file stops changing, you can narrow the issue to the player, bridge or file-reading source. One behaviour to plan for is stale text. The bridge README says the last title remains if the YouTube Music app is fully closed, so test how that looks and decide whether your scene should retain it, hide it or replace it with a neutral message.

Use an OS media-control workflow when the player is known to expose its media session and the documented dependencies are acceptable. Use a file bridge when you specifically run the supported desktop app and want native OBS sources. If either route adds more moving parts than you want to maintain, a browser overlay supported by your exact playback source may be simpler.

Add text or image sources in OBS

Once the metadata route is chosen, treat the graphic as part of the scene rather than an afterthought. Give the title a predictable space, keep it clear of YouTube's own interface areas and any channel branding, and use contrast that survives the backgrounds behind it. A title that is technically updating but unreadable at phone size has not solved the viewer's problem.

For a file-based bridge, create the OBS text source with the file option enabled and select the title file specified by the bridge instructions. Add artist text separately if the workflow provides it. If artwork is written to a file, add an image source and point it to that image. Exact file locations and source options depend on the project; follow its current README rather than guessing paths or copying settings from a different bridge.

For a browser overlay, add its provided page as a browser source and keep the source dimensions and transparency settings consistent with its instructions. Put it above the background but below any foreground elements that should cover it. Lock its position once placed so an accidental drag does not move the title during a long broadcast.

Keep source names descriptive: for example, distinguish the track title, artist and artwork rather than naming everything “Browser Source”. If a title becomes stale, that makes troubleshooting quicker. The same habit helps if you later add a second scene or make a clean copy for a different channel.

The display method does not dictate whether you need a local computer running during the broadcast, but a local OBS workflow does rely on its player, bridge and scene being available when the title should change. If you are choosing between a home machine and a hosted workflow, compare the practical operating trade-offs in AWS EC2 cost for 24/7 YouTube live streaming in India and the guide to streaming an internet radio station from a Windows mini PC. Those pages address the wider broadcast arrangement; they do not replace checking which metadata reader supports your audio player.

Handle long titles and scrolling

Track titles often exceed the space reserved for them, particularly where a filename or release title includes a devotional collection, remix note or featured artist. Depending on the font and source, a long line may be clipped, wrap awkwardly or end with an ellipsis. Check the rendered result in the actual OBS scene rather than assuming the overlay will shorten it in a useful way.

Choose the treatment that suits the channel. A fixed-width label can show the opening words and artist, while a smaller font may fit more text but become difficult to read on a phone. A two-line layout can preserve the full title, though it takes more screen space. A scrolling line can reveal a long name over time, but it moves and can be harder to scan if the viewer looks away and returns.

Do not assume every overlay offers scrolling, or that a setting described in an old forum post still exists in its current version. Check the tool's current controls, then test a deliberately long title and an ordinary short one. If it cannot scroll, consider shortening the displayed title at the metadata source only if that will not confuse the track identity, or allocate a wider title area in your scene.

You can also separate the information by importance. Keep the track name visually primary and the artist secondary; omit artwork if it forces the title into a narrow strip. For a radio stream where listeners may join midway, a stable title card is often easier to read than an animated treatment, provided it does not hide other scene information.

Test track changes before going live

A title that appears correctly for one song may still fail at the transition. Make a short rehearsal in the same scene and with the same player you will use for the live channel. Verify the current track appears, advances to the next title, and behaves sensibly when playback pauses, stops or closes.

Test these cases before scheduling an overnight broadcast:

  • Change tracks and wait long enough to see whether the overlay updates at the expected transition, not just on initial launch.
  • Pause and resume, then stop playback. Note whether the last title remains, clears or changes to a default state.
  • Play audio in another tab or application, then stop it. Confirm that the metadata reader still follows the intended radio source.
  • Use a long title, an artist with a long name and any non-Latin text your playlist contains. Check that the result is readable in the stream preview.
  • Restart OBS and the player in the order you would use after a computer restart. Confirm that the bridge or browser extension reconnects rather than relying on a one-time manual refresh.

For a Windows Media Control setup, the multiple-source case deserves particular attention: two active audio tabs can change which source is considered current, and a stopped source may not be selected again until another track event. For the YouTube Music desktop bridge, check the closed-app behaviour because a previously written title can remain on screen. These are documented workflow caveats, not reasons to assume the tools will fail; they are reasons to rehearse the cases that matter to your stream.

Keep the test recording or preview open long enough to inspect title changes at normal viewing size. A label that looks fine on a large OBS monitor may be too small on a phone. If your station uses a playlist file or rotating schedule, run through a few different entries rather than testing only the first track. For broader live-production checks, see live streaming best practices for YouTube creators.

If you change browser, player, OBS scene or overlay version, repeat the relevant tests. The metadata route is part of the broadcast chain: a change upstream can leave the stream sounding normal while the graphic silently shows an old title. A simple pre-live check of the scene preview is more useful than discovering that mismatch from a viewer after the channel has been running for hours.

When the playback source and title layout have passed your test, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.

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

Does YouTube automatically show the song playing on my computer?

No. YouTube's live broadcast metadata is separate from the changing playback metadata available to your player or operating system. You need an overlay or a metadata-to-OBS workflow to render the track name in your scene.

Will one overlay work with YouTube, YouTube Music and every computer?

No. Browser overlays, Windows media-control tools and desktop-app bridges each have their own supported sources and dependencies. Check the tool's current documentation against the exact browser, app and operating system you will use, then test it in OBS.

Can OBS scroll a long song title instead of clipping it?

That depends on the overlay or source styling; scrolling is not a universal OBS behaviour for every title input. Check the current tool controls and rehearse with a long title, then use a wider label, smaller type or a two-line layout if scrolling is unavailable or difficult to read.

Does showing the track name mean I can stream the music?

No. A title overlay only displays metadata and does not establish music-use permission. Check the current official guidance and the permissions that apply to the tracks and use you have in mind.

YOU’VE REACHED THE END

Keep the ideas coming.

More guides, useful tools and a little help for your next broadcast.

Back to the journal ↗
YOUR NEXT READ

A little more to explore.

More Tools guides ↗ · All topics ↗