If your YouTube radio stream plays music in a browser, a now-playing overlay built for YouTube or YouTube Music is usually the most direct way to show the current title. If Nightbot controls song requests, its current-song file is a better fit; if viewers choose tracks through a queue, StreamElements is designed for that workflow.
The important choice is not the appearance of the label but where the music is playing. A title tool can only show useful information when it is connected to the playback method and when the source contains usable track metadata.
Identify where the music is playing
Start by tracing one complete song through your setup. Is a browser playing a YouTube playlist or YouTube Music? Is Nightbot handling requests and playback? Or do viewers submit songs to a managed request queue before they are played?
These routes can look similar to someone watching the broadcast, but they expose different information to your streaming software. A browser extension may read the page and its available track information. Nightbot can write the current request to a local text file. A request widget can display queue information supplied by its own service. None of these should be treated as a universal detector for every kind of audio.
This distinction matters particularly for a 24/7 channel. A title that updates correctly during a short test can still become misleading when the playlist changes format, a video has no chapters, or a request queue is paused overnight. Before choosing an overlay, write down the actual playback path:
- Where does the audio start?
- What decides which track plays next?
- Does that source expose a title, artist, uploader or request name?
- Is the title needed as an on-screen label, in chat, or both?
If the stream is built from uploaded programmes rather than live browser playback, a title overlay may not be the right first problem to solve. You may need to divide the programme into labelled scenes or publish a schedule instead. For a continuous music source, however, one of the three workflows below should usually give you a clearer route.
Choose a title source that matches the workflow
The following comparison is more useful than choosing an overlay by appearance alone.
| Route | Best fit | What it displays | Main limitation |
|---|---|---|---|
| Music on stream browser extension | YouTube or YouTube Music playing in a browser | A customisable now-playing overlay using YouTube chapters or a description playlist as title inputs | The source must contain usable metadata, and compatibility should be checked before relying on it |
| Nightbot App current-song output | Nightbot Song Requests on Windows or macOS | Current-song information written to a local file that OBS can display as text | It is tied to Nightbot's request workflow, not arbitrary browser playback |
| StreamElements Media Request widget | Viewer requests and queue management through StreamElements | A media-request widget with queue controls and optional video display | It is a request feature, not a documented general detector for unrelated YouTube playback |
| YouTube Music in this video | Checking metadata already associated with some videos | Song and artist information in the video description | It is not a general live overlay and can be incomplete or absent |
For browser playback, the Music on stream route is the closest match. Its OBS resource listing describes support for YouTube and YouTube Music, with YouTube chapters or a playlist in the video description available as title sources. That does not mean every playlist will produce a correct label. A video may have no chapters, a description may contain an incomplete tracklist, or the format may not match what the extension expects.
For Nightbot Song Requests, a plain text source is often easier to understand and maintain than a browser overlay. Nightbot's official App documentation explains that its Windows and macOS application can write current-song information to a file in the Nightbot folder under Documents. OBS can then read that file as a text source.
StreamElements belongs in a different part of the decision. Its Media Request feature is useful when the audience is meant to add YouTube media, and the queue itself is part of the channel format. It should not be selected merely because a stream contains YouTube audio. If the stream plays an unrelated playlist outside that queue, the documented widget is not established as a general way to detect it.
YouTube's own metadata is useful as a check, not as the main overlay plan. The YouTube Help page about Music in this video explains that song information appears only for some videos. It can be missing when YouTube does not have sufficient rights-holder data or has not identified the music.
Set up Music on stream for browser playback
Choose this route when the music is playing directly in a browser tab through YouTube or YouTube Music, and you are comfortable adding a browser-based extension to that playback workflow.
Check the source before styling the overlay
First open the actual video or playlist that your channel will use. Look for chapters in the YouTube timeline or a tracklist in the description. If the source uses one long video with chapters, check whether the chapter names are meaningful titles rather than generic labels such as “Part 1” or “Music”. If the description contains a playlist, check that each entry has the title and artist information you want viewers to see.
This check prevents a common mistake: spending time designing an attractive label when the source has no reliable title data. The extension can use the supported inputs, but it cannot create accurate track names that the video does not provide.
Add the extension and configure its source
Install the Music on stream extension from its current resource page, then follow its own setup instructions for the browser and playback page. Avoid copying settings from an old tutorial without checking the extension's current installation and compatibility notes. The resource listing records its own update history, but browser and YouTube behaviour can change independently.
Select the title input that matches the source. Use chapters when one video contains a sequence of tracks divided by chapter markers. Use the description playlist when the video provides a readable tracklist there. Do not select a source simply because it is available in the menu: if your video has no usable chapters, a chapter-based label cannot provide dependable results.
The resource describes customisation for the now-playing element, including long-title scrolling and hiding while paused. Keep the first version plain. A text line containing artist and title is easier to read against a static background than a heavily animated panel, especially on a devotional, study or ambience channel where the label may remain visible for long periods.
Place it in the broadcast
Add the overlay according to the extension's instructions, then position it where it does not cover subtitles, devotional text, weather information or the main visual. If the channel uses a fixed background, reserve a small title area before you build the rest of the scene.
Keep the title readable at the final stream resolution, not only in the OBS preview on a large monitor. A long Hindi, transliterated or mixed-language title may wrap or scroll differently from a short English title. Check both cases before you settle on the font size and width.
If you run a 24/7 channel from a local computer, the browser, OBS and the playback page all become part of the overnight chain. Use the guide to monitoring a 24/7 YouTube music stream for silence alongside your title test. A correct label is not useful if the audio has stopped while the overlay continues displaying the last song.
Use Nightbot's current-song file with OBS
Choose Nightbot when Nightbot Song Requests controls which track is played. This workflow is less about reading an arbitrary browser page and more about passing a current value from the request application to OBS.
Nightbot documents an application for Windows and macOS that writes current-song information into a file in its Documents/Nightbot folder. The application output can be customised in the Song Requests settings. In OBS, add the relevant file as a text source, using the file-output option rather than typing a fixed title.
The practical sequence is:
- Install and sign in to the Nightbot App using Nightbot's current documentation.
- Configure Song Requests and the current-song output format.
- Locate the output file in the Nightbot folder under Documents.
- Add the file to the OBS scene as a text source.
- Format the text so it can accommodate the longest title you expect.
- Start a controlled request and confirm that the displayed value changes when playback changes.
The file is the handoff between Nightbot and OBS. OBS is not identifying the song from the audio. It is displaying the text Nightbot has written. That makes this route clear and predictable when Nightbot is the source, but it also defines the limitation: if music starts elsewhere, the file may remain unchanged or show the last request.
Nightbot's request interface can also show details such as the track title, uploader, duration, song link and requester. Its .songs current command can report the current title in chat. That can be enough for a small channel that wants the information available to viewers without adding a permanent visual label.
Use a simple format first, such as Artist — Title. Add the requester only if that information helps the channel. For a devotional or family-friendly station, a long request line can compete with the content and create more moderation work than value.
Nightbot also warns that streaming copyrighted music can have negative consequences for a stream. It recommends using licensed or free music and restricting requests to an appropriate channel playlist. Showing a song title does not give you permission to play the recording, so review the current rights information separately. The article Can I Play Copyrighted Music in a 24/7 YouTube Live Stream? covers that distinction in more detail.
Consider StreamElements for request queues
StreamElements is relevant when viewer requests are part of the broadcast design. Its Media Request feature lets viewers add YouTube media to a queue, while the creator manages what is played. The corresponding widget can be shown on stream, and its settings include options such as showing or hiding the video.
This is a different job from displaying the title of whatever happens to be playing in a browser. A queue widget can tell viewers what has been requested and help you manage the order. It is a reasonable choice for a community radio format where listeners submit tracks and the presenter approves them. It is not the natural choice for a pre-built YouTube Music playlist that no one is requesting from chat.
The StreamElements guide describes using the widget through an OBS.Live browser-source integration and through a dedicated overlay. Follow the current instructions in the creator dashboard rather than assuming that an old browser-source URL or layout still applies. The guide was updated on 17 July 2026, so check the current version before documenting your final setup.
Decide whether you want viewers to see the video itself. Hiding the video can leave a progress bar and a more compact queue display, which may suit a radio-style scene. Showing video may be useful when the visual content is part of the request, but it can compete with your channel artwork and change the shape of the scene.
Moderation is part of this route. A public request queue needs rules for unsuitable titles, repeated requests and tracks that do not match the channel. A queue tool may make submission easier, but it does not remove the need to decide what your channel is willing to play or whether you have the necessary rights.
Add and position the overlay
Once you have chosen the source, treat the title as one scene element rather than as the centre of the broadcast. Add it to the scene that is actually live, not only to a scene used during testing. If you have separate scenes for daytime, overnight, announcements or prayer programmes, check whether the title source is present in each one where it is needed.
A useful label normally answers two questions quickly: what is playing, and who is performing it. If the source supplies only a video title, do not silently present that title as a verified artist-and-song pair. Keep the format faithful to the available data.
Use a background or outline that preserves contrast over light and dark artwork. Leave enough width for a long title, but set a sensible maximum so one unusual filename does not cover the rest of the scene. If the tool offers scrolling, make the movement slow enough to read. If it offers a paused-state rule, decide whether the last title should remain visible or disappear while playback is stopped.
For a plain OBS text source, use a font and size that remain legible on a mobile screen. Avoid placing the label in the exact area where YouTube's own player controls or live-chat elements may appear in screenshots shared by viewers. For an Indian audience, test titles in the scripts your source actually uses, including Devanagari if applicable, rather than checking only Latin characters.
A cloud workflow can remove a different problem from this setup. When a file and YouTube channel are ready, StreamNeo lets you upload the file once, provide the YouTube stream key and leave the broadcast running without keeping your computer switched on. It is useful when the operational pain is leaving a browser and OBS machine running overnight, but it does not turn arbitrary music into identified metadata, and it is separate from the browser, Nightbot and StreamElements title workflows described above.
Test title changes during playback
Do not test only whether the first title appears. Test the moments when title systems usually reveal their limitations.
Start with a normal track and confirm that the title appears in the intended scene. Then change to a second track and watch for an update. If the source is a browser playlist, use one item with a short title and one with a long title. If the source is Nightbot, submit a controlled request and confirm that the file changes rather than merely checking the old value in OBS. If the source is StreamElements, add two permitted requests and verify both the queue and the on-screen widget.
Pause the playback. Check whether the overlay hides, freezes or continues showing the previous title. Each behaviour can be acceptable, but viewers should not be led to believe that a frozen title is still playing. Resume playback and confirm that the title returns or updates as expected.
Test a source with incomplete metadata. YouTube's Music in this video information may be absent, and a description playlist may contain a missing artist or inconsistent punctuation. Decide in advance whether the display should show the available title, a neutral message, or nothing. Do not fill gaps by guessing.
Then test the operating conditions that matter overnight. Switch scenes, restart the browser page if that is part of the workflow, and reopen OBS if the title source is local. Check that the Nightbot file remains at the expected path and that the browser extension still sees the intended page. For a long-running channel, review the checklist for testing a YouTube RTMP setup before starting a 24/7 stream before going live.
Watch for stale text. A stale title is more damaging than a missing title because it appears authoritative. If the music changes but the label does not, remove the label temporarily or correct the source rather than leaving the previous track displayed.
Finally, confirm that your title tool and your playback source agree about what a “song” is. A long YouTube video with chapters may change titles within one video. A request queue may regard each requested video as one item. A radio automation system may use its own track database. The display should follow the system that actually decides what listeners hear.
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 YouTube automatically show the song currently playing?
YouTube may show song and artist information in its Music in this video section for some videos, but this is not a general live overlay. It can be missing when identification or rights-holder metadata is incomplete, so do not use it as the sole title system for a radio stream.
Which option is best for a YouTube Music playlist in a browser?
A Music on stream browser workflow is the closest match among the options covered here. Check that the playlist or video provides usable chapters or a description tracklist, because the quality of the displayed title depends on those inputs.
Which option should I use with Nightbot Song Requests?
Use Nightbot's current-song file and add it to OBS as a text source. This follows the information source that controls playback, unlike a browser overlay intended for a different workflow.
Is showing the title the same as having permission to play the music?
No. A title display only labels the content. Review YouTube's current guidance and the licence terms for your music separately; Nightbot also warns that copyrighted music can have negative consequences for a stream.