To start an already-working FFmpeg YouTube stream at boot, run it as a systemd service, enable that service, and configure it to wait for the network and restart if FFmpeg exits. Then verify the picture in YouTube Studio: a running service only confirms that a local process is active, not that YouTube is receiving a healthy stream.
Before you begin
This walkthrough assumes your FFmpeg command already works when you run it manually and that you have a YouTube stream key. It moves that command into a service; it does not create a YouTube broadcast or configure the video and audio settings for you. Keep your working command intact while setting this up so you can compare its output if the service fails.
- Know the full path to the FFmpeg executable, typically found with
command -v ffmpeg. - Know which Linux user can access the input files or devices your command needs.
- Have the complete FFmpeg arguments that work manually, including the input and YouTube ingest destination.
- Choose a protected location for the stream key. Do not put it in a script that others can read or directly in a command you may leave in shell history.
Service examples for Raspberry Pi commonly use network-online.target and enable the unit with systemctl; those are useful patterns, not proof that DNS, routing, or YouTube ingest is available. See the systemd service example and Raspberry Pi loop guide.
1. Store the stream key in a restricted file
Create a root-owned environment file readable by the service group. This example uses /etc/ffmpeg-youtube.env; use a different path if it better suits your system:
#1 Best Overall
- Includes Raspberry Pi 5 with 2.4Ghz 64-bit quad-core CPU (8GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
sudo install -o root -g root -m 600 /dev/null /etc/ffmpeg-youtube.env
sudo nano /etc/ffmpeg-youtube.envEnter the key as a variable, without surrounding shell commands:
YOUTUBE_STREAM_KEY=replace_with_your_stream_keySave the file. The 600 permission allows only root to read and write it. If your service runs as a dedicated, non-root user, arrange group ownership and permissions deliberately so that user can read the file without making the key broadly accessible. Do not commit the file to a public repository.
2. Create a systemd unit for FFmpeg
Create a service file such as /etc/systemd/system/ffmpeg-youtube.service:
sudo nano /etc/systemd/system/ffmpeg-youtube.serviceUse this as a template, replacing the username, paths, input and FFmpeg arguments to match your working setup:
Rank #2
- Includes Raspberry Pi 5 16GB with 2.4Ghz 64-bit quad-core CPU (16GB RAM)
- Includes 128GB Micro SD Card pre-loaded with 64-bit Raspberry Pi OS, USB MicroSD Card Reader
- CanaKit Turbine Black Case for the Raspberry Pi 5
- CanaKit Low Noise Bearing System Fan
- Mega Heat Sink - Black Anodized
[Unit]
Description=FFmpeg YouTube stream
Wants=network-online.target
After=network-online.target
[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi
EnvironmentFile=/etc/ffmpeg-youtube.env
ExecStart=/usr/bin/ffmpeg -re -i /home/pi/video.mp4 -c:v copy -c:a copy -f flv "rtmp://a.rtmp.youtube.com/live2/${YOUTUBE_STREAM_KEY}"
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.targetAdjust the command and service user
- Set
User=to the Linux account that should run FFmpeg. A non-root account is preferable; it must be able to read the input and access any required device. - Use the real absolute path to FFmpeg in
ExecStart=. A wrong executable path or an inaccessible wrapper script can produce an execution error. - Set
WorkingDirectory=to a directory that exists and is appropriate for the service. Use absolute paths for media and scripts rather than relying on shell-relative paths. - Replace the sample input, codec options and destination with the arguments from your command that already works. The line above is only an illustration, not a universal FFmpeg command.
- Keep the stream key variable in the protected environment file. systemd does not run
ExecStartthrough a shell by default, so do not assume shell syntax such as pipes, redirects, or command substitution will work there. If your command depends on shell features, use a carefully written executable wrapper and restrict its permissions.
Understand network ordering and restart behavior
Wants=network-online.target requests the network-online target, and After=network-online.target orders the service after it. These settings do not test whether DNS works, a route exists, or the YouTube ingest server accepts a connection. A service can still start too early for a particular input device or fail later when the connection is interrupted.
Restart=always asks systemd to start the process again after it exits, with the delay set by RestartSec=10. Choose a policy that suits your command and failure handling. Automatic restart can help after FFmpeg exits, but it cannot correct a bad stream key, unavailable input, invalid command, or a process that remains running while stuck. A restart policy alone is not a universal YouTube reconnection mechanism.
3. Load the unit and start it
After saving the unit, tell systemd to reload its configuration, then enable and start the service:
sudo systemctl daemon-reload
sudo systemctl enable --now ffmpeg-youtube.serviceenable arranges for systemd to start the unit at boot; --now starts it immediately as well. If this is a complex or new setup, validate the configuration, input, and YouTube output before relying on boot automation. A public GitHub project illustrates a more cautious validation-first approach for setups involving OAuth and additional configuration: YouTube-AutoEncoder.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- CanaKit Raspberry Pi 5 Essentials Starter Kit
4. Check the service and YouTube separately
Inspect systemd status and logs
Check whether systemd considers the process active:
sudo systemctl status ffmpeg-youtube.serviceFollow the service journal while it runs to see FFmpeg output and errors:
sudo journalctl -u ffmpeg-youtube.service -fIf you edit the unit later, run sudo systemctl daemon-reload again. After changing the environment file, restart the service so FFmpeg receives the updated key.
Confirm the actual live picture
Open YouTube Studio and check the scheduled or active broadcast’s preview and stream health. Confirm that the expected video and audio arrive; a service showing active (running) only tells you that its process is running. It does not prove that FFmpeg has valid input, that the key is correct, or that YouTube has a usable picture.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #4
- All-in-One Complete Kit: This SANOOV RPi 5 bundle comes with Raspberry Pi 5 4GB RAM single board, active cooler, durable ABS case and screwdriver. No extra parts needed, ready to use right out of the box for beginners and hobbyists
- Powerful Single Board Computer: Equipped with 4GB RAM and high-performance processor, delivers fast running speed for 4K playback, AI projects, programming and daily computing tasks. SANOOV for raspberry pi 5 4GB is equipped with broadcom 64 quad-core Arm Cortex A76 processor with gigabit ethernet and upgraded with IEEE 802.11ac Wi-Fi, Bluetooth 5.0 dual-band 2.4Ghz and 5Ghz and Power Over Ethernet (POE). Upgrading delivers 2-3 x speed vs Pi 4, redefining the experience
- Efficient Active Cooler: Effectively lowers operating temperature and prevents performance throttling. Runs quietly even under long-time heavy load, ensures stable operation all day long. SANOOV RPi 5 4GB kit offer an active cooler, which combines an aluminium heatsink with a high-performance PWM fan. Active cooler is fully compatible with the Pi OS, which can effectively reduce the temperature of RPi5 and ensure its good performance during long-term high load operation
- Sturdy ABS Protective Case: Well-fitted for Raspberry Pi 5 board, can be secured with 4 screws to effectively protect the Pi 5 motherboard from damage, reserves full access to all ports and buttons. SANOOV uses ABS material to produce the case, which has a softer texture and feel. Meanwhile, SANOOV case adopts a layered design for easy disassembly and installation. (Tip: The Case cannot install M.2 HAT Add on Board and Solid State Drive!)
- Wide Application & Full Compatibility: Seamlessly compatible with official OS and mainstream peripheral accessories for Raspberry Pi 5. Whether you are a beginner, student, electronics hobbyist or professional developer, this all-in-one kit meets your diverse needs. It excels in IoT projects, robotics design, retro gaming devices, home media servers and other DIY creations. Backed by a large global community, you can easily find guides, technical support and shared projects online
5. Test the reboot behavior
Once the stream works while started by systemd, reboot the Raspberry Pi at a time when interrupting the stream is acceptable:
sudo rebootAfter the Pi returns, check sudo systemctl status ffmpeg-youtube.service, inspect the journal with sudo journalctl -u ffmpeg-youtube.service -f, and verify the broadcast preview in YouTube Studio. This confirms both that systemd launched the process after boot and that the stream reached YouTube.
Troubleshooting common failures
systemd reports “203/EXEC” or cannot execute FFmpeg
Check that ExecStart= contains the correct absolute binary path and that the binary exists. If it points to a wrapper script, verify that the script exists, is executable, and has a valid interpreter line. A Raspberry Pi forum thread documents this class of startup-script execution error: Startup script fails with (code=exited, status=203/EXEC).
The service exits repeatedly
Use systemctl status and the journal to find FFmpeg’s error. Check unit syntax, the command copied into ExecStart=, the working directory, input path, permissions for the service user, and access to the environment file. If the input is a camera or other device, make sure it is ready when the service starts; boot ordering for the network does not guarantee device readiness.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 【What you Get】You will get 1*Pi 5 8GB Single Board,1*RasTech Case,1*Active Cooler,1*Screwdriver,1*Installation instructions,12-month free warranty, lifetime service, 24-hour prompt and friendly response.
- 【More Connectors】There are two USB 3.0 ports(5Gbps simultaneously) and two USB 2.0 ports, which triple total bandwidth ,support any combination of up to two cameras or displays. Peak SD card performance is doubled through support for the SDR104 high-speed mode. It provides a smooth desktop experience for you. Offer Gigabit Ethernet and a PCIe interface, along with dual-band Wi-Fi and Bluetooth 5.0/BLE wireless capability. The RasTech Pi 5 Kit use the new 27W 5.1V 5A USB-C power connector.
- 【 Support Dual 4Kp60 Display 】Each of the two microHDMI sockets can control a 4K display at 60 Hertz, now support HDR, offering super HD video for media streaming projects. RPi 5 is the first RPi model that comes with a PCI Express port (PCIe 2.0 x1 with 500 MB/s) to attach SSDs (requires separate M.2 HAT).
- 【 Excellent Chips And Applications】Pi 5 is a full-size Pi computer using silicon built in-house at Pi. The RP1 “southbridge” provides the bulk of the I/O capabilities for Pi 5. Pi 5 is more friendly and convenient in the development of Internet of Things, Web development, machine identification, automatic control and other electronic equipment applications and network.
- 【 Faster CPU, Better GPU 】 Pi 5 features a Broadcom BCM2712 64-bit quad-core Arm Cortex-A76 processor running at 2.4GHz, it delivers a 2–3× increase in CPU performance relative to RaspberryPi 4. The 800MHz VideoCore VII GPU is compatible to OpenGL ES 3.1 and Vulkan 1.2, substantial uplift in graphics performance. Pi 5 Offers lightning-fast CPU speed, a PCI Express interface, a Real Time Clock (RTC) and a power button and runs significantly cooler than Pi 4.
The service is active but YouTube shows no picture
Review FFmpeg’s journal output and check the stream key, destination, input and YouTube Studio preview. The process may be alive despite a broken or stalled input or an unsuccessful ingest connection. A Raspberry Pi forum camera case describes a fault that persisted through reboot and required attention to the camera-side stream condition, rather than systemd alone: How to gently terminate ffmpeg when called from a service?
FFmpeg does not recover from a network interruption
Systemd restart directives act when the FFmpeg process exits. If FFmpeg remains alive but cannot deliver a usable stream, systemd may have nothing to restart. FFmpeg’s documented reconnection options address particular HTTP protocol behavior; they should not be treated as a universal RTMP or YouTube recovery switch. See the FFmpeg protocols documentation and diagnose the actual transport and failure rather than adding unrelated flags.
Or let it run in the cloud
If you do not want to keep and maintain a Raspberry Pi at home, StreamNeo runs uploaded videos as a 24/7 YouTube stream from the cloud. Upload a recording or build a playlist, add your YouTube stream key, and go live. Nothing at home has to stay on; StreamNeo automatically recovers if YouTube drops the stream. Videos stream as uploaded, up to 4K 60fps, at one flat price per slot rather than quality tiers. The first day is free with no card. Monthly service is $9.99 per month. See StreamNeo or start the 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.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
