To loop a 4K video on YouTube Live, add the local file to OBS as a Media Source and enable Loop. Then send OBS’s programme output to YouTube with resolution, frame rate, codec and bitrate suited to the source and to the upload connection you have tested.
Looping makes the file play again when it ends; it does not stabilise the route from OBS to YouTube. If frames drop, treat that as a separate delivery problem: check OBS’s counters and YouTube’s stream health, then test the encoder settings and network path rather than changing the loop option.
Set up a looping 4K Media Source
In OBS, add a Media Source to the scene that will be on air. Select the local video file and enable Loop in the source properties. The source repeats playback when it reaches the end, so YouTube does not need a separate loop setting for this workflow. OBS lists formats including MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM in its Media Sources documentation.
Before you build the rest of the scene around the file, check that it plays from beginning to end in OBS. Watch the transition back to the start: a file can repeat without an obvious pause, but a visible jump, black frame or audio gap at the boundary may come from the edit itself. Looping cannot repair a discontinuity already present in the file.
Set the OBS canvas and output to the resolution and frame rate you intend to send. If the source is 2160p at 30 frames per second, for example, a 2160p30 output is a natural starting point. Do not assume that labelling a file “4K” means every part of the workflow is already set to 4K; inspect the OBS video and output settings as well as the file properties.
If you are new to looping a local file, this workflow is different from building a rotation of several clips. The guide to making a YouTube Live stream repeat a video automatically covers the repeat behaviour; here, the concern is getting one 4K source through the encoder and across the connection reliably.
Match resolution and frame rate to the source
Resolution and frame rate determine how much visual information OBS must process and send. Start with what the footage actually contains, not with the highest setting available in a drop-down menu. A 2160p30 file does not gain detail by being sent as 2160p60; the higher output rate may add processing and bitrate demands without adding source frames.
YouTube Live Control Room can detect incoming resolution and frame rate automatically. With a custom stream key, YouTube also allows manual resolution settings. Confirm what the control room reports during testing, rather than relying only on the OBS output label. YouTube’s encoder settings guidance describes the supported settings and how to configure them.
A mismatch can create a stream different from the source in ways that matter. If OBS scales a lower-resolution video up, it cannot restore detail that was not in the original. If frame rates differ, OBS has to adapt the output cadence. For a static devotional image with modest movement, the cost may be less apparent than it would be in a fast-moving news clip, but the settings should still be deliberate.
For a long-running channel, choose the output that your content and equipment can sustain, not simply the largest combination you can select. Compare the resolution and frame rate, codec, available sustained upload capacity, and the encoding capacity of the computer. YouTube recognises software and hardware encoders; a dedicated hardware encoder is not automatically required just to repeat a local file.
Choose YouTube encoder settings for the source
YouTube’s published bitrate guidance varies by resolution, frame rate and codec. For 2160p30, the table gives AV1/H.265 a minimum of 8 Mbps and a maximum of 35 Mbps, and recommends 30 Mbps for H.264. For 2160p60, it gives AV1/H.265 a minimum of 10 Mbps and a maximum of 40 Mbps, and recommends 35 Mbps for H.264. These are platform encoder values, not a promise that a particular internet connection can sustain the stream.
| YouTube output | AV1/H.265 published range | H.264 recommendation |
|---|---|---|
| 2160p at 30 fps | 8–35 Mbps | 30 Mbps |
| 2160p at 60 fps | 10–40 Mbps | 35 Mbps |
Use the row matching your intended output, and the codec column matching your encoder. Do not treat the H.264 recommendation as interchangeable with the AV1/H.265 range. The YouTube guidance also lists RTMP/RTMPS, constant bitrate (CBR), and a recommended keyframe interval of two seconds, with four seconds as the maximum. Check the current table before configuring a production stream, especially if YouTube changes its guidance.
The practical question is not only “What bitrate does 4K need?” but “What bitrate can this connection keep sending?” YouTube recommends testing upload bitrate and choosing a quality that is reliable for your connection. A speed test is a useful first check, but a short test does not show how your connection behaves over a long session or when other people and devices are using it. Leave room for that other network use rather than setting OBS at the edge of a single speed-test result.
If your sustained upload capacity cannot support the selected 4K combination comfortably, consider reducing frame rate or resolution instead of forcing a high bitrate. A lower, stable output can be more useful to viewers than nominal 4K accompanied by interruptions. Conversely, a strong connection does not remove the need to check whether the computer can encode the selected codec and frame rate.
For another focused setting, use the guide to set OBS keyframes for better stream quality. Keep the keyframe interval consistent with YouTube’s published guidance; changing keyframes is not a substitute for adequate upload capacity.
Why OBS drops frames
A file that stops, fails to repeat or has a gap at its loop point is a playback or source issue. Network-dropped frames are different: OBS says they mean the connection to the remote server is unstable or cannot keep up with the configured bitrate. The OBS connection troubleshooting guide explains this distinction and the checks to make.
Check the OBS dropped-frame counter while sending the stream, and compare it with the stream health information in YouTube Live Control Room. If the file continues playing locally but the outgoing stream reports dropped frames, changing the Media Source’s Loop setting is unlikely to help. Investigate whether the chosen bitrate is sustainable, whether the local network is unstable, and whether another application or device is competing for upload capacity.
A network counter is not the only possible sign of trouble. If the preview stutters while OBS reports no network drops, look separately at rendering and encoding performance: the computer may be struggling to compose or encode the scene. Reduce unnecessary scene complexity, check the encoder load, and test again before lowering network settings at random. Diagnose what the counters and preview show before making changes.
OBS describes dynamic bitrate adjustment as a way to lower bitrate when congestion occurs. That may help keep data flowing during a temporary dip, but it does not fix the underlying connection and it reduces video quality while the bitrate is lower. For a fixed 4K target, a repeatable test with a sustainable setting is more informative than relying on an automatic adjustment to conceal a persistent problem.
Check the route to YouTube’s ingest server
The computer sends the encoded stream over your network to a YouTube ingest server. The route may be affected by the connection inside your premises, the router, the internet service provider’s path, or congestion beyond your own equipment. A video looping cleanly in OBS only confirms that playback continues; it says nothing about whether this route can carry the selected bitrate without interruption.
If the computer is on Wi-Fi, test over a wired connection where practical. OBS recommends wired networking because Wi-Fi can be unstable for streaming. An Ethernet cable can remove one source of local variation, but it cannot guarantee that the ISP route or YouTube ingest connection stays stable. It is a useful comparison, not a universal cure.
Test at the time and from the location where the channel will normally run. Close or pause uploads, cloud backups and other traffic that are not needed for the test. If a stream improves when those uses stop, you have evidence of contention on the shared connection. If it does not, the cause may be elsewhere; avoid assuming that buying new local equipment will fix an upstream route problem.
When drops persist after local checks, record the OBS log and note the stream settings and time of the issue. OBS advises contacting your ISP with details when connection trouble continues. If your current setup depends on OBS running on a spare computer, the guide to running a 24/7 Bhojpuri music channel from a spare laptop may help you assess the limits of that arrangement, but it does not change the need to test the connection itself.
Test the complete broadcast before going live
A useful test includes the actual file, scene, encoder, network connection and YouTube preview. Use a representative section with the movement and audio your channel will carry; a still image alone may not expose encoding load or an awkward loop boundary. Let the source reach its end and start again, then confirm both playback and the outgoing stream.
In Live Control Room, check the incoming preview and stream health. In OBS, watch the dropped-frame counter and relevant rendering or encoding indicators. If you change one setting, repeat the test and note whether the symptom changed. Altering several settings at once makes it difficult to learn whether the cause was bitrate, frame rate, codec, local load or the route.
A preflight should cover the following:
- The Media Source plays and loops through its end without an unwanted pause or audio gap.
- OBS output resolution and frame rate match the planned stream and the source’s real properties.
- Codec, bitrate, CBR and keyframe interval match the applicable YouTube guidance.
- Upload capacity has been tested with room for ordinary network use.
- Live Control Room preview and stream health are checked while the test is running.
- OBS counters are watched so network drops can be distinguished from encoding or rendering trouble.
YouTube recommends testing before the live event and monitoring stream health. Its published settings say 2160p does not offer the low-latency option; a 4K stream uses normal latency. If low latency is a requirement, factor that limitation into the format decision rather than expecting a different loop setting to change it.
For a channel that needs the video to continue while your own computer is switched off, StreamNeo removes the specific burden of leaving OBS running on that computer: you upload the video, provide the YouTube stream key, and it runs the broadcast with monitoring and automatic restarts if it drops. It is YouTube-only, and you still need to prepare the file and channel and confirm the stream behaves as intended.
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
How do I loop a video on YouTube Live?
Add the local file as a Media Source in OBS and turn on Loop. OBS repeats the file; YouTube receives the programme output as a live stream. Test the loop point and the outgoing broadcast separately.
How do I stream a pre-recorded video on YouTube Live?
Load the video in OBS, configure the output and encoder for the source, and send the programme output to your YouTube stream. A local-file loop is one way to keep the same video repeating; it does not mean YouTube is replaying an uploaded video as a live broadcast.
What bitrate do I need for 4K YouTube Live?
It depends on frame rate and codec. YouTube’s published H.264 recommendations are 30 Mbps for 2160p30 and 35 Mbps for 2160p60; the AV1/H.265 guidance gives ranges for each. Check the current table and test that your connection can sustain the selected value.
Why is OBS dropping frames?
For network-dropped frames, OBS points to an unstable connection to the remote server or a bitrate the connection cannot sustain. Check the OBS counter, test wired networking if possible, and review YouTube stream health. If the network counter is clear but playback still stutters, investigate rendering or encoding performance separately.