To stream a Minecraft survival world archive on repeat, load a recording into OBS Studio, enable its loop setting, and send the encoder output to a YouTube Live broadcast. Before you go live, check that you can use every part of the recording, especially music and other third-party audio, and decide whether YouTube should keep a replay.
A loop only controls playback of the source file. It does not keep your computer, internet connection, YouTube broadcast or archive processing running without interruption. This guide takes you from a local recording to a live feed and gives you checks to run before leaving it unattended.
Check the archive file and rights
Start with the recording, not the streaming controls. Play the whole file locally, or review it in sections if it is long. Check that the footage is the version you intend to broadcast, that the audio is audible at a consistent level, and that there are no unfinished edits, private information or long blank sections. Look at the beginning and end closely: those are the points viewers will encounter on every repeat.
Keep the source file in a stable location while OBS is using it. Moving, renaming or deleting it can leave the source unable to find the file. If you plan to run the stream from a different computer, copy the recording there and test that copy before configuring the broadcast.
Minecraft’s Usage Guidelines for Fans and Creators allow creators to share gameplay videos and streams, subject to the guidelines. They say the content must remain free to view and should include meaningful creator contribution; commentary is one example. A logo or overlay by itself may not make a recording sufficiently distinctive. Do not assume that putting an unchanged archive on repeat automatically meets every guideline or makes it eligible for monetisation. Consider the actual footage, its presentation and the complete current guidance.
Gameplay permission does not clear the soundtrack. Review game audio, background tracks, sound effects, voice clips and any music added during editing separately. Minecraft’s guidelines require permission for third-party audio, and YouTube says it scans live streams for third-party content. A match can lead to a warning, a placeholder, interruption or termination; a Content ID claim may also appear on an archived stream after it ends. If you have a licence, check its terms for both live streaming and replay use. YouTube notes that a rights owner may need to allowlist your channel for licensed content to avoid live interruption. See YouTube’s guidance on copyrighted content in live streams.
Make a simple inventory before opening OBS: the gameplay recording, its game audio, any added music, voice commentary, and anything else viewers will hear. For each component, note its source and whether your permission covers a livestream and an archived replay. If you cannot establish the status of a track, remove or replace it with audio you can use rather than relying on the stream appearing to work.
Choose a local encoder or cloud workflow
With a local workflow, OBS reads the recording on your computer and sends the resulting feed to YouTube. This gives you direct access to the source and encoder controls, but the computer must stay on and the network connection must remain suitable for streaming. A power cut, system update, sleep setting or encoder problem can stop the feed. A loop setting cannot correct those failures.
A cloud workflow can be useful if you do not want your own computer to run throughout the broadcast. For a fixed archive, StreamNeo removes the specific burden of keeping OBS and your computer running for the repeat: you upload the file, provide your YouTube stream key and manage the broadcast from the cloud. YouTube access and audio rights remain your responsibility, and a cloud workflow does not guarantee that a live broadcast or its replay will be uninterrupted.
| Workflow | What runs the file | What you need to watch |
|---|---|---|
| Local OBS, one recording | OBS Media Source on your computer | Power, sleep settings, OBS and internet connection |
| Local OBS, several recordings | OBS VLC Video source with a playlist | Playlist order, VLC installation and transitions between files |
| Cloud playback | A cloud workflow runs the uploaded file | File readiness, stream configuration, channel status and YouTube dashboard |
For one recording, a Media Source is the simplest place to begin. For a sequence of recordings, a playlist source avoids manually replacing the file after each play. If you are still deciding between ways to run a long broadcast, the trade-offs of a local 24/7 streaming computer are useful context; the right choice depends on what you can monitor and maintain, not on a universal best option.
Add the video in OBS as a Media Source
Install OBS Studio from its official source and open the scene you intend to use for the live feed. A scene determines what appears in the stream; for a single archive it can be as simple as one video source. Add a Media Source and choose the local recording file. OBS’s Media Sources documentation describes supported options and controls, including common video containers such as MP4, MOV, MKV, AVI and WebM. That does not mean every file using one of those extensions will play in every setup: codecs, file integrity and the local playback environment still matter.
After selecting the file, check that the source fits the canvas as intended. If the recording is a different aspect ratio from your stream layout, decide whether to preserve the full picture with empty space around it or crop part of the image. Do not stretch the video to fill the canvas if doing so distorts the game view. Play the source in OBS and confirm that both picture and audio reach the preview and audio mixer.
If you have several recordings, OBS also offers a VLC Video source for playlists. It requires VLC to be installed; the OBS guidance specifies matching the VLC installation architecture to OBS, such as 64-bit VLC for 64-bit OBS. Load the playlist, confirm the order, and check the Loop Playlist option. This is different from looping one Media Source file: decide whether you want a single recording to restart or a set of recordings to play through in sequence.
You do not need to construct an HLS playlist or use YouTube’s Live Streaming API for an ordinary OBS broadcast. Those tools serve different technical workflows. For a beginner-friendly overview of encoder scenes and broadcast setup, see this step-by-step streaming software guide.
Enable Loop and verify playback
In the Media Source properties, enable Loop. OBS documents this option as off by default; when enabled, the file starts again after playback completes. Test the setting before starting the YouTube event. Let the file reach its end and observe the transition into the next play rather than assuming that a checked box proves the whole setup works.
Watch for a flash of black, a frozen final frame, an audio click, a pause or a sudden change in volume at the boundary. If the recording begins with a fade-in or silence, viewers will hear that on every repeat. If the last frame differs sharply from the first, the visual jump will also recur. You can make a cleaner loop by editing the file’s ends, but preserve any part of the recording that matters to its meaning and review the edited version for sound and rights again.
For a playlist, test the boundary between each item as well as the final item returning to the first. A playlist that works once may still have an unwanted gap or mismatch at the restart. If OBS shows black between successive videos, this guide to fixing a black screen between videos covers a related failure mode. A file conversion can sometimes help when the source is not playing reliably, but check the converted file rather than assuming the extension change fixed it; the WebM-to-MP4 conversion walkthrough explains that separate task.
Check what happens if you stop and reopen OBS. Confirm the source still points to the right file, the scene is intact and the loop remains enabled. Also check that Windows or macOS will not put the computer to sleep during a local run. Do a short test broadcast or use the platform’s available preview controls before committing to a long session.
Send the encoder feed to YouTube Live
In YouTube Studio, set up or schedule the live broadcast using the channel’s available live controls. Channel access and eligibility can depend on the account’s current status, so check the dashboard rather than relying on an old setup guide. OBS needs the corresponding YouTube streaming settings, including the stream key. Treat the key as private: anyone who obtains it may be able to send a feed to the broadcast configuration.
Connect OBS to YouTube using the platform’s normal encoder workflow, then send a short test. Confirm in YouTube Studio that the incoming picture and sound are what you expect before starting the event for viewers. Follow the broadcast controls shown in Studio to start the live event; sending an encoder feed and making the broadcast live are related but distinct steps in this workflow.
If you plan recurring broadcasts, distinguish the reusable stream configuration from each individual broadcast event. Google’s YouTube Live broadcasts and streams documentation describes stream resources and broadcast resources separately, including reuse of a stream configuration for recurring broadcasts. You do not need to use the API to do this in Studio, but the distinction helps when planning a schedule: a saved encoder configuration is not the same thing as an event that is currently live. YouTube’s documentation describes only one event live at a time in the relevant recurring-broadcast scenario.
Avoid making a schedule more complicated than the channel needs. For one ongoing archive, test the event controls you will use and record how to reconnect if the encoder stops. For a rotating schedule, plan how the next event will be created and how its archive settings will be checked. A guide to scheduling YouTube Live playlist changes is relevant when a channel has planned source changes, rather than one file repeating indefinitely.
Check the live picture, audio, and replay settings
Once the event is live, check the YouTube viewing page as well as OBS’s preview. Look for the right scene, legible game picture, expected audio and a stable incoming feed. Monitor the YouTube Live dashboard for warnings or signal problems. If you are running locally, keep OBS and the computer available; if you leave the room, do not confuse the loop continuing in preview with proof that YouTube is still receiving a usable stream.
Decide whether viewers should be able to watch the broadcast afterward. If so, check the archive setting for the specific event before going live. Archive behaviour belongs to the broadcast, not merely to the reusable stream settings. When the event has ended, allow time for processing and inspect the replay itself: check its beginning and ending, picture and audio, and whether any claim or restriction has appeared. An event appearing in Studio does not mean its replay has finished processing.
A replay is another use of the material, so revisit the audio rights inventory for that use. Live playback appearing without an immediate warning does not establish clearance, and YouTube says a Content ID claim can be made after an archived live stream finishes. If a claim appears, read the details and follow YouTube’s current dispute or editing options only where you have a valid basis. Do not assume a gameplay permission resolves a soundtrack claim.
Keep a brief operating note for the next session: which file was tested, which scene and source were used, whether the loop boundary was clean, which broadcast was created, and whether the replay was checked. If you change the recording or its audio, repeat the rights and playback checks. If the channel will run overnight, make the first unattended period a deliberate test after you have verified the live dashboard and local or cloud workflow.
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 loop one Minecraft recording without making a playlist?
Yes. Add the file as an OBS Media Source and enable Loop in its properties. Test the ending and restart in the preview, because the setting repeats playback but does not guarantee a seamless transition or an uninterrupted live broadcast.
Does Minecraft gameplay permission cover music in my recording?
No. Gameplay guidance does not clear third-party music, sound effects or other audio. Check permission for each soundtrack element and for both live use and any replay, and consult YouTube’s current copyright guidance if you are unsure.
Can I use several survival recordings in one repeating feed?
Yes, an OBS VLC Video source can play a playlist, with Loop Playlist enabled to restart after the last item. VLC must be installed, and you should test every transition and the final return to the first recording before going live.
Will YouTube keep the replay automatically?
Do not assume so. Check the archive setting for the individual broadcast, then inspect the replay after processing. YouTube may also make a Content ID claim on an archived live stream after it finishes, even if the live feed appeared to play normally.