To set up a YouTube Live loop on a Windows mini PC, add your local video to OBS as a Media Source, enable Loop, and connect OBS to the stream URL and key in YouTube Live Control Room. Keep Windows awake, then check the picture, sound, upload path and YouTube preview before you make the stream public.
This is a practical setup for repeating one video file, not a promise that a small computer or internet connection will run without interruption. YouTube’s automatic archive guidance applies to streams under 12 hours; do not assume a longer loop will produce a complete recording.
Check the mini PC and stream prerequisites
First confirm that the YouTube channel is allowed to go live. YouTube requires a verified channel without live-streaming restrictions in the previous 90 days. If you have not streamed before, enabling live access can take up to 24 hours, so do not leave activation until the planned broadcast. Check the current YouTube live-streaming eligibility guidance before scheduling your first session.
The mini PC needs to run OBS while reading the video file and sending the encoded stream over your internet connection. There is no universal processor, memory or graphics specification that fits every file and output setting. A still devotional image with audio and a high-motion video are different workloads, and resolution and frame rate affect the work the machine must do. OBS notes that 60 fps can be considerably more demanding than 30 fps; test the settings you intend to use on your own machine rather than relying on a generic minimum.
Install OBS Studio and place the video file somewhere that will remain available, such as a local drive. Avoid moving, renaming or disconnecting that file after you have configured the source. If Windows or OBS cannot find the file when the scene loads, the preview may be blank even though the scene itself is still present.
Check the upload connection as well as the PC. YouTube advises that outbound upload capacity should exceed the stream’s total bitrate and recommends leaving 20% bandwidth headroom. That is guidance, not a guarantee: other devices using the same connection can reduce the bandwidth available to OBS, and a broken connection can interrupt the broadcast. For a longer setup discussion, see what to check when an OBS YouTube stream keeps disconnecting.
A mini PC can be a sensible compact machine for a fixed stream, but it still needs a sustained test. Run the intended scene and output settings long enough to see whether playback, audio and stream health remain acceptable. If the machine struggles, reduce the output demands and repeat the test before relying on it for a scheduled broadcast.
Add a local Media Source in OBS
Open OBS and create a scene for the loop. A scene is the collection of sources OBS sends to the stream; for this simple setup it can contain the prerecorded video and any overlays you actually need. Keep the first version plain so you can establish that the file plays correctly before adding logos, text or browser content.
In the Sources panel, choose +, then Media Source. Give it a recognisable name, such as “Main loop”, and choose the local video file. OBS supports common formats including MP4, TS, MOV, MKV, AVI, GIF and WebM. If the source properties offer Local File, make sure it is selected for a file stored on the mini PC, then use Browse to locate the correct file.
When the source is added, look at the OBS preview. Confirm the video appears at the expected size and that the file starts at the beginning. If the picture does not fill the canvas, adjust its size or position in the preview rather than stretching it without checking the result. Check that the source is not hidden and that its visibility control is enabled.
Audio deserves its own check. Watch the OBS audio mixer while the file plays. A moving meter indicates OBS is receiving audio, but it does not tell you whether the level sounds right or whether the correct track is being sent. Listen through the mini PC’s audio output or headphones, and check that music, speech or ambience is neither silent nor distorted. If the video is intentionally silent, verify that this is the expected result rather than assuming the audio path works.
If you want to rotate several files rather than repeat one, that is a different configuration. OBS can use a VLC Video source with a playlist, but VLC must be installed and its architecture must match OBS; for 64-bit OBS, use 64-bit VLC. For one file, the Media Source is the simpler choice. If you are weighing a more complex rotation against a single loop, OBS and FFmpeg playlist approaches address that separate decision.
The OBS Media Sources documentation describes the source options. Keep the first test close to the final broadcast: use the same file, scene dimensions, audio and output settings you expect to run, so a successful preview is meaningful.
Enable the source Loop option
Double-click the Media Source in the Sources panel to open its properties. Turn on Loop and confirm the selection. With Loop enabled, OBS starts the file again when playback reaches its end. It does not create a longer video file; the source repeats the same local media during the live output.
Before moving to YouTube, let the file reach its end in the OBS preview. Confirm that it starts again and that the transition is acceptable. A visible pause, black frame or abrupt audio cut at the boundary may be part of the file itself, or it may be the way playback transitions. Check the file’s start and end in a media player, then test the actual source in OBS. Do not assume the Loop checkbox corrects a rough edit.
For a devotional track, for example, listen across the join between the end of the recording and its restart. For an ambience video, watch whether the first frame differs sharply from the last. If the boundary is distracting, revise the file before streaming. The guide to avoiding repeated black frames in prerecorded streams offers useful checks for a loop that does not look seamless.
Once looping behaves as expected, leave the source properties in place and save the scene collection. Reopen OBS if practical and verify that the scene still finds the file. A source configured against a removable drive or a file path that later changes can fail after a restart, even if it worked during the initial setup.
Connect OBS to YouTube Live
In YouTube Studio, open Create > Go Live. In Live Control Room, create or choose the stream and open the Stream tab. YouTube provides the stream URL and stream key that OBS needs to send its output to your channel. The names and screen layout can change, so consult the current YouTube encoder setup instructions if the controls are not where you expect.
Treat the stream key as a password. Anyone with access to it may be able to send a broadcast to the stream, so do not paste it into a public document, screenshot or chat. If you expose it, reset it in YouTube Studio before relying on that key again.
In OBS, open Settings > Stream. Choose YouTube from the service list if the relevant connection option is available, then follow the prompts or enter the stream details requested. If using a stream URL and key, copy them from Live Control Room carefully. Keep the key private and avoid sharing a screenshot that includes it.
Start the encoder by selecting Start Streaming in OBS. This sends the video to YouTube, but it may not mean the event is public yet. Return to Live Control Room and wait for the incoming preview and stream health information. Inspect the picture and sound there. When you are satisfied and the stream is ready for its audience, use YouTube’s Go live control as appropriate for the event setup.
For a first attempt, use a test or unlisted event if that suits your channel and audience. Check the current event visibility before starting; do not assume that a test is private just because you are still looking at the encoder. The stream-key setup guide for an always-on broadcast covers the key side of this workflow in more detail.
Keep Windows awake during the stream
Windows power settings can put the mini PC to sleep after a period of inactivity. If the machine sleeps, OBS cannot keep encoding and sending the loop as intended. Set the sleep behaviour for the period you plan to stream, and check it again after Windows updates or changes to the power plan.
On Windows 11, open Start > Settings > System > Power & battery > Screen, sleep, & hibernate timeouts. Set the sleep timeout so the PC does not enter sleep during the scheduled session. The screen timeout is separate: you can let the display turn off while choosing a different sleep setting for the computer. Microsoft’s Windows 11 power settings guidance explains these controls.
Do not confuse a dark or switched-off monitor with a sleeping computer. The display can turn off while the mini PC keeps working; the setting that matters to OBS is the system sleep behaviour. Check that the mini PC has adequate ventilation and that its power supply is secure. Those are practical checks, not assurances that a particular PC will operate continuously.
If the device is shared with other work, consider whether someone may shut it down, restart it or change its power settings. Close applications that are not needed for the stream, but avoid disabling updates or security protections blindly. Schedule maintenance outside the broadcast where possible and review any restart prompts before the stream begins.
A Windows setting cannot protect against a power cut, internet outage, application crash or a machine overheating. If a broadcast matters, decide in advance who will check it and what you will do if the stream drops. For a local devotional or music station, a UPS for a 24/7 streaming PC may be worth evaluating against the power conditions at your location, but it cannot solve network or software failures.
Test video, audio, upload and preview
A scene that looks right in OBS is only one part of the path. Run a test that includes the source, OBS encoding, internet upload and YouTube’s incoming preview. A short test can expose an incorrect key or missing audio; a representative sustained run is more useful for checking how the mini PC behaves under the actual load.
Use a checklist before the public event:
| Check | What to look for | If it fails |
|---|---|---|
| Video source | The local file plays, fills the intended area and restarts at its end | Recheck the selected file, visibility, transform and Loop property |
| Audio | The OBS meter moves as expected and playback sounds clear | Check the file, source audio, mixer level and monitoring device |
| Upload | OBS sends the configured output and YouTube receives it without persistent health warnings | Check competing network use and whether upload capacity has headroom over total bitrate |
| YouTube preview | Live Control Room shows the expected picture and sound | Do not announce the stream until the incoming preview is right |
| Sustained run | Playback and encoding remain acceptable over a representative period | Reduce output demands, check the PC and repeat the test |
YouTube recommends previewing before going live and monitoring audio and video quality. The YouTube streaming tips explain its advice on upload bandwidth and leaving headroom. A speed test can help you understand the connection, but it is not a substitute for observing the actual stream: the available upload can vary, especially on a shared connection.
Choose modest output settings that suit both the source and the mini PC. There is no need to force a higher resolution or frame rate than the material and audience require. OBS’s overview notes the greater demand that 60 fps can place on a system compared with 30 fps, so assess the real scene rather than deciding from the product label on the PC. If the output stutters, test a lower setting and compare the YouTube preview and stream health.
Listen at YouTube as well as locally. A sound that is audible in the room may not be reaching the encoder, or the stream may have a different level than expected. Check speech intelligibility, music level and silence between sections. If your file has a long quiet opening, make sure the quiet is intentional and that viewers do not mistake a working stream for a fault.
If the stream is meant to run while you are away from the mini PC, decide how you will notice a problem. OBS and YouTube status indicators are useful when you are present, but they do not eliminate the need to monitor the broadcast in a way that suits its importance. For detailed output-setting comparisons, see the 720p upload settings guide for a YouTube loop in India; treat settings there as a starting point to test, not a universal configuration.
Understand the archive caveat
A live loop and a saved replay are separate things. YouTube says streams under 12 hours are automatically archived. The cited guidance does not establish a complete archive guarantee for a stream longer than 12 hours, so do not build a recording plan around the assumption that a day-long or continuous loop will be available in full as a replay.
If you need a copy of the content, keep the original local video and any separate audio or project files you may need. For a long live event, review YouTube’s current archiving guidance before you decide how to preserve the broadcast. This is especially important if viewers will depend on a replay or if you need to retain a particular event in full.
Set expectations with your audience accordingly. You can tell viewers when the live stream is planned, but avoid promising that a long broadcast will remain available as a complete recording. If an archive matters, test the workflow with an event whose length falls within YouTube’s stated guidance and check the resulting video after the event; that still does not establish what will happen for a stream longer than 12 hours.
When ending a planned stream, use the event controls in YouTube and stop the encoder in OBS. Confirm that the broadcast has ended where you expect. Keep the source file unchanged until you have checked what, if anything, YouTube has retained and decided whether another recording is needed.
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 OBS loop one video file on YouTube Live?
Yes. Add the local file as an OBS Media Source and enable its Loop option. Test the end-to-start transition in the preview, since the setting repeats playback but does not repair a rough edit or a black frame in the file.
Can I turn off the mini PC screen without stopping the stream?
You can set the screen timeout separately from the system sleep timeout in Windows 11. The display can turn off while the computer stays awake, but confirm the sleep setting and test your exact power configuration before a scheduled broadcast.
Do I need a specific mini PC processor or graphics card?
There is no universal minimum established for every video and output setting. Use a modest resolution and frame rate that match your content, then test OBS and the YouTube preview under sustained load on the actual mini PC.
Will YouTube keep the full archive of a loop longer than 12 hours?
YouTube’s cited guidance says streams under 12 hours are automatically archived; it does not establish complete archiving for longer streams. Keep the original media and check the current official guidance rather than relying on a full replay being available.