To stream a prerecorded video to YouTube Live with OBS, add the local file as a Media Source, create a live event in YouTube Studio and connect OBS using the event’s stream key. On a budget PC, treat 720p at 30 fps as a cautious test setting, not a promise: your computer, the file and your upload connection all need to manage it reliably.
The dependable approach is to test the complete setup from the place where it will run, using the actual video and sound. If OBS reports encoding or rendering lag, or YouTube reports an unstable stream, lower the output settings before you schedule a longer broadcast.
Check the PC and connection you will actually use
A prerecorded file removes the need to capture a camera or desktop, but OBS still has to play the file and send a live signal to YouTube. Depending on your selected output, the PC may also have to encode that signal in real time. A modest computer may handle one file comfortably at a lower output setting and struggle at a higher one. There is no single processor, memory or graphics specification that guarantees success for every file and OBS setup.
Start by checking the practical basics. Make sure the source file plays normally on the PC, note where it is stored, and close applications you do not need during the broadcast. Leave the machine plugged in, prevent sleep from interrupting the session, and ensure the video file will remain available at the same path. These steps do not make a slow PC faster, but they remove avoidable interruptions.
Next, test upload from the location and at the time you expect to stream. An ISP plan’s download figure does not tell you how much stable upload capacity is available. YouTube notes that the stream’s total bitrate must fit the upload bandwidth, that other users and devices can affect the available capacity, and that a wired connection can be preferable where practical. Its streaming tips advise leaving bandwidth headroom; a speed test is a useful starting point, not a guarantee of conditions through the night. See YouTube’s streaming tips and test while the household or shop network is in realistic use.
If the PC is currently on Wi-Fi and can be placed near the router, compare a wired test with the wireless one. Ethernet may reduce variability caused by a weak or busy wireless link, but it cannot increase the upload capacity your internet connection provides. If the connection is shared, ask other users to avoid large uploads during the test and eventual broadcast where that is practical.
For a longer explanation of the settings that affect a music channel, the encoder settings guide for 24/7 Indian music streaming is useful background. It is not a substitute for testing your own PC and connection: a setting that works on another channel may not suit your file, home network or hardware.
Enable live streaming and create the event
Before opening OBS, confirm that the YouTube channel is eligible to go live. YouTube requires a verified channel and says it must not have live-streaming restrictions during the preceding 90 days. If live streaming has not been enabled on the channel, allow time for YouTube’s activation process rather than leaving it until the scheduled start. Check the current requirements in YouTube’s live-streaming getting-started guidance.
In YouTube Studio, open the Live Control Room and create or schedule the event. Choose the visibility you need. An unlisted test can let you inspect the stream without presenting it as a public broadcast, though you should still check who can access the link. Set the title, description, audience details and start time carefully; scheduling the event does not itself make OBS start sending video.
For an encoder workflow, the Live Control Room provides the stream details OBS needs. The stream key is a credential, not a public label. Keep it out of screenshots, shared documents and the video itself. If you think it has been exposed, replace or reset it through YouTube Studio before relying on it again. You can read the key-handling details in YouTube’s encoder setup instructions.
Make the test event early enough to leave time for changes. If you have only a few minutes before a public start, you may discover that the file has no sound, the stream key is wrong or the PC cannot sustain the chosen output. A separate unlisted test makes it easier to check those things without confusing viewers who expect the real programme.
Add the local file as an OBS Media Source
Open OBS and create a scene for the broadcast. Add a Media Source to that scene, give it a recognisable name, and choose the local video file. The source’s name is only for your organisation in OBS; it does not change the file or the YouTube title. Check that the image appears in the preview and that the audio meter responds when playback begins.
OBS Media Source supports a range of video formats, including MP4, MOV, MKV and WebM. That does not mean every file will decode smoothly on every PC: resolution, encoding and the available hardware all matter. If a file fails to open, shows a black preview or plays unevenly, first confirm it plays locally in a normal media player. Then check the OBS log or test a compatible copy rather than assuming the stream settings are the only problem.
In the Media Source properties, decide whether playback should start again when the source becomes active. That can be useful if you switch away from and then back to the scene. Hardware decoding may also be available, but it depends on what the computer’s graphics hardware supports. Try it only as a test; if playback becomes less reliable, turn it off and compare results.
For a single video, Media Source is the straightforward choice. OBS also has a VLC Video source that can play multiple files as a playlist, but VLC needs to be installed on the PC. If your programme consists of an ordered group of clips, that distinction matters. For one long recording, a playlist feature is unnecessary. The guide to making a Hindi lofi stream from MP4 files covers a related use case, but check the behaviour of your own file in OBS.
Before changing output settings, watch the source in the preview for long enough to see a representative part of the video. Check for black bars, an unexpected crop, muted sound or a mismatch between picture and audio. A static opening frame can hide problems that appear only when the video changes scene or uses faster motion.
Choose whether the video should repeat
A Media Source can play once or loop. Enable Loop only when the programme is meant to restart at the end. If the broadcast should stop after one showing, leave looping off. For an always-on devotional channel, a repeated bhajan programme may be the intention; for a scheduled talk or news presentation, an unexpected restart could confuse viewers.
Do not assume that a loop creates a seamless transition. Play through the end of the file during a test and observe what happens at the restart. A visible pause, abrupt change in sound or return to an opening slate may be acceptable for your programme, or it may call for a better-edited source. OBS repeats the file; it does not edit out silence or join the final frame to the first one.
If you need to rotate several videos rather than repeat one, decide the order and test the transitions before going live. A playlist source may be more convenient for multiple files, but it adds another dependency in the form of VLC. A single file in Media Source is easier to diagnose when you are learning the workflow. The article on rotating videos on an always-on YouTube channel explores the scheduling problem separately.
Also check that the material is yours to stream or that you have the necessary rights. A file being stored on your PC does not establish permission to rebroadcast its music, footage or other content. YouTube’s monetisation rules also distinguish original work from reused material; broadcasting a recording as a live stream does not, by itself, make it original or eligible for monetisation. Review the current YouTube channel monetisation policies and make your own rights checks before publishing.
Set a conservative output for a real test
For an ordinary SDR stream, a sensible first test on an unknown budget PC is 1280 × 720 output at 30 frames per second, using H.264, CBR and a two-second keyframe interval. This is a starting point to evaluate, not a minimum hardware specification or a guarantee that your computer can encode the video without lag. If OBS offers a hardware encoder, you can test it, but availability and results depend on the PC.
YouTube’s current encoder guidance lists 3 Mbps as the minimum and 8 Mbps as the recommended H.264 video bitrate for 720p30. Those are YouTube ingest figures, not a promise of smooth encoding on your machine or sufficient capacity on your particular connection. Choose a test bitrate that fits measured, stable upload bandwidth and leaves room for normal variation and other network use. YouTube recommends a two-second keyframe interval and advises not exceeding four seconds. For audio, its guidance recommends AAC stereo at 128 kbps. Consult the official encoder settings and bitrate table when setting up the event.
In OBS, open Settings, then Output. If you need to choose the encoder and rate-control details, use Advanced output mode. Select H.264 where available, set rate control to CBR, enter the test bitrate, and set the keyframe interval to two seconds. Set audio to AAC if that is offered for the selected streaming path. Under Video, choose the output resolution and frame rate for the test. For ordinary SDR, Rec. 709 is a common colour-space choice; avoid changing colour settings without a reason, since mismatched settings can make the preview look different from the source.
The comparison below shows why it is better to establish a stable baseline than to pick a larger number because it sounds better. YouTube’s bitrates are encoder guidance; they do not determine whether an unknown PC can sustain a particular output.
| Test output | YouTube H.264 video bitrate guidance | Practical consideration |
|---|---|---|
| 720p at 30 fps | 3 Mbps minimum; 8 Mbps recommended | A reasonable first test for a modest setup, but still needs real testing |
| 1080p at 30 fps | 5 Mbps minimum; 14 Mbps recommended | More detail, with a higher bitrate requirement and potentially greater PC load |
Do not jump to 1080p just because the source file is 1080p. You can output at a lower resolution and test whether the picture is clear enough for the programme. If OBS shows encoding lag, lower the output resolution or frame rate, or test another available encoder. If YouTube reports connection problems while OBS itself is keeping up, examine the upload path and bitrate instead of assuming the PC is at fault. Change one setting at a time so that the effect is understandable.
Connect OBS to YouTube Live
In OBS, open Settings and select Stream. Choose YouTube from the service list if the available OBS version offers it, then connect through the sign-in flow or enter the stream key according to the option shown. If using a custom server workflow, enter the server URL and private key supplied by YouTube Studio. Keep the key private, and check that you have copied the key for the event you intend to test rather than another scheduled stream.
Apply the settings and return to the main OBS window. Confirm the correct scene is selected and the Media Source is visible. When you are ready, select Start Streaming in OBS. This begins sending the signal to YouTube; it does not necessarily mean the event has been made public or that viewers have been told it is live. Follow the Live Control Room prompts to verify the preview and start the event at the appropriate time.
If OBS cannot connect, check the basics in order: the selected YouTube service or server URL, the stream key, the internet connection, and whether the event is ready in Studio. Avoid posting the key in a support forum or sending it in a public screenshot. If you need help, describe the error message without exposing credentials.
Keep OBS open for the broadcast and do not let the PC sleep or restart for updates. A local prerecorded file still depends on the computer, the OBS process and its connection remaining available. If the PC is also used for other work, avoid heavy tasks during the stream until you have tested their effect. A workflow based on OBS is useful when you want direct control on a PC, but it does mean that PC remains part of the broadcast.
Preview, check stream health and adjust
Run an unlisted test with the actual file, scene, audio and network you plan to use. Let it run long enough to see a range of movement and hear the programme clearly. In YouTube Studio’s Live Control Room, check the incoming preview and stream-health messages. On the viewing side, confirm that the audio is present, picture is not frozen, and the event can be accessed as intended.
OBS’s Stats window helps separate common problems. Rendering lag suggests OBS is not drawing frames in time; encoding lag suggests the selected encoder cannot keep up; dropped frames related to the network point towards the connection or sending bitrate. These indicators are clues, not a diagnosis by themselves. Compare them with YouTube’s health messages and note when the issue occurs.
If the PC struggles, reduce the output resolution or frame rate and run another test. If the network is the problem, compare the chosen bitrate with stable upload capacity, reduce it if necessary, and test over Ethernet where possible. If the preview is fine but the file has no audio, inspect the Media Source and audio routing before changing video settings. Make one change, repeat the relevant part of the test and keep a short note of what improved.
Test at the actual location, not only at a time when nobody else is using the connection. YouTube recommends a wired connection where practical and advises allowing upload headroom. If your connection varies, a bitrate comfortably below the best speed-test result is more prudent than matching the test result exactly. A speed test cannot reproduce every interruption, evening slowdown or competing device that might occur during a long broadcast.
Before the scheduled event, verify the title and visibility, confirm the correct OBS scene and source, and check the YouTube preview again. During the live session, monitor both the OBS statistics and Studio’s stream health. At the end, stop the broadcast in YouTube’s control room and then stop streaming in OBS, checking that the event has actually ended.
If the test shows that a home PC or connection is not dependable for a long unattended run, do not assume a settings tweak will solve every interruption. Reconsider the operating arrangement, reduce the broadcast demands, or schedule a shorter test window. The comparison of a PC and cloud options for a 24/7 YouTube stream can help frame that decision without replacing your own test.
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 stream a prerecorded video to YouTube Live with OBS?
Yes. Add the video as an OBS Media Source, set whether it should loop, and send the OBS stream to a YouTube Live event using its stream key. You still need to check channel eligibility, the file’s playback and the stream preview before a public start.
Will 720p at 30 fps work on every budget PC?
No. It is a cautious configuration to test, not a guarantee for any particular computer. Check OBS for rendering or encoding lag while playing your actual file, and reduce resolution or frame rate if the test is unstable.
Is my download speed enough to choose a stream bitrate?
No. Streaming depends on available upload capacity, and that can vary with the location, time and other users on the network. Test upload under realistic conditions and leave headroom rather than setting the stream bitrate equal to a speed-test result.
Does looping a video make it eligible for monetisation?
No. Looping is only a playback choice in OBS; it does not grant rights to the material or determine monetisation eligibility. Check YouTube’s current copyright and monetisation policies, and use content you have permission to stream.