To configure OBS Studio 30 for a 24/7 prerecorded YouTube stream, create a scene with a Media Source, select your video and enable Loop. Then connect OBS to a YouTube stream and match the output settings to YouTube’s current guidance and to what your computer and upload connection can sustain.
OBS is a local software workflow: your computer must remain on and the stream process must keep running. You do not need a particular physical product to set it up, and a cloud-hosted approach is a separate alternative if you cannot leave a computer running. Neither approach guarantees uninterrupted operation, so test and plan for interruptions before relying on the channel.
Prepare a compatible prerecorded video
Start with the exact file you intend to broadcast. Check that it plays from beginning to end on the computer where OBS will run, with the expected picture and sound. OBS’s Media Sources guide lists supported formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM for video, and MP3, AAC, OGG and WAV for audio. A supported extension is a useful first check, not a guarantee that every particular file will behave correctly; test the file in OBS as well as in a media player.
Choose an output shape that fits the content and the intended audience. A landscape devotional recording, a static study scene and a local news loop may have different visual requirements. Avoid increasing resolution or frame rate just because a setting is available. Higher output demands can require more encoding capacity and upload bandwidth, and a prerecorded scene may not benefit from settings that add no visible detail.
Listen for the transition at the end of the file. A hard cut, a brief silence or a music track that ends abruptly will recur every time the source loops. If the material is meant to run continuously, edit and export it so the end-to-start transition is acceptable. OBS’s Loop control replays the file after playback completes; it does not smooth or edit that transition for you.
Keep a stable copy of the file in a location that will remain available for the whole broadcast. If you move or rename it after setting up the source, OBS may no longer find it. Give the file a clear name and avoid relying on a temporary download folder. For a larger collection, a playlist or a different playback workflow may suit you better; this guide covers one looping file in a Media Source.
Create a scene and add a Media Source
Open OBS Studio 30 and create a scene for this broadcast. A scene is the composition OBS sends to the encoder: it can contain a video source, audio and other visual elements. For a simple prerecorded channel, one scene with one Media Source is enough to begin. Keep the initial layout plain until you have confirmed that the file plays and reaches YouTube correctly.
In the Sources panel, use the add control and choose Media Source. Give it a recognisable name, such as “Main loop”, so it is easy to identify if the scene later contains a logo, clock or other element. Create a new source, then open its properties. The OBS documentation on Media Sources describes the source controls, including Loop, restart playback when the source becomes active, hardware decoding when available and the option to show nothing when playback ends.
The source sits within the scene, so check its size and position in the preview. If the video does not fill the canvas, decide whether to preserve its proportions with unused space around it or crop it. Stretching it to fill can distort faces, text or artwork. Preview the result at the intended output dimensions, particularly if text near the edges matters on a phone screen.
Use additional sources only when they serve the broadcast. A small channel logo or a title card can be useful, but each added element is another thing to review. If you are considering a live presenter, browser overlay or screen capture rather than a single prerecorded file, a different setup may be needed; see our guide to sharing your screen while live streaming.
Select the file and enable Loop
In the Media Source properties, browse to the video file and select it. Confirm the displayed path is the copy you intend to use. If the file has audio, check that the source’s audio reaches the OBS mixer and that its meter moves during playback. A silent preview may mean the file has no audio, that its audio track is not present as expected, or that you need to inspect the source and mixer settings before going live.
Enable Loop. This tells OBS to replay the file after playback completes. Without it, the source is not configured to restart when the file ends, which is a common reason a loop channel shows a finished frame or an empty canvas. Do not assume that a successful first playback proves looping works: let the source reach the end during a test and watch for the transition back to the beginning.
Review the related playback controls for the behaviour you want. Restart playback when the source becomes active can be useful if you switch scenes and return to this one, but it also means the file may start from the beginning when reactivated. The setting to show nothing when playback ends has a different purpose and does not substitute for Loop. For a single-file continuous scene, Loop is the important control.
Observe both picture and sound at the loop point. Listen for a gap, repeated click or abrupt change in volume. If your channel mixes material with pauses, playlists or scheduled content rather than repeating a single video, OBS’s single-source loop may not provide the transitions you need. For another approach to gaps between clips, compare the FFmpeg loop pause guide.
Configure the YouTube encoder connection
In YouTube Live Control Room, create or select the live stream you intend to use. YouTube’s encoder setup instructions describe connecting an encoder by entering the stream URL and stream key in its stream settings. In OBS, open the stream settings, select YouTube if offered, or use the appropriate custom connection fields, then enter the details shown by YouTube. The exact labels and layout can vary with the selected service and OBS interface, so follow the current on-screen instructions rather than relying on a screenshot from a different version.
Treat the stream key as a password. It connects an encoder to your broadcast, so do not put it in a public document, screenshot, chat or article. If you believe it has been exposed, use YouTube’s current controls to replace or reset it before broadcasting again. Keep access limited to people who need to operate the channel.
Starting the encoder does not always mean the public broadcast is live. YouTube’s workflow can show an incoming preview in Live Control Room, and a scheduled broadcast may require you to use its Go live action after checking that preview. Confirm which state the stream is in before sharing its watch page. Also check whether the selected broadcast is public, unlisted or private, according to your intended audience.
Do not confuse a configured connection with a stable one. A brief connection test only establishes that OBS can send data at that moment. YouTube’s encoder guidance recommends checking stream health and testing with representative material, but it does not guarantee that a connection will remain up all night. Keep the Live Control Room open during initial tests so you can see whether YouTube is receiving the stream and whether it reports a problem.
Set output and bitrate using current YouTube guidance
Use YouTube’s encoder settings and bitrate table as the reference for the output you choose. Its current guidance covers RTMP or RTMPS, H.264, H.265 (HEVC) or AV1, constant bitrate (CBR), frame rates up to 60 fps, and a recommended two-second keyframe interval that should not exceed four seconds. Check the live page when configuring your stream: guidance can change, and settings for one codec or frame rate should not be copied blindly to another.
In OBS, review the output mode and streaming encoder options. Match the codec, resolution and frame rate to the YouTube table, then set the keyframe interval and rate control accordingly. If the encoder offers CBR, use it in line with YouTube’s recommendation. Menu names can differ depending on the encoder and platform; if a field is not available, check the current OBS help and YouTube guidance rather than guessing what a similarly named control does.
Bitrate is not a universal fixed setting. It depends on the selected codec, resolution and frame rate, and the upload connection must be able to sustain it. For example, YouTube’s current H.264 table recommends 5 Mbps for 1080p at 30 fps and 6 Mbps for 1080p at 60 fps. For 720p, it recommends 3 Mbps at 30 fps and 8 Mbps at 60 fps. These are YouTube recommendations, not a guarantee that your connection or encoder can hold the rate. Use the row for your actual configuration and check the current table before setup.
| Choice to match | Why it matters | What to check |
|---|---|---|
| Codec | YouTube’s bitrate guidance differs by codec. | Select a codec supported by your chosen encoder and follow the matching YouTube table. |
| Resolution | More picture detail can raise the bandwidth and encoding demand. | Choose a resolution that suits the source and can be sustained locally. |
| Frame rate | A higher frame rate can increase encoding work and change the recommended bitrate. | Use the frame rate that serves the content; do not select 60 fps by default for a static scene. |
| Upload capacity | The outbound connection must carry the encoded stream consistently. | Test the actual connection and leave room for normal variation rather than planning around a best moment. |
For a static ambience or devotional video, 30 fps may be adequate, but choose based on the source and how motion looks. OBS notes that 60-fps streaming can be demanding on a system compared with 30 fps. If you see dropped frames, encoder overload or unstable stream health, reduce the output demands and test again. For advice on diagnosing load when OBS loops video, see how to reduce CPU usage when OBS loops videos.
Preview, test and monitor the stream
Before publishing, watch the OBS preview and listen to the mixer while the file plays. Check that the image is correctly framed, sound is present at an appropriate level, and no unintended desktop audio or microphone source is being sent. If you have a title or logo, check that it remains readable and does not cover important content. A local preview helps catch scene problems before they reach viewers.
Then run a private or unlisted test, as appropriate for your channel, and confirm that YouTube receives it. Use representative audio and motion, not only a static opening frame. Let the file approach and cross its end so you can see whether Loop works. Watch YouTube’s stream-health indicators and OBS’s status information while the test is running; a clean preview on your own computer does not prove the upload is healthy.
Test under the conditions you expect to use. If the computer will normally be on Wi-Fi, a test on wired Ethernet does not tell you how the normal setup will behave. If other people in the building use the same connection, test at a time when that is likely to matter. Avoid running large uploads or downloads during a sustained test, and note whether the connection or encoder reports trouble.
A short test is not evidence of 24/7 reliability. It can expose obvious problems with the scene, file, key or bitrate, but it cannot prove that the computer, power, network or YouTube ingest will remain available indefinitely. Keep a record of which settings worked and what warnings appeared. Change one setting at a time so you can tell whether an adjustment improves or worsens the result.
Plan for sustained operation and recovery
With a local OBS setup, the computer running OBS must stay powered on, connected and able to play the file and encode the output. Consider the practical environment: sleep settings, operating system updates, an accidental shutdown, local power interruptions, network changes and storage access. Preventing automatic sleep may be necessary, but it does not prevent every interruption. If the machine needs a reboot or a person must sign back in after an update, decide who will handle that before treating the channel as unattended.
Keep the source file and scene configuration recoverable. Record where the file is stored, which scene is used, and which output choices you selected. Do not record the stream key in a public setup note. If OBS closes or the connection drops, have a human check whether the encoder is still running and whether YouTube is receiving it before assuming a restart has restored the broadcast. OBS’s overview describes the application and its streaming workflow, but the available official guidance does not establish an unattended recovery guarantee.
YouTube’s setup page says streams under 12 hours are automatically archived. That statement does not establish what happens to a stream that stays live longer, or whether a multi-day broadcast will be preserved as one complete archive. If keeping a replay matters, check YouTube’s current documentation and your Live Control Room rather than relying on an assumption about a 24/7 stream.
If you cannot keep a local computer and connection operating, compare a software-based local workflow with a cloud-hosted prerecorded-streaming service. YouTube’s encoder setup page lists a cloud-based prerecorded streaming option, but provider behaviour and terms differ; assess each provider’s documented controls, limitations and recovery process. A cloud service can remove the need to leave your own computer running, but it is not an assurance of uninterrupted broadcasting. StreamNeo removes the specific burden of leaving your computer on by turning an uploaded video into a YouTube broadcast that runs without your local machine; you still need to check the stream and plan for interruptions.
Choose the operating method around the control you need. OBS is useful if you want to build and adjust scenes on your own computer. A cloud service may suit a single-file loop when you cannot leave a computer running, while a reader who wants hands-on control of a more complex live composition may prefer a local encoder. For a broader comparison of local and alternative approaches, see OBS versus FFmpeg for a 24/7 YouTube loop.
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
Does OBS Studio 30 need a special physical product to stream a prerecorded video?
No particular physical product is required by the setup described here. OBS runs on a computer that can play the file, encode the output and sustain the upload; the computer and connection you already have may or may not be capable enough for your chosen settings. Test your actual configuration before relying on it.
Why does my video stop instead of starting again?
Open the Media Source properties and check that Loop is enabled for the selected file. Then test through the end of playback, because a normal first pass does not confirm that the loop transition behaves as intended. If it still stops, check that OBS is using the source and file you expect.
Can I use YouTube’s recommended bitrate as a guarantee that my stream will work?
No. YouTube’s bitrate table is a platform recommendation for a particular codec, resolution and frame rate, not a promise about your encoder or upload connection. Match the table to your output, test stream health and lower demands if your setup cannot sustain them.
Will YouTube keep one complete archive of a 24/7 stream?
YouTube’s encoder setup page states that streams under 12 hours are automatically archived, but that does not establish how a broadcast longer than that will be archived. Check YouTube’s current documentation and the Live Control Room if preservation matters, and do not assume a multi-day stream will become one complete replay.