You can keep a prerecorded playlist live on YouTube from an Ubuntu VPS by looping the files with FFmpeg, sending the output to YouTube Live over RTMPS, and using systemd to restart FFmpeg if it exits. A restart policy helps recover from a process failure; it cannot guarantee an uninterrupted stream, so monitor YouTube’s stream health and keep a separate recording if the archive matters.
What you need before you start
- An Ubuntu VPS with enough disk space for your media and enough CPU capacity if FFmpeg will encode or transcode it in real time.
- A sustained outbound connection with sufficient capacity and transfer allowance for your chosen stream settings. A provider’s advertised port speed alone does not establish sustained throughput.
- FFmpeg installed on the VPS and a playlist of video and audio you have the rights to broadcast.
- A YouTube channel with live streaming enabled, plus its stream URL and a private stream key from YouTube Studio.
An India-region VPS may reduce network distance for an operator or audience in India, but YouTube does not require one, and location alone does not guarantee better reliability. Compare sustained egress or transfer limits, CPU, storage, region, support, and restart and monitoring options. Treat claims such as “unthrottled” bandwidth or continuous FFmpeg loops as the provider’s claims; confirm the terms for the plan you intend to use.
As an Amazon Associate I earn from qualifying purchases.
Configure YouTube Live safely
Create the live stream
- In YouTube Studio, create or schedule a live stream and select the encoder workflow.
- Copy the server URL and stream key shown for that stream. YouTube recommends RTMPS, a secure extension to RTMP; use the RTMPS server address provided in the live control room.
- Keep the key secret. Treat it like a password: do not put it in a public repository, screenshots, or shared logs. If it is exposed, replace or reset it in YouTube Studio.
Check YouTube’s current live settings for supported resolution and bitrate rather than assuming a VPS plan supports a particular stream profile. YouTube’s encoder guidance lists H.264, H.265/HEVC, and AV1 video options, up to 60 fps, and recommends constant bitrate (CBR), a two-second keyframe interval, and no more than four seconds between keyframes. Choose settings the VPS can sustain; test upload bitrate and check stream health with representative motion and audio. YouTube transcodes the incoming feed for viewer formats.
Free tools Windows power users keep installed
One-click scans. No signup required.
Sources: YouTube Help: Choose live encoder settings, bitrates, and resolutions and Google’s RTMPS ingestion guide.
#1 Best Overall
Prepare a playlist and loop it with FFmpeg
Make a file list
Place the media on the VPS, for example under /srv/youtube/media/, and create a playlist file with one entry per file. FFmpeg’s concat demuxer expects entries in a specific format; a simple list for compatible files can look like this:
file '/srv/youtube/media/video-01.mp4'
file '/srv/youtube/media/video-02.mp4'Save it as /srv/youtube/playlist.txt. Use paths that the service account can read. This basic concat approach works best when files have compatible streams and parameters; mixed codecs, dimensions, frame rates, or audio formats may require normalization or a different playlist workflow. Validate the exact options against the installed FFmpeg version and your media before relying on the service.
Choose pass-through or real-time encoding
If the files already match the output format and settings accepted by YouTube, stream-copying can avoid the CPU cost and quality change of re-encoding. It is not a universal shortcut: incompatible inputs or parameters can cause playback or ingest problems. If you need to normalize the playlist, encode in real time and ensure the VPS CPU can keep pace.
An illustrative FFmpeg command for a compatible playlist using H.264/AAC inputs and stream-copy output is:
ffmpeg -re -stream_loop -1 -f concat -safe 0 -i /srv/youtube/playlist.txt
-c copy -f flv "YOUR_RTMPS_INGEST_URL/YOUR_STREAM_KEY"Replace the destination with the RTMPS URL and key from YouTube Studio. Do not save a command containing the real key in a shared shell history or logs. This is an implementation pattern, not a guarantee that every playlist is compatible. For transcoding, specify video and audio codecs and settings that match YouTube’s current guidance, and test before going live. The -re option reads media at approximately its playback rate; -stream_loop -1 repeats the input indefinitely.
Run FFmpeg under systemd
Use a dedicated, unprivileged service account and restrict access to any file containing the stream key. A systemd unit can restart FFmpeg after it exits. One pattern is to keep the destination in a root-readable environment file and reference it from the unit; protect that file with restrictive permissions. The example below assumes a script at /usr/local/bin/youtube-loop.sh that runs the tested FFmpeg command and reads its destination from a protected configuration.
[Unit]
Description=YouTube playlist stream
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
User=youtube-stream
ExecStart=/usr/local/bin/youtube-loop.sh
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target- Save the unit as
/etc/systemd/system/youtube-loop.service. - Ensure the script is executable and readable by the service account, and media paths are accessible.
- Reload systemd and start the service:
sudo systemctl daemon-reload, thensudo systemctl enable --now youtube-loop.service. - Check process status with
sudo systemctl status youtube-loop.serviceand inspect recent logs withsudo journalctl -u youtube-loop.service -n 100 --no-pager.
Restarting a process only addresses some failures. A live FFmpeg process can still be stalled, lose input, or stop sending advancing video or audio. Check YouTube’s stream-health indicators, not only systemd’s process status. A public FFmpeg/systemd example documents an intermittent input/decoder issue, another reason to monitor rather than assume the service is healthy.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallArchive, copyright, and monetization limits
Do not rely on a 24-hour YouTube replay
YouTube says streams under 12 hours can be automatically archived, while a stream exceeding 12 hours may not be captured at all. It recommends keeping a local archive backup. If a replay matters, record locally or create shorter broadcasts with a planned handoff; do not assume one continuous 24/7 broadcast will leave a complete replay.
Source: YouTube Help: Archive live streams.
Use content you have the rights to broadcast
Looping a file does not grant permission to use it. YouTube’s livestream terms require the provider to have the necessary rights for worldwide exploitation of the live content, including music licensing rights. Use original material or obtain permissions and licenses covering the intended live use and territory.
Source: YouTube Terms of Service.
Copyright permission does not guarantee monetization
YouTube’s monetization policies also apply to livestreams. Its July 15, 2025 update renamed “repetitious content” as “inauthentic content” and clarified that repetitive or mass-produced material is included. Reused-content review is separate from copyright enforcement: permission to use material does not by itself establish monetization eligibility. Eligible monetized livestreams may earn from ads, Super Chat or Super Stickers, and memberships, but ad slots are not guaranteed to serve.
Sources: YouTube channel monetization policies and YouTube Help: Monetize your live stream.
Troubleshoot a stream that stops or has no signal
- FFmpeg exits repeatedly: inspect the systemd journal for file paths, permissions, decoder errors, and invalid options. Confirm the service account can read every playlist entry and test the media outside the service.
- YouTube does not receive the stream: verify the RTMPS server address and stream key, confirm live streaming is enabled for the channel, and check that the VPS can make outbound connections to the ingest service.
- The process is active but YouTube reports a problem: confirm that video frames and audio are actually advancing at YouTube. A running process alone is not a stream-health check.
- Playback stutters or drops frames: reduce output demands to settings the VPS can sustain, check CPU use if encoding, and check sustained egress and transfer limits with the provider. Do not infer sustained performance from a headline port-speed figure.
- The loop breaks at a file boundary: check whether playlist files have compatible streams and parameters. Test the transition between each pair; normalize mismatched files or use an approach suited to the inputs.
- A past broadcast is missing or incomplete: a stream beyond 12 hours may not be captured. Use a local recording backup for material that must be retained.
- The stream is claimed or restricted: review YouTube’s notice and resolve rights or policy issues. Technical looping does not override copyright or monetization rules.
Or let it run in the cloud
If you do not want to maintain an Ubuntu server, StreamNeo is the first alternative to consider: it keeps uploaded videos live on YouTube from the cloud, at any uploaded quality up to 4K 60fps for one flat price per slot, with the first day free.
- Upload a recording or build a playlist.
- Add your YouTube stream key once.
- Go live; StreamNeo loops the uploaded video or playlist from its cloud service.
Your computer and home connection do not need to stay on, and StreamNeo automatically recovers if YouTube drops the stream. Every slot includes 10 GB storage, pooled across active slots, 24/7 looping and playlists, and support from the StreamNeo team. The same product is on every plan; only the billing length changes. The first day is free with no card, one free day per account. Monthly pricing is $9.99 per month. UPI and cards are accepted in India; card checkout is available worldwide. See StreamNeo or current plan details, then start your free day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
