A YouTube radio stream needs both audio and video: a still image can supply the visual while your radio feed supplies the sound. To show now-playing information, add a text layer to the encoder’s video output and connect it to current artist and title metadata; YouTube Studio manages the live broadcast but does not create that graphic.
The practical work is making those pieces meet reliably: a legible station image, metadata that changes when the track changes, and an encoder that sends the combined result. Build and test the visual before connecting it to YouTube, then use the Live Control Room to check what the platform receives.
Plan the station visual and track information
Start by deciding what viewers need to see when they open the stream on a phone. A station logo, station name and a clear now-playing line are usually more useful than a busy collage. Keep important elements away from the edges, where the player’s controls or screen cropping may obscure them. Use a high-contrast background and a font that remains readable when the video is reduced to a small player.
Separate fixed information from changing information. Your logo and station name can be part of a single still image. Artist and track title need to come from the radio source’s metadata if you expect them to update automatically. A manually edited graphic will stay as it is until someone changes it; it is not a substitute for a metadata connection.
Check the metadata your source actually supplies. Some sources provide separate artist and title fields; others provide a combined label, incomplete values, or no metadata at all. Decide how the overlay should behave when a field is blank: for example, show the station name or a neutral “Now playing” label rather than leaving a broken template on screen. Do not assume that a music player, playlist, or audio URL exposes metadata in a form your chosen graphics workflow can use.
Think through long titles and different scripts before styling the layer. A short Latin-script title may fit easily while a long devotional recording title or a Hindi title may wrap or be clipped. Decide whether to use one line, two lines, or a shortened display, and test the actual font and language you plan to use. If you need a separate explanation of the video requirement, see whether a radio station can stream to YouTube Live without video.
Choose an encoder or graphics workflow
The encoder produces the audio and video sent to YouTube. You can use software on a computer or a standalone hardware encoder; YouTube documents both broad classes and maintains a directory of encoder options. Choose based on the graphics you need, the available equipment, and how you plan to keep the stream operating—not on the assumption that one type is required for radio.
| Workflow | Where the visual is assembled | Useful when | Trade-off to plan for |
|---|---|---|---|
| Graphical encoder software | In a scene with image, text and audio sources | You want to position and preview layers visually | You must keep the computer, software and source media running |
| Scriptable media workflow | In a configured video and audio pipeline | You can maintain a repeatable configuration and metadata hand-off | Setup and recovery may need technical attention |
| Standalone hardware encoder | In the device’s supported graphics controls | You need a dedicated appliance and its feature set fits your layout | Check that it supports the metadata-driven text workflow you require |
A graphical scene is often the clearest way to arrange a fixed logo and a changing text layer, but the fact that a scene can display text does not mean it can read your radio source’s metadata. Confirm that connection separately. OBS, for example, can compose image and text sources; the exact route for making text change depends on your metadata source and any additional integration you choose. Do not treat an example configuration as proof that your own source will work the same way.
A scriptable workflow can combine a still image, radio audio and changing text. The Liquidsoap book’s YouTube example documents an image as video and metadata-driven text as part of a composed stream. Its example is a documented approach, not a claim that every source supplies compatible metadata or that its settings fit every channel. Hardware is not mandatory; check the actual product’s supported graphics and metadata features before choosing it.
Your choice also affects unattended operation. A computer-based setup depends on that computer and its software continuing to run, while a standalone device has its own configuration and monitoring requirements. In either case, plan what you will check after a disconnect, power interruption, or source failure. An always-on channel is an operating process, not just a scene layout.
Add the logo and now-playing text
Create the fixed visual first. Set the station logo against a background that gives it enough contrast, then add only the supporting details viewers need. Export or prepare the image at the dimensions and format your encoder accepts. Keep an original copy so you can revise the layout without rebuilding the station artwork.
In your encoder, place the image as a video source and add a text layer above it. For a static-only version, enter a fixed label and confirm the composition. For changing now-playing text, connect the text layer to the artist and title values supplied by your audio or playlist system. The key path is: the source reports track metadata, the graphics workflow reads it, and the encoder renders the result into the outgoing video. If any link is missing, the image may stream correctly while the text remains blank or unchanged.
Choose a format that is informative without making the title hard to read. “Artist — Track” is compact; adding album, station frequency and programme details may crowd the screen. If your station plays long-form devotional recordings, a title-only display can be clearer than trying to fit every credit. Keep the text layer’s dimensions generous enough for the longest realistic title, and decide whether it should wrap, scroll, or truncate. Test rather than assuming the encoder’s default text box will behave well.
Preview transitions between tracks. When a new item begins, check whether the metadata arrives at the same time as the audio, whether it briefly disappears, and whether a missing artist field leaves awkward punctuation. Some sources may update metadata only at particular points or may not provide it at all. Your fallback should be deliberate: a fixed station label is better than an overlay that exposes template syntax or stale information.
Keep the station visual within the encoder output. YouTube Studio’s stream setup and Live Control Room are for configuring and managing the broadcast; they do not author a persistent encoder-side logo and metadata overlay. If you are familiar with adding an image source in a scene, the OBS bhajan-stream workflow is relevant background, but the metadata connection still needs to be configured and checked for your own source.
Connect audio and video to YouTube Live
Before sending anything, enable live streaming for the channel and open YouTube Studio’s Live Control Room. YouTube says first-time live streaming may take up to 24 hours to become enabled, so do not leave channel activation until the moment you plan to launch. Create or select the broadcast, then use the server URL and stream key shown for that stream in your encoder. YouTube’s encoder setup instructions describe this connection.
Treat the stream key as a secret. Anyone who can use it may be able to send a signal to your channel, so do not put it in a public screenshot, shared document, or source code. If you think it has been exposed, replace it in Studio and update the encoder configuration. Copy the values shown for your own stream rather than relying on an endpoint copied from an old tutorial; available ingest details and protocol support depend on the setup.
Select the composed video output and the radio audio source in the encoder. A static image can provide video while the audio continues, but verify that both are present in the outgoing signal. Start the encoder and wait for the Live Control Room preview. Use that preview to confirm that the stream has arrived, that the picture is the intended composition, and that the audio can be heard. The stream and broadcast are related but distinct parts of YouTube Live: the encoder sends media, while the broadcast is the viewer-facing event managed in Studio.
If you are building a loop or a continuous feed, plan how the media source will behave at transitions and after a reconnect. A guide to sending a prerecorded stream to primary and backup ingest URLs covers a different part of the workflow; it does not remove the need to check your encoder’s own signal and the current values Studio provides. For an audio-only station, do not omit video: the still image is the visual signal that accompanies the radio sound.
Test text updates and readability
Test before making the stream public. First, play several tracks locally through the source and watch the text layer. Confirm that the artist and title change for each item, that fields are in the intended order, and that a blank or unusual value does not make the overlay confusing. If your source exposes metadata separately from its audio output, verify that your chosen workflow can actually read those fields.
Next, inspect the encoded picture at the same output size you intend to send. A text layer that looks large on a desktop preview can become difficult to read in the YouTube player on a phone. Check the contrast against the image behind it, including any light or detailed areas. If the title crosses a logo or other important visual element, adjust the layout rather than expecting viewers to work around it.
Use real examples, not only short test strings. Include a long title, a title with punctuation, a title in the scripts your station uses, and a case with a missing artist or title. Look for clipping at both ends, awkward line breaks, and text that changes too quickly for a viewer to read. If you use scrolling text, check that the speed is readable and that it does not obscure the logo; if you use wrapping, make sure the second line remains inside the safe area.
Then observe the change in the Live Control Room preview. A local preview verifies the scene or output before YouTube; the Studio preview verifies what has reached the platform. Compare the displayed title with the track actually playing, especially at a transition. If the audio changes but the title does not, the problem is likely between the source metadata and the overlay rather than a YouTube Studio graphic control.
Finally, check what a viewer will encounter after a refresh or late arrival. The currently playing title should be visible without waiting for the next track change. A useful test log can be simple: note the track, the metadata received, the text displayed, and the time you observed it. This helps distinguish a delayed metadata update from a permanently disconnected text source without guessing.
Check audio, preview and stream status
Watch the Live Control Room while the encoder is running. Confirm that the preview contains both the fixed image and changing title, then listen for the radio audio. A picture can arrive without sound, and sound can arrive with an unintended blank or frozen image; checking only one side is not enough. Keep the preview open while you make a controlled track change so you can see whether the text follows it.
YouTube’s live health feedback can report issues such as missing audio or video, unsupported codecs, or keyframe intervals that are too long. Its Live Streaming API documentation describes stream health and ingestion details. Use the feedback shown for your actual stream rather than copying an example bitrate or encoder preset as a universal setting. If the signal reports a problem, change one relevant setting at a time and check the preview again.
Listen for clipping, long silence, abrupt cuts, and an audio level that is much lower than expected. Check the source feed directly as well as the YouTube preview; that separates a radio-source problem from an encoder or ingest problem. For a continuous station, make a monitoring plan that someone can follow when the stream is unattended: who checks the preview, how they identify a failed source, and how the encoder is restarted according to its own documented behaviour.
Decide whether you need an archive. YouTube says streams under 12 hours are automatically archived when stopped; verify the current guidance for your broadcast and channel before relying on an archive. Stopping the encoder ends an encoder stream, but the broadcast controls and archive settings are managed in YouTube Studio. If the stream is intended to continue indefinitely, consider the operational and content implications of how you stop, restart and archive it.
There is also a rights consideration separate from visual setup. YouTube scans live streams for matches to third-party content, and a licence does not necessarily prevent interruption if the rights owner has not allowlisted the channel. Read YouTube’s current copyright guidance for live streams and confirm permissions with the relevant rights holders. Do not infer that a static logo, metadata display, or a successful preview settles music rights.
Troubleshoot stale or missing track text
When text is stale, trace the data path in order. Check whether the audio source is reporting the new artist and title; then check whether the graphics workflow receives those values; finally confirm that its text layer is rendered into the outgoing video. This method narrows the fault without changing several parts of the setup at once. If the source itself has no metadata, no overlay can infer a reliable title simply from the audio.
If the overlay is blank, check its field names, formatting and fallback behaviour. Metadata systems do not all use identical labels, so a template that expects “artist” may not read a differently named field. Compare the exact values arriving at the graphics workflow with the fields the text layer is configured to display. Avoid showing raw field names or placeholder marks to viewers while diagnosing the problem on a public stream.
If the title updates locally but not in the Studio preview, check that the encoder is sending the scene or output that contains the dynamic layer. You may be previewing one scene while streaming another. If the Studio preview updates but the audio and title do not match, examine how your source signals track changes and whether the metadata event is delayed relative to playback. Do not treat a delayed label as proof that YouTube has changed the audio.
If text is clipped, fix the overlay dimensions or layout and test again at the final output size. Reducing the font may help, but it can make the title unreadable on mobile. Better options may include a shorter display format, more room in the composition, or a deliberate two-line design. If a track name contains unexpected characters, confirm that the chosen font can display them before assuming the metadata is corrupt.
A reliable fallback matters for an always-on station. If metadata stops arriving, keep the logo and a neutral station label on screen, and arrange for an operator or monitoring process to notice and investigate. Restart behaviour varies by encoder and configuration; use its documentation and test recovery rather than assuming a disconnect will be handled automatically. If you want a cloud-run stream based on an uploaded video, StreamNeo removes the need to keep your own computer on for that file-based broadcast, but it does not make a radio source’s metadata appear in an overlay.
Prepare the launch and operating routine
Before launch, write down the parts that are easy to forget: the correct stream key location, which encoder output is live, where the radio source comes from, and how to confirm the current track text. Keep this operational note private where it contains credentials. A second person should be able to identify whether the failure is audio, video, metadata, or the YouTube connection without needing to redesign the scene.
Do a final private or unlisted rehearsal if the channel workflow allows it. Check a track transition, test a long title, mute or interrupt the source briefly to see what the preview does, and confirm that recovery returns the correct scene. Restore the intended audio and visibility settings before the public broadcast. Testing is especially useful when changing computers, source software, fonts, or the metadata route.
For a station that runs unattended, decide what counts as an actionable fault. A title that stays unchanged while audio continues is different from a dropped stream; both are worth noticing, but they do not call for the same fix. Set a human check or monitoring routine that fits your schedule and capabilities. No encoder choice removes the need to verify the source, connection and actual output from time to time.
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 Studio add a changing now-playing label?
YouTube Studio is where you configure and manage the live broadcast, but the changing label described here is part of the encoder’s video composition. It needs a text layer connected to track metadata before the encoder sends the combined picture and audio to YouTube.
Can I use a static image if the stream is audio-only?
Yes. The image supplies the video portion while the radio feed supplies audio. Confirm in the encoder preview and Live Control Room that both are present; a radio audio source alone does not provide the visual signal described in this setup.
Why does the song title stay the same when the audio changes?
The source may not be supplying updated metadata, or the graphics workflow may not be reading the fields it receives. Check the source values, the text-layer mapping and the outgoing scene in that order, then compare the result with the Studio preview.
Do I need a hardware encoder for a logo and track text?
No. Software can compose an image and text layer, provided the chosen workflow can access the metadata you want to display. Hardware is an alternative when its graphics and metadata features match your requirements; verify those capabilities before buying.