To stream a pre-recorded video to YouTube Live in 1080p with OBS, add the local file to a scene as a Media Source, set the output to match the source and your upload capacity, then send it to a YouTube Live event. Before you make the event public, check the incoming preview, picture, sound and stream health.
The settings below are a starting point, not a promise that every file or computer will deliver a stable 1080p picture. Source quality, frame rate, encoder choice and available upload all matter. You do not need a camera for this workflow, but you do need a file you have the necessary rights to broadcast.
Create or select a YouTube Live event
First check that live streaming is enabled for your channel. YouTube says a first-time activation can take up to 24 hours, so do not leave this check until the day you plan to broadcast. You can find the current requirements and setup steps in YouTube’s encoder setup guide.
In YouTube Studio, create or schedule a live stream using the encoder workflow. Select the privacy setting that suits your purpose. For a test, an unlisted event can let you check the actual feed without making it discoverable to the public. Confirm that you are working on the intended event before copying its stream details.
The event provides a stream URL and a stream key. OBS uses these to send its output to the right YouTube event. Treat the key like a password: anyone who obtains it may be able to send a feed to your event. Do not include it in a screenshot, recording, public document or message. If it is exposed, replace it in YouTube Studio before broadcasting.
If this is your first event, take time to inspect the event settings as well as the encoder details. Check the title, privacy, audience and scheduled time before you start. A correctly configured OBS scene cannot fix an event that is public too early, attached to the wrong channel or scheduled for a different time.
Add the local file as an OBS Media Source
Open OBS and select an existing scene or create one for this broadcast. In the Sources dock, use the add control and choose Media Source. Give the source a recognisable name, such as “Main programme file”, so it is easier to identify later if you add a logo or other elements.
Choose the option to create a new source, then browse to the video on your computer. OBS documents support for common file types including MP4, MOV, MKV, AVI and WebM, as well as other formats. Supported extensions do not guarantee that every file will behave identically: the codec inside the container and the system’s ability to decode it can affect playback. If a file does not play, test it locally in OBS before scheduling the event.
Once added, look at the OBS preview. The source may not fill the canvas, or it may be cropped if its shape differs from the scene. For a conventional 1080p YouTube picture, a 16:9 file fits a 1920×1080 canvas without needing to stretch it. If your original video is vertical or a different aspect ratio, decide whether to preserve the full picture with empty space around it, crop some of it, or design a scene that uses the unused space. Avoid stretching faces, text or graphics just to fill the frame.
Check the whole scene, not only the file’s thumbnail or a still frame. Make sure the video is visible above any background source and not covered by an overlay. Play a short section and check that the audio meter responds if the file has sound. The guide to choosing between an OBS Media Source and a VLC playlist can help if your programme is a single file versus a sequence of clips.
Set playback and looping behaviour
A Media Source can play once, loop, or leave the scene without a picture when it reaches the end, depending on its settings. OBS’s loop option is off by default, and “Show nothing when playback ends” is on by default according to its Media Sources documentation. Check these options deliberately rather than assuming the file will repeat.
For a one-off presentation, leave looping off and decide what viewers should see after the ending. If the source disappears, the scene behind it may show through; that could be a blank background, a holding graphic or another source. Preview that result. If you want the video to repeat, enable looping and let it reach the end during a private test. Confirm that playback returns to the beginning cleanly and that the transition does not create an unwanted pause or a flash of another scene.
Do not treat a loop as a substitute for checking the file itself. A file with a black lead-in, an abrupt ending or a long silent tail will repeat those features too. If you are preparing a devotional programme or music stream, listen to the join and inspect the start and end points. For a long-running channel, the advice in how to encode devotional videos for a continuous YouTube stream is relevant to source preparation as well as the broadcast settings.
Use a local file path that will remain available for the whole stream. Moving, renaming or disconnecting the source file after configuring the scene can break playback. Keep the file on a drive that will not go to sleep or disconnect, and avoid relying on a removable device that might be unplugged. OBS is playing the file from your computer; it is not uploading the video to YouTube in advance.
Configure OBS for 1080p output
In OBS settings, set the canvas and output resolution intentionally. A common 1080p target is 1920×1080 with a 16:9 layout. The canvas is where you arrange the Media Source and any overlays; the output resolution is the size sent to the encoder. Check both, because a 1080p canvas does not by itself establish that the stream output is also 1080p.
Choose a frame rate that suits the source. For a talking presentation, devotional video or still-heavy scene, 30 frames per second may be sufficient. Motion-heavy footage may benefit from 60 frames per second, but it asks more of the encoder and upload connection. Matching the source frame rate where practical avoids needless conversion. YouTube says it detects resolution and frame rate automatically by default; a custom stream key can allow manual selection. Follow the event and key settings you have chosen rather than assuming the same control is available in every setup.
For bitrate, use YouTube’s current encoder settings and bitrate table as the reference. Its recommendations vary by codec and frame rate. The table below summarises the 1080p figures in that guidance; they are platform recommendations, not a guarantee of picture quality or stream stability.
| Output and codec | YouTube-listed minimum | YouTube-recommended bitrate |
|---|---|---|
| 1080p30 H.264 | 5 Mbps | 10 Mbps |
| 1080p60 H.264 | 6 Mbps | 17 Mbps |
| 1080p30 AV1 or HEVC | 4 Mbps | 10 Mbps |
| 1080p60 AV1 or HEVC | 4 Mbps | 12 Mbps |
Use the row for the codec and frame rate you actually select. If you choose H.264 at 1080p30, for example, YouTube’s page lists 10 Mbps as recommended and 5 Mbps as the minimum. A minimum is not a sensible target in every situation: leave room for network variation and other traffic, and test the upload from the location where you will stream. Do not raise bitrate simply because a file is labelled 1080p. A low-resolution or heavily compressed source will not gain detail when encoded at a higher output resolution.
YouTube specifies constant bitrate (CBR) and recommends a two-second keyframe interval, with no more than four seconds. Its guidance recommends RTMPS for encrypted transport. Select an encoder format supported by your setup and YouTube’s current guidance; a newer codec may not be available in every OBS installation or hardware encoder. If the available encoder cannot maintain the chosen output, reduce the demand or use a lower frame rate rather than treating the setting as a guarantee.
The output also depends on the computer doing the encoding and the upload connection. Close unnecessary workloads, keep the computer powered, and make sure the network is not being heavily used by backups or other uploads. For more on diagnosing a soft or blocky picture, see practical fixes for a blurry YouTube Live stream. Change one setting at a time during testing so you can tell whether the cause is source quality, encoding load or network capacity.
Connect OBS to the YouTube event
Open OBS’s stream settings and choose the YouTube service if it is available in your version. You can also use the custom server option when appropriate. Copy the server URL and stream key from the YouTube Live event into the matching fields in OBS. Check that you have not copied details from another event, and keep the key out of any screen recording or public support request.
Save the settings, then review the scene and audio once more before sending anything. If you are using a scheduled event, check that its time and privacy are correct. YouTube and OBS labels can shift between versions, so use the current service selection and event details shown in your software rather than relying on a menu position from an older screenshot.
Starting the encoder in OBS sends the feed to YouTube; it may not automatically make the event public. Whether the event starts automatically depends on the event and the auto-start setting. Confirm the event’s controls in YouTube Studio and understand whether you must separately start the live broadcast there. This distinction matters for a scheduled presentation: a feed can be arriving in the control room while viewers still see a waiting state.
Check the preview and stream health
Start with a private or unlisted test event where possible. After starting the encoder, wait for YouTube’s incoming preview and inspect it before you announce the stream. YouTube advises checking the preview and testing the stream; OBS also recommends a short test rather than beginning a first broadcast without one. A preview gives you a chance to catch a wrong scene, a missing file, a silent soundtrack or a picture that is cropped unexpectedly.
Check the picture and sound together. Let the file play through a section with movement and a section with speech or music. Confirm that the audio is audible in the YouTube preview, not only in your local OBS monitoring. Watch for dropped frames or encoder warnings in OBS, and use YouTube’s stream health indicators in Live Control Room. If the preview stutters, distinguish between encoder overload and network problems before changing resolution or bitrate.
A useful test includes the start and end behaviour too. If the video is meant to loop, see it return to the beginning. If it should play once, check what appears after it finishes. Make sure overlays remain legible at the actual output size and that no desktop notification or private window is visible. For an always-on setup, a test lasting only a few seconds will not reveal every overnight issue, but it can catch basic scene and connection errors before viewers arrive.
When you are satisfied, confirm the event is ready and use the appropriate control to go live. Keep OBS and the Live Control Room visible during the opening minutes. If you need a channel to run unattended for long periods, remember that OBS depends on the computer and connection continuing to operate; keeping a 24/7 study stream online overnight involves planning for interruptions beyond the initial setup.
For a pre-recorded programme that must continue while your computer is switched off, StreamNeo removes the need to keep this local OBS playback machine running by turning an uploaded video into a YouTube live stream. That is a different workflow from the local Media Source steps above, so decide whether you need OBS’s scene controls or unattended playback before committing to either approach.
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
Do I need a camera to stream a video file with OBS?
No. Add the local file to an OBS scene as a Media Source and use that scene as the stream picture. A camera is only needed if you also want a live camera image.
Which bitrate should I use for 1080p?
It depends on frame rate and codec. YouTube lists separate minimum and recommended figures for H.264 and AV1/HEVC, so use the matching row in its current encoder guidance and check that your upload and encoder can sustain the choice.
Why is the video not looping?
The Media Source loop setting is off by default, so check it in the source properties. Test the end-to-start transition before making the event public, and confirm what the scene shows when playback ends.
Does starting the stream in OBS make the YouTube event public?
Not necessarily. OBS sends the encoder feed, while the event’s auto-start behaviour or Live Control Room controls determine when the broadcast begins for viewers. Check the event status and preview before you tell people it is live.