To loop a video on YouTube Live from Ubuntu, add it to OBS as a looping Media Source, then send OBS’s 3840×2160, 60 fps output to YouTube. A playlist can use OBS’s VLC Video source instead, while a reliable live result still depends on your encoder, connection and checks during the broadcast.
This guide takes you from file preparation through a test stream and local recording. A loop setting repeats playback; it does not guarantee that OBS, Ubuntu or the YouTube stream will stay live indefinitely.
Prepare the video and YouTube stream
Start with the source material. If you have one video, check that it plays correctly from beginning to end and that its first and last frames and audio transition are suitable for repetition. OBS can repeat the file, but it cannot make a hard cut or abrupt audio change at the join feel seamless. Watch at least one complete cycle before using the file on air.
If you are choosing footage for an ambience channel, for example, review the source and its licensing terms before putting it into a public stream. A collection of options for rain and fireplace footage is discussed in this guide to free footage for a YouTube live loop. For an existing video, also consider whether its resolution and aspect ratio suit a 4K canvas. Upscaling a smaller file fills the canvas but does not restore detail that was never in the source.
Check that live streaming is enabled for your channel. YouTube’s eligibility requirements include a verified channel and no live-streaming restriction in the preceding 90 days; check the current YouTube live-streaming requirements rather than assuming a new channel is ready. In YouTube Studio, open the Live Control Room and create or select an encoder stream. Copy the stream key and server details needed by OBS.
Treat the stream key like a password. Anyone who obtains it may be able to send a feed to that stream, so do not include it in screenshots, public notes or a shared configuration file. If you suspect it has been exposed, replace it in YouTube Studio and update OBS with the new key.
For a scheduled event, allow time to prepare the encoder and preview the feed before viewers arrive. YouTube advises preparing at least two hours ahead and starting the encoder at least 15 minutes before the scheduled time. Use the YouTube Live Control Room guidance to check the incoming preview and stream health before making the broadcast public.
Add a looping Media Source in OBS on Ubuntu
Install OBS using the current OBS Project Linux installation instructions. Those instructions are the right place to check for your Ubuntu release; avoid relying on an old package command copied from a different version. OBS’s stated baseline requirements include an OpenGL 3.3-compatible GPU and an X window system or Wayland, but meeting those requirements only establishes that OBS can run. It does not establish that your system can render and encode 4K60.
Create a scene for the broadcast, then add a Media Source in the Sources panel. Choose the local video file and enable Loop in the source properties. Fit the source to the canvas if necessary, and check the result in the preview. Keep the source file in a stable local location: moving or renaming it later can break the source path.
The Media Source is the straightforward choice when your programme is a single file. It avoids creating and maintaining a separate playlist, and its Loop property tells OBS to replay that file. It does not promise a gapless join on every Ubuntu system or with every media file. Watch a full cycle and listen closely at the join, especially if the stream carries music or spoken content.
If you are building a long-running devotional or study channel, decide whether the broadcast is meant to repeat one continuous programme or a sequence of different files. A single-file loop is easier to inspect, but its repeated order can become noticeable. For more than one file, use the playlist route below rather than adding several overlapping sources and hoping their playback stays in order.
Use VLC Video when a playlist is needed
OBS’s VLC Video source is the alternative when you need a playlist. Add that source, create or select a playlist, and check the Loop Playlist option. OBS documents that this option is enabled by default. The source requires VLC libraries to be available, so install VLC on Ubuntu before configuring it and confirm the source appears in your OBS installation.
A playlist helps when a channel rotates several tracks or clips in a defined sequence. Before broadcasting, check each entry, its duration and its audio level. A missing file or an unexpectedly different aspect ratio can disrupt the presentation even when playlist looping itself is enabled. Test the whole sequence, not just the first item, and make sure the transition from the last item back to the first is acceptable.
Choose based on what you need to play, not on a general claim that one source is more reliable. For one file, Media Source has fewer moving parts. For a list of files, VLC Video gives you a playlist mechanism but adds a VLC dependency and more entries to inspect. Neither source setting guarantees uninterrupted availability of the stream.
If the content has different dimensions, check how each item fits the canvas. A landscape clip followed by a portrait clip may leave empty space or require a different crop. This overview of video aspect ratios in a 24/7 YouTube stream can help you plan the presentation before making a playlist.
Configure the 4K60 encoder output
In Settings → Video, set the base canvas and output resolution to 3840×2160 and set the common FPS value to 60. If your original file is lower resolution, OBS can scale it to the canvas, but the output dimensions should not be mistaken for native 4K detail. Check that the scene is composed as intended at the larger canvas size.
In Settings → Output, use Advanced mode if you need its encoder controls. Select an encoder that is actually available and stable in your installed OBS build and Ubuntu driver setup. OBS notes that hardware encoders can move some work from the CPU to a specialised component; availability depends on compatible hardware and software. OBS documents Intel Quick Sync support on Linux for compatible Intel HD Graphics hardware. Do not infer that a codec is supported just from a GPU brand or product label. Test the encoder you intend to use on the actual machine.
For 4K60, YouTube’s current encoder settings guidance gives different bitrate recommendations by ingest codec. The table below reflects its 2160p60 figures; use the codec OBS exposes and YouTube accepts for your chosen ingest setup.
| Ingest codec | YouTube-listed minimum | YouTube-recommended bitrate |
|---|---|---|
| AV1 | 10 Mbps | 35 Mbps |
| H.265/HEVC | 10 Mbps | 35 Mbps |
| H.264 | 14 Mbps | 50 Mbps |
These are YouTube’s recommendations, not a guarantee that your computer can encode at those settings or that a particular Ubuntu installation exposes each codec. For SDR, H.264 is a documented fallback when it is the stable option available to you, though YouTube’s recommended bitrate is higher than for AV1 or HEVC. Compare the encoder options in OBS with the current YouTube encoder settings and bitrate table.
Use CBR rate control and a two-second keyframe interval; YouTube says not to exceed four seconds. Its guidance supports up to 60 fps and lists AAC or MP3 audio. For stereo audio, the guidance recommends 128 kbps and a 44.1 kHz sample rate. For SDR video, use progressive scan, square pixels and Rec. 709 with 8-bit colour. YouTube optimises 4K streams for normal latency; the low-latency optimisation option is unavailable at 4K.
The outbound bitrate is only part of the connection requirement. YouTube recommends 20% upload bandwidth headroom over the total outgoing stream bitrate. Applying that margin to the recommended 50 Mbps H.264 setting means planning for at least 60 Mbps of available upload; for the 35 Mbps AV1 or HEVC recommendation, the arithmetic gives 42 Mbps. Those totals apply the headroom guidance; they are not separate YouTube bitrate recommendations. Check upload capacity on the same connection and at the same location you will use for the stream, allowing for other devices and uploads sharing it.
Connect OBS and test the stream
Choose YouTube RTMPS in OBS where it is offered, or enter the server and stream key from Live Control Room. YouTube recommends RTMPS, an encrypted extension of RTMP. Confirm that the selected ingest protocol works with the codec you chose, then start OBS and wait for YouTube to detect the incoming feed.
Use the Live Control Room preview before going public. Look for stream-health warnings and confirm the picture, sound and timing. A local OBS preview only shows what OBS is rendering; YouTube’s preview and health indicators show what is reaching the platform. If YouTube reports a connection problem, check the output bitrate, available upload capacity and competing network use before changing several encoder settings at once.
Run a representative test, including motion, audio and a complete loop or playlist cycle. Watch OBS’s rendering and encoding lag indicators, then compare the result with YouTube’s stream health. A static image may not reveal an encoder problem that appears during fast movement. Likewise, a short test cannot establish that a machine will keep up over an extended run. Rehearse long enough to observe the intended content and the transitions that matter to your channel.
You can find a more focused discussion of YouTube bitrate settings for Indian music streaming when comparing the outgoing feed with a music-led channel’s needs. For this setup, keep the decision tied to the actual codec, available upload and scene load rather than copying a bitrate from a different resolution or frame rate.
Record locally and plan the archive
If you may need a copy of the broadcast, configure OBS local recording and check where the file will be saved before the live run. Confirm that the target disk has room, that the recording format is usable in your editing or recovery workflow, and that the file grows during a test. A separate local recording gives you a copy under your control, but it also uses disk space and adds work for the machine that is already rendering and encoding the live output.
YouTube can automatically archive streams shorter than 12 hours, including 1440p and 2160p streams. It warns that a stream exceeding 12 hours may not be captured at all. Check the current YouTube archive live streams guidance for the applicable details. If a complete archive matters, do not rely on the platform copy alone for a longer broadcast.
A practical approach is to record locally, verify that the output file is growing, and plan a controlled stop and restart if you need YouTube to create separate archives. A planned restart creates a break in the live broadcast, so it is a trade-off rather than a way to preserve one continuous stream. Keep a note of the recording location and check the resulting file after the test; a recording indicator by itself does not prove the archive is readable.
Plan for extended runtime and recovery
A video source can repeat while OBS is running, but the broader setup includes the Ubuntu machine, display or session state, encoder, network and YouTube ingest. Any of these can fail or change. Do not describe a local loop as an indefinite broadcast guarantee. If your plan is to leave a computer running overnight, test the actual Ubuntu configuration and consider power use, cooling, updates, network interruptions and who will respond if the feed stops.
Write down a recovery sequence before starting: check whether OBS is still open, whether the source is moving, whether the encoder is reporting lag, and whether YouTube has an incoming signal. Then decide who can safely restart the broadcast and how they will confirm the preview returns. Avoid unattended changes to system updates, power-saving settings or drivers just before a scheduled stream. Make changes in a rehearsal and keep a known-working scene and source configuration available.
If keeping a local computer available is not practical, compare operating arrangements rather than assuming one fits every channel. This guide to alternatives to keeping a computer on for a 24/7 stream in India considers that decision from the operating side. StreamNeo removes the need to leave your Ubuntu computer on by turning an uploaded file into a YouTube live stream, which can be useful when the specific pain is maintaining the local machine; it remains YouTube-only and does not remove the need to check content, channel readiness and the result.
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 Media Source loop a video on Ubuntu?
Yes. Add a Media Source, select the local file and enable Loop in its properties. Test the transition from the file’s end back to its beginning; the setting repeats playback but does not guarantee a seamless join or a continuously available stream.
Do I need VLC to loop a single video?
No. A single file can use OBS Media Source. VLC Video is useful when you need a playlist, and OBS documents that VLC must be installed for that source to work.
What bitrate should I use for YouTube 4K60?
YouTube’s current guidance recommends 35 Mbps for AV1 or HEVC and 50 Mbps for H.264 at 2160p60. Choose only a codec your OBS installation exposes and YouTube accepts, and provide the recommended upload headroom rather than treating the bitrate as the whole connection requirement.
Will YouTube archive a 4K60 stream longer than 12 hours?
It may not: YouTube warns that streams exceeding 12 hours may not be captured at all. If you need a dependable copy, record locally, confirm the file is growing and plan any required stop and restart with the interruption in mind.