To stream a podcast archive to YouTube Live with OBS, use Media Source for one local file and VLC Video for a playlist of files. Build and test the scene, connect OBS with the stream URL and key from YouTube Studio, and check the incoming preview before making the event public.
A YouTube replay is not a substitute for your own copy: YouTube says streams longer than 12 hours may not be captured. If you need the complete event, make a local recording and check that it is being saved.
Choose one file or an archive sequence
Start with the shape of the archive, not with the source menu. If you have one finished episode or a single compiled programme, a Media Source is usually the direct choice. If the archive is split into several files that should play in order, VLC Video gives OBS playlist controls.
A single file may be an audio file with a static cover image, or a video file with its own visuals. Decide whether the source should play once, loop, or restart when the scene becomes active. A podcast intended as a continuous station may need looping; a scheduled episode premiere may need to play once and then transition to a holding scene. Those are different broadcast behaviours, so choose deliberately rather than assuming that the source will continue after it ends.
For a sequence, write down the intended order and check filenames before adding them. A playlist containing an introduction, several episodes and a closing card will not necessarily behave as an editorial programme just because its items are present. Confirm whether you want the list to loop or shuffle, and whether changing scenes should hide playback or leave it running.
Also decide what viewers should see while listening. A podcast video can use episode art, a title card, captions or other useful context, but extra elements are not required simply because OBS permits them. For a station serving listeners on phones or slower connections, a simple static visual may be more dependable than layering several animated elements over the archive.
Before using any archive in a public live stream, confirm that you have the necessary rights for the podcast itself and for music, guest contributions, clips or other incorporated material. YouTube's livestream terms and conditions put responsibility for the required rights on the content provider. This is a practical check, not individual legal advice.
If you are deciding between a live replay and an uploaded programme, the distinction is worth considering: this guide on YouTube radio livestreams versus uploaded radio mixes explains how the format affects how people encounter a station. A live event suits the feeling of a scheduled broadcast; an upload can be easier to revisit as a discrete episode.
Add Media Source or VLC Video
In OBS, add a source to the scene using the Sources panel. For one file, choose Media Source, give it a recognisable name such as “Episode archive”, and browse to the local audio or video file. OBS documents common formats including MP4, MOV, MKV, WebM, MP3, AAC, OGG and WAV in its Media Sources guide. If your file is not opening, verify its format and test playback outside OBS before changing several source settings at once.
The Media Source options affect the lifecycle of the file. Loop repeats it when playback ends. Restart playback when source becomes active starts it from the beginning when the source becomes active. Show nothing when playback ends controls what is shown after completion, while Close file when inactive affects whether the file remains open while that source is not active. The appropriate combination depends on whether this is a one-time episode, a recurring loop, or part of a scene you may switch away from.
For example, if a two-hour archive should play once and then leave a “Thanks for listening” card visible, test the end behaviour in advance. Do not rely on the file’s final frame as a deliberate holding image: it may be blank, irrelevant, or simply not what you want viewers to see. If a source is intended to loop through the night, test the transition from its last moment back to its beginning.
For multiple files, add VLC Video and configure its playlist. This source depends on VLC being installed; OBS notes that 64-bit OBS requires 64-bit VLC. If VLC Video is missing or does not work, check the installation and architecture rather than treating it as an OBS-only feature. The OBS Media Sources documentation covers VLC Video settings as well as the single-file source.
Add the files in the desired sequence, then check loop or shuffle behaviour and what should happen when the source is hidden or playback ends. Shuffle is unsuitable if episode order matters. A playlist is convenient for an archive of separate programmes, but it adds another dependency and more behaviour to verify than a single file. If you only have one compiled programme, using VLC Video brings no meaningful playlist benefit.
Build the scene and check audio
After adding the archive source, compose the scene in the OBS preview. Sources higher in the list appear above sources below them, so a title graphic may cover the video if its order is wrong. Resize or position a source only after you can see that it is playing. Keep the scene legible and avoid placing important text too close to the edges where it may be obscured in a player interface.
For an audio-only podcast, a still image, show name and episode title are often enough. If you include a waveform or other visual element, treat it as decoration and check that it does not obscure captions or episode artwork. A local news or devotional archive may have different needs from an interview podcast; include information that helps the audience follow the content, not elements added merely to fill the screen.
Play the source in OBS and watch the Audio Mixer meters while listening through headphones or speakers. The meter should respond to the archive’s sound. If it does not, check that the source is unmuted and that you have selected the correct file. If the level appears unexpectedly low or distorted, inspect the source and mixer controls and test again. Avoid making a late adjustment based only on the meter; listen to a sample as well.
Check the beginning, a point in the middle, and the end of the file. For a playlist, sample the transition between items and verify that the next file starts as expected. An abrupt gap or a different loudness between episodes may be part of the archive, but it should not surprise you while viewers are listening. OBS's Quick Start Guide recommends a test stream and checking audio meters before a first broadcast.
If you will change scenes during the event, test whether the archive continues or restarts when you return. That outcome depends on source settings and how the source is activated. A scene change can be useful for a break or announcement, but it can also accidentally restart an episode or leave the audience with no programme audio.
A clean scene and clear audio matter more than elaborate overlays. If the intended stream is a long-running station rather than a one-off event, compare the workflow with streaming multiple video formats in one YouTube Live loop. That example is relevant when an archive includes varied media formats, though the same basic test remains necessary for every file.
Connect OBS using the stream URL and key
In YouTube Studio, open the Live Control Room and create or select an encoder stream. Set the event details, including title, visibility and schedule, before connecting. YouTube's instructions for creating a live stream with an encoder describe the setup flow. Check the current guidance in your account because live-stream availability and account status can vary.
Copy the stream URL and stream key shown for that stream into OBS's stream settings. These are the connection details that let OBS send its output to the correct YouTube event. Treat the key like a password: do not include it in a screenshot, paste it into a public chat, or store it somewhere other people can access. If you believe it has been exposed, reset it in YouTube Studio and update OBS with the replacement.
YouTube currently recommends RTMPS for encoder delivery in its live-stream guidance. Use the connection option supported by the current YouTube and OBS settings, and consult YouTube's streaming tips and encoder settings guidance for quality choices. There is no single resolution or bitrate to prescribe without knowing the archive properties and the upload connection available at the stream location.
After entering the details, verify which YouTube stream the key belongs to. A correct key paired with the wrong event can send the feed somewhere other than intended. Confirm the event title and visibility in Live Control Room before starting the encoder, especially if the archive includes material not ready for a public audience.
If you are streaming from a personal computer, remember that OBS must remain open and the computer must stay powered and connected for the broadcast to continue. A power interruption, operating-system update or lost connection can interrupt the feed. For creators whose specific concern is keeping a long broadcast going while their own computer is off, StreamNeo removes that particular burden by letting you upload a file and connect the YouTube channel for a cloud-run stream; it does not change the need to check the content, rights and YouTube preview.
Check the incoming preview before going public
Start streaming from OBS, then wait for the signal to appear in YouTube Studio's Live Control Room. Do not assume that OBS showing activity means YouTube is receiving a usable picture and sound. Inspect the incoming preview and stream health, and listen to the YouTube-side preview if available before using the Go live control required by the selected setup.
Check the visual framing, title card, motion and audio. Make sure the opening begins where you intended and that the source is not blank, muted or showing an unintended desktop. If there is a delay before the feed appears, allow the control room to update rather than repeatedly changing settings without evidence of a fault.
A useful check is to have another person view the preview or monitor it from a separate device, particularly if your OBS screen and playback audio share the same computer. That can reveal a muted feed or an image that looks different from the canvas. Do a short private or unlisted test when appropriate, but verify the visibility and event settings before changing to public.
YouTube recommends testing the stream and checking its health rather than choosing settings blindly. If the preview reports a problem, check the source playback, OBS output, selected event, connection and current encoder settings one at a time. The aim is to identify the actual break in the chain, not to raise quality settings at random.
The process is similar to a soundcheck before a live programme: the archive is the content, OBS is the encoder, and the preview is the last chance to catch a wrong scene or connection before viewers arrive. For a more continuous channel, the guide to an always-on sleep music stream offers related planning considerations, while this article focuses on the OBS media-source workflow.
Keep a local archive backup
If the broadcast itself must be retained, make a local recording as well as sending the stream to YouTube. YouTube Help recommends a local archive backup. A local recording gives you a copy to review or preserve even if the platform archive is unavailable, but it still depends on your own recording destination and storage being available.
Before starting, choose a recording location with room for the expected file and confirm OBS is configured to record. During the stream, check that the recording indicator is active and that the file is growing. After the event, stop the recording cleanly and verify that the saved file opens and includes the material you expected. A recording that never started is not a backup.
Storage needs depend on the recording format, quality, duration and the amount of free space already available, so do not guess from a generic capacity figure. If the computer’s internal storage is tight, an external drive can be an optional destination, provided it has suitable space and remains connected. For planning, this guide to calculating storage for a week of YouTube stream videos helps frame the factors that change the required capacity.
Keep the original podcast files separately from the live recording where practical. The original archive is your source material; the OBS recording is a copy of what the programme captured. If there is a failure in playback, a scene transition or the stream itself, having both can make it easier to identify whether the problem came from the source file or from the broadcast workflow.
If you do not need a local capture of the entire live output, you may not need to enable one, but be clear about what you are giving up. YouTube’s archive and a local recording have different failure conditions. A local backup is especially useful when an event runs for a long time or the recording is part of your own publishing workflow.
Understand replay capture limits
YouTube can automatically archive live streams that are shorter than 12 hours, but its Help page warns that a stream exceeding 12 hours may not be captured at all. That is not a promise that every shorter stream will become a replay, and it is not a safe basis for assuming a very long broadcast will be available afterwards. Check YouTube's current archive live streams guidance before relying on a platform archive.
If you need a complete recording, do not plan a stream that crosses the 12-hour threshold and then depend on YouTube to preserve it. Record locally and verify the file. This is particularly important for a 24/7 podcast or radio-style channel, where a continuous event may run far beyond the duration YouTube says it can capture. You can also break programming into appropriately managed events, but event design does not remove the need for your own backup if the material matters.
The distinction is between a live feed and a saved replay. A viewer may have watched the event live even when no replay is available afterwards. If a replay is central to your audience, choose an event length and recording plan with that limit in mind, then confirm the resulting archive after the broadcast rather than treating the live preview as proof of a saved copy.
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
Should I use Media Source or VLC Video for one podcast episode?
Use Media Source for one local audio or video file. VLC Video is useful when you need a playlist of multiple files, but it adds a VLC installation requirement and playlist behaviour to check.
Does VLC Video work without VLC installed?
No. VLC must be installed for the VLC Video source to be available, and OBS notes that 64-bit OBS requires 64-bit VLC. If you only need to play one file, Media Source avoids that dependency.
Will YouTube always save a long live stream as a replay?
No. YouTube says a stream exceeding 12 hours may not be captured at all, so do not rely on a platform replay for a longer event. Keep and verify a local recording if you need the full programme.
What should I check before making the stream public?
Confirm that the intended archive is playing, the mixer shows audio, the stream key belongs to the correct event, and YouTube's incoming preview looks and sounds right. Check the event visibility and the rights for music, guests and other material before going live.