You can create the YouTube live event in YouTube Studio, send the podcast feed through OBS, and place the episode schedule directly over the video. The moving schedule comes from an OBS Text or Browser source with the Scroll filter, not from YouTube chat.
The practical division of labour is simple: YouTube Studio manages the event and watch page, OBS combines the audio and visuals, and the preview confirms that viewers can read the schedule before you start broadcasting.
Schedule the live event in YouTube Studio
Start in YouTube Studio rather than OBS. YouTube Studio creates the live event, gives you a watch-page URL to share, and provides the Live Control Room where you can check the incoming preview before the public broadcast begins.
Open YouTube Studio, choose Create, then Go live. In the live area, open Manage and schedule a stream. Add a title, description, thumbnail, date and time, then select the privacy setting you need. The exact labels can change as YouTube updates Studio, so check the current YouTube encoder streaming instructions if a control is not where you expect it.
Scheduling is useful for a podcast because it separates promotion from transmission. You can send the watch-page URL to listeners, add the episode description, and prepare the artwork before OBS is sending anything. It also gives you a planned point at which to check the final preview instead of discovering layout problems after the stream has begun.
A scheduled event and the encoder feed are related, but they are not the same thing. The event is the YouTube destination. OBS is the programme that sends the audio and video feed to that destination. You must connect OBS to the correct stream URL and stream key for the scheduled event.
Treat the stream key as private. Do not paste it into a public document, show it in a screen recording, or send it in a group chat. If you think it has been exposed, use YouTube’s controls to replace or reset it before the next broadcast.
If this is the first time the channel has been enabled for live streaming, YouTube says activation may take time, including up to 24 hours in some cases. Check the current eligibility and live-streaming restrictions on YouTube before promising listeners a start time. If Studio reports that you have reached a daily live-streaming limit, the steps in YouTube says I have reached my daily live streaming limit may help you identify whether the issue is account-related or temporary.
For the event settings, choose the audience and visibility carefully. A public stream is discoverable, an unlisted stream is useful for a private rehearsal or a limited audience, and a private stream is for restricted access. Do not assume that changing visibility later will fix every scheduling problem. Decide what listeners should see before sharing the URL.
Prepare a readable episode schedule
Write the schedule before you design the overlay. A scrolling line is not a good place for a full episode description, a long list of guests, or several paragraphs of announcements. It should tell someone joining midway what is playing now and what is likely to come next.
A useful starting format is:
NOW: Episode 14 — Building a Home Studio | NEXT: Listener Questions | AFTER THAT: Field Notes
For a longer podcast block, include a few upcoming items and times only if those times are dependable:
NOW 20:00 — Episode 14 | 21:00 — Listener Questions | 21:30 — Episode 15 preview
These are editorial choices rather than YouTube or OBS requirements. The right amount of information depends on how quickly your programme changes and how much space the schedule occupies. If the text takes a long time to pass the screen, viewers may miss the item they wanted. If it moves too quickly, the schedule becomes decoration rather than information.
Keep episode names consistent. Decide whether you will use title case, sentence case, episode numbers, or guest names, then apply that choice to every item. Check spellings against the podcast artwork and show notes. A scrolling overlay is easy to overlook during preparation because each item is visible only briefly.
Use a separate copy of the schedule for the stream rather than editing the master show notes directly. That gives you a short version for the video and a fuller version for the description or pinned chat message. If the current segment changes during the day, edit the stream copy and preview it again before sending the feed.
A schedule can include a short instruction such as NEW EPISODE EVERY MONDAY or SEND QUESTIONS IN CHAT, but keep promotional text subordinate to the programme information. Viewers should be able to identify the current episode without waiting through several branded messages.
Check the schedule against the actual running order. A podcast that starts late, includes an extended introduction, or inserts a sponsor message can make fixed timestamps misleading. If the programme is not tightly timed, use labels such as NEXT and LATER rather than presenting estimates as guarantees.
You also need to decide whether the schedule should remain in the recorded replay. An OBS overlay is part of the video feed, so it will generally remain visible wherever that feed is watched. That is useful for people discovering the broadcast later, but it means a date-specific message may look old in the archive. YouTube says streams under 12 hours are automatically archived, so consider whether a long-running schedule still makes sense when viewers watch the recording afterwards.
The schedule is not a substitute for checking audio rights. If your podcast includes music, clips, guest material, or a repeated video loop, confirm that you have the necessary permissions for the YouTube broadcast and replay. For a broader discussion of the risk around repeated material, see Can YouTube terminate a channel for streaming copyrighted videos 24/7?. The schedule can explain what is playing, but it does not change the rights position.
Build the OBS scene with audio and visuals
Open OBS and create a scene for the podcast. Think of the scene as the complete picture that YouTube will receive, not just the place where the schedule will be added.
Add the audio source first. This might be a microphone, a mixer output, a USB audio interface, or another device already carrying the podcast audio. OBS documents microphone and other audio inputs in its Sources Guide. Choose the device that actually contains the programme sound, then speak or play a short test and watch the mixer move.
If the podcast is pre-recorded, add the source that plays the prepared episode. If it is live, make sure the microphone or mixer is not also being captured through another source, as duplicated audio can create an echo. Listen through headphones while testing rather than relying only on the mixer meter.
Add the visual material that should remain on screen. A camera source can show the host. An image source can display cover art. A video or browser source can provide a waveform, a branded background, or another visual element. OBS’s Sources Guide describes the main source types and how they are arranged in a scene.
Arrange the sources in the order you want them displayed. A background should sit below the artwork, camera, captions, and schedule. The schedule must be high enough in the source list to appear above any background, but it should not cover a face, a guest name, or permanent captions.
A simple podcast scene often works better than a crowded one. For example, place the cover art on one side, the camera or waveform in the centre, and a narrow schedule strip along the lower edge. Leave enough unused space around the moving text that it can enter and leave the frame without colliding with other labels.
Before styling the schedule, confirm the scene’s intended output size. A line that looks comfortable in the OBS preview can become difficult to read when watched on a smaller phone. Use a clear typeface, strong contrast, and enough padding around the letters. Avoid placing pale text over a detailed image.
If you are broadcasting from a home computer, remember that the machine must keep OBS, the audio devices, and the source media running for the duration of the show. A power-saving setting, a system restart, or an audio device that disconnects can interrupt the programme. The overnight lessons in How to keep a sleep sounds YouTube live stream running overnight are also relevant to a podcast that must continue while nobody is watching the controls.
Add a Text or Browser source for the schedule
For a straightforward schedule, add an OBS Text source. Create the source, type or paste the short schedule, and place it where the marquee should appear. OBS Text Sources can also use text supplied from a file, which is useful if you want to update the wording without rebuilding the scene.
A text file can be practical for a recurring podcast. Keep the file in a known location, edit it before the show, then reopen or refresh the source if necessary. Do not assume every edit will appear instantly in the preview. Check the rendered text after changing the file.
Use an OBS Browser source when the schedule needs more structure than plain text. A local HTML page or web page can provide styled blocks, colours, spacing, and other layout elements. This is helpful when you want an episode title, a current-status label, and upcoming items to have separate visual treatment. OBS describes how its Browser Source can load a local file or web page in the Browser Source guide.
The trade-off is maintenance. A Text source is usually easier to edit before a show. A Browser source can create a more controlled design, but it introduces another page or file to check. If it loads from the web, the page must remain available and should be tested in the same environment in which you will broadcast.
Start with one schedule source rather than separate moving sources for every episode. A single line is easier to align, scroll, pause, and replace. If you want a fixed NOW PLAYING label, keep that label static and scroll only the changing schedule content. This makes the current item easier to find.
Set the source width and height so that the schedule has a defined track. A very narrow source may clip long episode names before the Scroll filter can move them into view. A very large source may cover more of the programme than intended. Resize the source in the scene and inspect the edges before adding motion.
Do not use a pinned YouTube chat message as a replacement for this source. A pinned message is useful for a static schedule that viewers can open in chat, but it remains in the chat panel. It does not place text over the video and it does not create an on-video marquee. YouTube’s current live-chat guidance explains the pinning behaviour in its live chat help.
Only one chat message can be pinned at a time, and the creator controls the pin. You can therefore use the pinned message for a fuller list, links, or listener instructions while the OBS overlay carries the short, visible version. They serve different purposes rather than competing for the same space.
Apply OBS Scroll to create a marquee
Select the Text or Browser source in OBS, open its filters, and add the Scroll filter. The filter moves the source in a chosen direction, which is the mechanism that turns a schedule line into a marquee. The OBS Scroll Filter documentation covers the filter’s direction, speed, looping, and size controls.
Choose horizontal movement when the schedule is a single line along the top or bottom of the video. Choose vertical movement when you have a taller schedule panel and want items to rise through it. The source dimensions and the available blank space should decide the direction, not a fixed rule about what a podcast must use.
Set the speed slowly enough for a viewer to read an episode title in one pass. There is no universal ideal setting because reading time depends on font size, language, title length, screen size, and the number of words on the line. Watch the preview at the intended output size, not only in a large editor window.
Use looping when the schedule should continue throughout the broadcast. A repeating schedule can be useful for a long music or podcast block, but make the loop boundary clean. If the final item runs directly into the first item with no separator, viewers may not know where one cycle ends.
Add separators between items, such as a vertical bar, a dash, or a small neutral symbol. Keep the separator consistent and avoid using a character that is hard to distinguish from a letter at small sizes. A readable line such as NOW: Episode 14 | NEXT: Listener Questions | LATER: Episode 15 is easier to scan than a dense sentence.
The Scroll filter can limit the source’s width or height. Use those limits when you need the moving text to stay within a narrow strip rather than travelling across the whole scene. Check the source edges after applying the filter because a schedule that extends into a camera or logo can make the scene look unfinished.
Consider using a static panel if the schedule is very short. A fixed panel with the current episode and one upcoming item may be easier to read than a moving line. The scrolling version is most useful when the schedule contains more information than can fit in the chosen strip and needs to remain available without taking over the entire video.
Motion should not compete with speech. If the schedule passes over captions, a guest’s lower-third, or a waveform that viewers are meant to study, move it to a separate band or use a static panel instead. The purpose is to make the programme easier to follow, not to add movement for its own sake.
Preview the overlay before going live
Start with an internal rehearsal. In OBS, watch the complete scene while the audio source is active and the schedule is moving. Check the beginning, middle, and loop point of the schedule rather than looking only at the first few seconds.
Then start the encoder connection and wait for the preview in YouTube’s Live Control Room. A scheduled stream can be inspected there before you click the control that makes it live. This is where you confirm that YouTube is receiving the expected picture and sound, rather than relying only on what OBS shows locally.
Use a short checklist:
- Can you read the current episode without waiting through several loops?
- Does the schedule remain inside its intended strip?
- Does it avoid faces, cover art, captions, and lower-thirds?
- Is the audio coming from the intended microphone or programme source?
- Is there an echo, hum, clipped speech, or silence?
- Does the schedule update correctly if the text file or browser page changes?
- Does the loop restart cleanly?
- Is the event connected to the correct YouTube watch page and stream key?
Preview on a smaller display if possible. A schedule that is legible in the OBS canvas may be too small on a phone. Also check the contrast against the busiest part of the background. A dark translucent strip behind the text can improve consistency without requiring a larger typeface.
If you need to change the text, speed, or source position, make the change before the public start. Stop and reconnect the rehearsal if necessary, then wait for the updated YouTube preview. Do not treat the first public minutes as a design test.
After the broadcast, review the replay as well as the live preview. The replay shows whether the schedule remains useful when someone watches later and whether a date-specific message has become confusing. If the channel runs repeated broadcasts, keep a written pre-flight checklist so that the same checks happen before every episode.
If the main problem is leaving a home computer and OBS running for the whole broadcast, StreamNeo removes that particular operational task by letting you upload the prepared video, add your YouTube stream key, and let the channel run without your computer switched on. It is suited to a finished, pre-recorded programme rather than a live microphone workflow, so decide whether your podcast needs real-time participation before choosing the delivery method.
When you are ready to compare the operating options, use 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
Can I add a scrolling schedule with only YouTube Studio?
YouTube Studio schedules and manages the live event, but it does not create the moving text overlay described here. Use OBS or another encoder to combine the podcast audio, visuals, and schedule before the feed reaches YouTube.
Does a pinned chat message scroll over the video?
No. A pinned message stays in the live-chat area and can provide a static schedule for people who open chat. An OBS Text or Browser source with the Scroll filter is what places a moving schedule inside the video itself.
Should the schedule show every episode in the podcast feed?
Usually not. Use the current episode and a few upcoming segments that listeners can read while the line moves. Put the complete season or playlist in the description or pinned chat message, and keep the on-video schedule short enough to verify during the preview.
Can I use a Browser source instead of an OBS Text source?
Yes. A Text source is simpler for plain wording or a text file, while a Browser source is useful for a styled local page or web layout. Test the page, refresh behaviour, dimensions, and contrast before connecting the scheduled event.