To stream a prerecorded video to YouTube Live with OBS on Windows 11, add the local file as a Media Source, connect OBS to the stream URL and key from YouTube Live Control Room, then start the encoder and check YouTube’s preview before relying on the public stream.
The basic encoder steps are the same in India as elsewhere in the reviewed documentation; there is no separate India-specific OBS configuration established here. Your own channel must be eligible and have live streaming enabled, and your actual upload capacity will determine a sensible stream setting.
Check live access before event day
Open YouTube Studio and select Go Live. If this is the first time the channel will stream, follow YouTube’s activation prompts and check the account’s status there. YouTube says a channel must be verified and must not have live-streaming restrictions in the past 90 days; first-time activation can take up to 24 hours. These are YouTube’s stated requirements, not a conclusion about any particular channel’s eligibility. Check the current YouTube live-streaming eligibility guidance for your account.
Do this well before a scheduled broadcast. An OBS scene can be configured correctly while the YouTube account still cannot go live, so testing the encoder alone does not establish eligibility. Create or schedule the live event in Live Control Room once access is available, and decide whether the test should be private or unlisted. Confirm visibility and access from the event settings rather than assuming a successful OBS connection means the public can watch.
A prerecorded programme also needs to be suitable for the channel and stream. If it contains music or other material you do not control, review the rights and YouTube’s current rules before broadcasting; a local file playing successfully does not resolve rights questions. For a music-focused channel, the practical considerations in this guide to copyrighted songs in an Indian music stream are separate from the technical setup.
Create a simple OBS scene on Windows 11
Install and open OBS Studio on the Windows 11 computer you plan to use. A scene is the layout OBS sends to the encoder; sources are the items that appear in that layout, such as a video file, camera, image or audio input. For a single prerecorded programme, one scene with one Media Source is enough to begin. OBS explains the Scenes and Sources workflow in its documentation.
In the Scenes dock, create a scene and give it a name that will still make sense later, such as “Main video”. In the Sources dock, use the + button to add the file in the next step. If you use multiple scenes for an opening slate or programme, name them clearly and test each transition; a scene change can alter what viewers see even if the stream itself remains connected.
Before connecting to YouTube, check that the preview shows the intended picture at the expected size and that sound is present. A black preview can mean the source is missing, hidden, positioned outside the canvas or still loading. If the video is wider or taller than the OBS canvas, use the source’s transform options to fit it, then watch the preview for cropping. Avoid adding extra sources until the basic file plays correctly.
Add the prerecorded file as a Media Source
With the scene selected, choose Sources → + → Media Source. Create a new source, name it, and browse to the local video file. OBS’s Media Source supports common local video formats including MP4, MOV, MKV, AVI and WebM. The exact result can still depend on the file’s encoding, so treat a successful selection as the start of testing rather than proof that every part of the file will play as intended.
The source properties include controls for the file and playback. Select the correct file path and check the preview. If you move or rename the source file after configuration, OBS may no longer find it, so keep the file in a stable folder for the duration of the broadcast. Do not use a removable drive that might be disconnected or a location that Windows can make unavailable while the stream is running.
Check the beginning, middle and end of the programme before going live. Look for blank frames, unexpected aspect-ratio changes, clipped sound or a long silent section. If the source’s sound is too quiet or too loud relative to your intended mix, adjust the audio in a test and listen on another device. A moving picture in OBS does not by itself confirm that YouTube is receiving the audio correctly.
If your plan is to turn several existing uploads into a continuous channel, that is a different workflow from sending one local file through OBS. This explanation of using existing YouTube uploads in a 24/7 channel can help clarify when a file-based encoder setup is or is not the right fit.
Choose whether the file should repeat
In the Media Source properties, turn on Loop if you want the same video to restart when it reaches the end. Loop is off by default. With it disabled, playback ends when the file finishes; the YouTube encoder connection may still be active, but that does not make the media restart. Decide whether the stream should stop at the end, hold on an ending frame, or repeat, and test the actual behaviour in OBS.
A loop is useful for a long ambience scene or a continuous information loop, but repetition can be noticeable. Check the final seconds and opening seconds together for a visible jump in image or sound. A song that fades out and then cuts to a loud opening, for example, can make the seam obvious even though the source repeats correctly. If a seamless loop matters, prepare or edit the source accordingly and verify it in playback.
For a sequence of separate files rather than one repeated file, OBS also has a VLC Video source that can work with playlists, but it requires VLC to be installed. That adds another application dependency, so a single Media Source is simpler where one video is all you need. For alternative looping approaches, see the FFmpeg looping guide; it covers a different toolchain and is not required for this OBS workflow.
Connect OBS to YouTube Live Control Room
In YouTube Live Control Room, create or select the event and locate its encoder settings. Copy the stream URL and stream key shown for that event. In OBS, open Settings → Stream and select YouTube if it is available, or choose the option to use a custom server and enter the supplied URL and key. The labels can vary with OBS versions, so use the values from the current Live Control Room rather than a URL copied from an old tutorial.
Treat the stream key like a password. Do not include it in screenshots, overlays, shared documents or a public support request. If you think it has been exposed, reset it in YouTube and update OBS with the replacement before streaming. The YouTube encoder setup instructions describe the connection flow and where to obtain the encoder details.
Prefer RTMPS when the available encoder path supports it. YouTube describes RTMPS as RTMP carried over TLS/SSL and recommends it where supported. For a conventional SDR video stream over RTMP or RTMPS, its guidance lists H.264 video, constant bitrate (CBR), frame rates up to 60 fps, and a recommended two-second keyframe interval; do not exceed four seconds. Consult the current YouTube encoder settings table for resolution-specific bitrate recommendations rather than selecting a setting from memory.
| Choice | What it means for this workflow | Trade-off |
|---|---|---|
| RTMPS with a standard SDR profile | The conventional path for a local video sent from OBS; use the current YouTube settings guidance for codec and bitrate. | Usually the simpler fit for a normal prerecorded video, but still needs testing against your connection and file. |
| HLS | A separate delivery route that can suit particular HDR or codec requirements when the encoder supports it. | More setup detail and higher latency than RTMP; unnecessary complexity for an ordinary SDR file unless you have a specific requirement. |
For most readers following this guide, do not switch to HLS simply because it sounds more advanced. The stream’s resolution, frame rate and bitrate should suit both the source and the upload connection. A 1080p file does not automatically mean that a 1080p broadcast is the sensible choice if the PC or available connection struggles with it. YouTube’s table is the place to check the supported range, while a real test shows how the chosen settings behave at your location.
Start the encoder and inspect YouTube’s preview
When the scene, source and stream settings are ready, select Start Streaming in OBS. Wait for YouTube Live Control Room to report that it is receiving the encoder feed, then inspect its preview before treating the public event as ready. Look for the intended image, moving playback and audio. Read the stream-health messages rather than relying only on a green-looking OBS status or the fact that the button has changed state.
YouTube recommends setting up an encoder in advance and starting it at least 15 minutes before a scheduled event. That time is useful for finding problems while you can still change settings or postpone the public start. If YouTube reports an unstable connection, dropped frames or no incoming video, make one change at a time: check the selected stream key and URL, verify the source is playing, and compare the encoder bitrate with the upload capacity available at that location.
YouTube’s streaming tips recommend leaving upload bandwidth above the total stream bitrate, with 20% headroom as a recommendation. The practical point is that other household or workplace traffic also uses the connection; a connection that barely matches the encoder setting may not be enough. YouTube states, “The total bitrate you’re streaming cannot exceed the amount of upload bandwidth available.” If Wi-Fi is inconsistent, an optional Ethernet connection to a compatible router may help remove wireless variability, but neither YouTube nor this guide requires a particular cable or connection type.
Keep the Live Control Room visible during the broadcast when possible. Check the health indicators and listen to the stream from a separate device or browser session. That helps distinguish a clean OBS preview from a problem in the delivered stream, such as missing audio or an image that has stalled. No test can promise uninterrupted streaming; monitoring gives you a chance to notice a fault and respond.
Test playback before relying on a public stream
Run a test with the same file, scene, output settings and network that you plan to use for the real broadcast. A private or unlisted event can reduce unintended audience exposure, but confirm the event’s visibility and test access from the account or device you will use to inspect it. Check YouTube’s incoming preview first, then check the event playback as a viewer. Those are distinct checks: the encoder preview shows what YouTube is receiving, while viewer playback confirms the event is being delivered as expected.
Let the source run long enough to test the parts that can fail: the opening, a representative section, and the end or loop point. Listen for audio drift, gaps or abrupt changes. If the file is intended to repeat, wait for it to reach the seam; if the test ends before the file does, you have not verified loop behaviour. Confirm the right scene remains selected and that no notification, desktop window or unrelated source appears in the output.
YouTube recommends preparing the encoder well in advance, starting it at least 15 minutes before the scheduled event, previewing the result and monitoring audio and video quality. Use the test to leave time for a correction, not as a promise that later network conditions will be identical. If the stream is unstable, lower the output demands in line with the YouTube bitrate guidance and test again; a lower resolution that plays reliably is more useful than a higher setting that repeatedly fails.
If this is meant to run continuously rather than for a single scheduled broadcast, consider the computer and operator requirements as well as the initial setup. OBS on your Windows PC depends on that PC, its power, its network and the playback source staying available. A guide to reducing CPU load on a long-running lofi stream covers a related practical concern, though it does not replace checking the particular machine and stream.
For creators who need the uploaded file to continue broadcasting while their own computer is switched off, StreamNeo addresses that specific burden by turning an uploaded video into a YouTube live stream without keeping this OBS computer running. That is a different operating choice from the local-file OBS process explained above, so decide based on whether you want to operate the PC and encoder yourself.
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 from OBS on Windows 11?
Yes. Add the local video as an OBS Media Source, connect OBS to the stream URL and key provided by YouTube Live Control Room, and start the encoder. Check that your channel can go live and verify YouTube’s incoming preview and stream health before relying on the event.
How do I loop a video in OBS?
Open the Media Source properties and enable Loop. It is off by default, so playback otherwise ends when the file finishes. Test the join between the end and beginning because a loop can repeat technically while still having an audible or visible jump.
Is there a separate OBS setup for India?
The reviewed official instructions do not establish a separate India-specific OBS configuration. Check live-streaming access in your own YouTube Studio account, then choose settings based on the file, computer and upload capacity at the place where you will stream.
What should I do if YouTube shows no preview or poor stream health?
First confirm that the Media Source is playing in OBS and that the correct stream URL and key are in use. Then check YouTube’s health messages, the selected encoder settings and the available upload capacity; make one adjustment at a time and test again.