To loop a prerecorded video on YouTube Live from Linux, install OBS using a route supported for your distribution, add the file as a Media Source, and enable Loop. That setting repeats the media; it does not keep your computer powered, your internet connected or YouTube ingesting the broadcast.
For a playlist, use OBS’s VLC Video source and install a compatible VLC build first. Before planning a long broadcast, test the actual file, encoder settings and connection, and decide how you will keep a recording if the YouTube archive matters.
Install OBS using a route for your distribution
OBS Project documents Flatpak and Ubuntu installation routes for Linux, and recommends Flatpak for distributions other than Ubuntu. Choose the route that fits your distribution rather than mixing package sources in the hope of fixing a problem later. The OBS installation instructions list the supported Linux approaches.
On Ubuntu, use the documented Ubuntu route. On another distribution, Flatpak is the documented general recommendation. If you already have OBS installed, check that it opens and that its version is compatible with the plugins or source types you plan to use. A basic prerecorded stream does not require a paid utility or a camera.
There is a practical trade-off: the package route affects how OBS is installed and updated, but it does not remove the need to test media playback, encoding and network performance on your own machine. Keep the installation straightforward. Once OBS launches, create a new profile or use a clean one so the output settings you test are easy to identify.
Create a scene and add a local Media Source
A scene is the canvas OBS sends to the stream. For a single prerecorded video, make a simple scene and add a Media Source pointing to the local file. OBS’s Media Sources guide describes the source types and their settings.
In OBS, use the Sources panel to add a Media Source, give it a recognisable name, and select the local video file. Keep the file in a location that stays available while you stream; a removable drive that gets unplugged, a renamed folder, or a file moved after setup can leave the source unable to play. OBS accepts common formats such as MP4, TS, MOV, FLV, MKV, AVI, GIF and WebM, though a supported extension alone does not prove that every file will decode smoothly on your particular system.
Check what appears in the preview. If the video is the wrong shape for the canvas, decide whether you want to preserve the whole frame with empty space, crop the edges, or prepare a separate export. Cropping can remove titles or important detail near the edge, so inspect the actual picture rather than assuming a full-screen fill is always right. Add an audio source only if the video does not already contain the sound you need, and verify that the meters move during playback.
Use a scene name that will still make sense when you return to OBS after a restart, such as “Night playlist” or “Local news loop”. A clear name matters more when a profile has multiple scenes or when you are troubleshooting a stream after hours. For a no-camera news loop, a still image, ticker or prepared video can be arranged in OBS without a studio camera; see this guide to streaming a local news radio station without a studio camera.
Enable Loop for one video
Open the Media Source properties and enable Loop. When the file reaches its end, OBS starts it again. Check the preview at the point where the file ends: a hard cut, a black frame or a pause is part of the media and will recur each time the loop restarts.
Looping solves one specific job: repeating the file while OBS is running and the source can still read it. It does not restart OBS if the application closes, recover a machine that loses power, repair a network interruption, or confirm YouTube is receiving the broadcast. Treat media playback and broadcast continuity as separate checks.
For a devotional channel, for example, the source might be a prepared bhajan video with an intentional opening and ending. If the end contains several seconds of silence, viewers will hear it on every pass. Preview the transition, including audio, before you use the file live. If a transition is distracting, edit the file or make a playlist of separate pieces rather than expecting the Loop checkbox to smooth it out.
If viewers need an ordered rotation of clips rather than one repeated video, do not force a single-file loop to serve as a schedule. A rotating schedule for a YouTube music livestream in India is a different planning problem: decide the order and timing of the material before choosing whether one file or a playlist is easier to maintain.
Use VLC Video for a playlist
OBS’s VLC Video source is intended for a list of media items. VLC must be installed before this source type appears, and OBS documentation notes that 64-bit OBS requires 64-bit VLC. Add VLC Video, select the files in the order you want, and inspect the playlist in the preview before going live.
Loop Playlist is on by default and Shuffle Playlist is off by default, according to the OBS Media Sources documentation. Confirm both settings rather than relying on defaults, particularly if the sequence matters. With shuffle disabled, the list plays in its given order; with it enabled, the order changes. A playlist suits a station that wants several clips to cycle, while a single Media Source is simpler when one finished programme should repeat unchanged.
| Need | Source choice | What to check |
|---|---|---|
| Repeat one finished video | Media Source | Loop enabled; end transition and audio checked |
| Cycle through an ordered set | VLC Video | VLC installed and compatible; playlist order correct; shuffle off |
| Vary the order | VLC Video | Shuffle enabled only if changing sequence is intended |
A playlist adds another dependency: every referenced file must remain available at the location OBS expects. Keep the media together in a stable folder, use clear filenames and test the list from its first item through a transition. If you update clips, re-open the playlist and confirm that it still points to the right files. A looped playlist can repeat content, but it still depends on OBS remaining active and the broadcast continuing to reach YouTube.
Set output and YouTube ingest separately
In YouTube Live, create or select the live stream and use the stream key and connection details YouTube provides. In OBS, configure the stream service for YouTube RTMPS, or enter the supplied RTMPS endpoint and key as directed in the interface. YouTube recommends RTMPS; its RTMPS ingestion documentation describes the secure protocol and endpoint requirements. Treat the key as a password: do not show it in a screenshot or share it in a public support post. If a key is exposed or stops working, follow the channel’s account and stream-key checks rather than repeatedly pasting it into unrelated configurations; this stream-key recovery guide covers that separate issue.
For output, YouTube’s current encoder guidance covers RTMP or RTMPS, H.264, H.265/HEVC or AV1 video, AAC or MP3 audio, constant bitrate (CBR), and up to 60 frames per second. YouTube recommends a two-second keyframe interval and says not to exceed four seconds. Use the codec and settings your OBS build and hardware can sustain; a listed option does not guarantee that a particular processor can encode it without dropped frames.
Choose bitrate with resolution, frame rate and sustained upload capacity in view. YouTube’s H.264 recommendations give 5 Mbps for 1080p30, 3 Mbps for 720p30 and 8 Mbps for 720p60; the publication year is not stated on the referenced guidance. These are YouTube recommendations, not a promise that your connection will sustain them. A smaller 720p30 output can be the more practical starting point than a higher-resolution stream if your upload connection varies or the computer is already busy.
YouTube also recommends 128 Kbps stereo audio and 44.1 kHz stereo sampling in its advanced settings. Match OBS settings to the intended picture and sound, then compare them against YouTube’s live encoder settings guidance. Avoid changing several variables at once during diagnosis: if a test fails, you want to know whether the cause is the file, encoding load, network or ingest configuration.
Check power, network and YouTube ingestion separately
A nonstop plan has several independent parts. The local file can loop correctly while the computer sleeps, the router loses its connection, OBS stops encoding, or YouTube reports an ingest problem. Make separate checks instead of treating the source preview as proof that the broadcast is healthy.
Power and computer: Set the Linux desktop not to suspend or sleep during the intended run, and check any laptop lid or power-saving behaviour that could interrupt it. Keep the machine ventilated and avoid scheduling system updates or a reboot during a planned test. Those settings reduce avoidable interruptions but cannot guarantee power or prevent hardware faults. If the stream ends when the display turns off, distinguish display blanking from system sleep; only the latter should stop the running application.
Network: Use the connection you intend to rely on, ideally wired if that is practical, and observe whether the upload remains steady while the test runs. Other users uploading large files, a weak wireless signal, or an ISP interruption can affect the outgoing stream. A connection test taken at a quiet hour is not proof of overnight performance. If you have seen evening buffering on your provider, compare the result during the hours when you expect the channel to run; this Airtel evening-buffering troubleshooting guide explains why timing matters.
YouTube ingestion: Confirm that OBS connects to the intended live event and that YouTube’s live control room reports a signal. The RTMPS endpoint, stream key and event state are different from the file’s loop setting. If OBS says it is sending but YouTube does not show the expected preview or health information, check the stream details and current official guidance rather than assuming the video will appear later.
Archive: Do not treat an indefinitely long YouTube stream as a guaranteed recording. YouTube warns that streams exceeding 12 hours may not be captured at all; streams under 12 hours are automatically archived according to its archive help page. YouTube also says DVR rewind may be limited or unavailable on streams longer than 12 hours. If the recording matters, plan periodic stream endings under that threshold and keep a local recording as a backup. A local recording uses disk space and adds work, but gives you a copy that does not depend on the live archive being available.
Rights and monetisation are separate from technical success. Confirm that you have the rights needed for the video and music in both the live transmission and any resulting archive. YouTube’s monetisation policies also apply to live streams; repetitive or mass-produced material may not qualify, so a technically functioning loop is not a promise of monetisation. Check the current YouTube monetisation policy and live-streaming terms before relying on assumptions about a particular format.
Run a short test before the full broadcast
OBS recommends testing settings and stream performance ahead of the first live stream. Use the actual file or playlist, the intended output settings and the same network you expect to use. A short test is useful because it can expose a missing file, unsupported decode, silent audio, overloaded encoder, weak upload or incorrect stream key before you build a long schedule around the setup.
A practical test sequence is:
- Start OBS and confirm the scene preview shows the correct file, framing and audio.
- Start a private or otherwise appropriate test broadcast using the intended YouTube event and ingest settings. Verify in YouTube’s live control room that it receives a signal.
- Let the file reach its end, or let a playlist advance, so you see the repeat or next-item behaviour rather than testing only the opening seconds.
- Watch OBS’s status and YouTube’s health information for dropped frames, interruptions or warnings. Listen to the sound on the received preview if available.
- Stop cleanly, check whether the expected archive or local recording exists, and correct one issue at a time before repeating the test.
Do not use a short test to claim that a multi-day run is proven. It checks that the parts can work together under those conditions; it cannot certify tomorrow’s power, internet route, machine temperature, YouTube ingest or archive. For a longer schedule, repeat the test at a representative time and decide who will notice and respond if the stream drops.
When the file and channel are ready, you can decide whether to leave your own computer responsible for the broadcast. StreamNeo removes the specific burden of keeping that computer switched on to send an uploaded video as a YouTube live stream, while the content, key and channel choices remain yours.
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 from Linux with OBS?
Install OBS using the route supported for your distribution, create a scene, add the local file as a Media Source and enable Loop in its properties. Configure YouTube RTMPS and OBS output separately, then test that YouTube receives the stream and the file restarts as expected.
Why does OBS show the video looping but the stream still stop?
The Loop setting only tells the media source what to do when playback reaches the end. It does not keep the computer awake, restore a failed internet connection, restart OBS after a crash or guarantee YouTube ingestion. Check those parts independently.
Can OBS loop a playlist instead of one file?
Yes. Use VLC Video, with VLC installed and matching OBS’s bitness; OBS documentation specifies 64-bit VLC for 64-bit OBS. Check playlist order, Loop Playlist and Shuffle Playlist before testing a transition.
Will YouTube archive an endless live stream?
Not reliably: YouTube warns that streams longer than 12 hours may not be captured, and DVR rewind may also be limited or unavailable. If the archive matters, plan shorter broadcast sessions and keep a local recording as backup, then check YouTube’s current help pages for the latest details.