The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →You can run a prerecorded or otherwise prepared feed continuously on YouTube Live by running FFmpeg on a Hetzner Cloud server and sending its output to the ingest URL and stream key shown in YouTube Live Control Room. The right server depends mainly on whether FFmpeg can copy an already compatible stream or must encode it in real time. A VPS does not guarantee an uninterrupted broadcast: test the full setup, supervise FFmpeg, monitor YouTube’s stream health, and plan for recovery.
How the setup works
The VPS runs FFmpeg; YouTube receives the stream. Your source might be a looping video, a playlist, a camera or remote feed, or generated content. Each has different input and looping requirements, so there is no single FFmpeg command that safely fits every source. You need a Hetzner server with outbound network access, a working FFmpeg build, and a YouTube Live stream’s current URL and key.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →YouTube’s encoder workflow uses both the stream URL and stream key. Treat the key like a password: do not publish it in scripts, screenshots, shared shell history, or logs. If it is exposed, replace it in Live Control Room and update the server configuration.
Choose the workload and server
Decide whether to copy or re-encode
Stream-copying passes through compatible encoded audio and video without doing the video encoding work again. It can use far less CPU, but it does not let you change the copied stream’s codec, resolution, frame rate, or bitrate. Real-time transcoding can make those changes but consumes CPU continuously. Check the source’s codecs, resolution, frame rate, and audio format, then test the exact FFmpeg command you intend to run.
#1 Best Overall
There is no universal vCPU or RAM size established for this workload. Hetzner describes shared-resource and dedicated-resource Cloud Server classes, with dedicated CPU resources presented for CPU-intensive workloads. Compare the current options for your location and benchmark your actual input and output settings; do not choose based on a generic “1080p VPS” rule.
Check network and traffic terms
Hetzner’s traffic documentation lists 20 TB of included traffic for EU CX, CPX, and CAX Cloud Servers, but allowances differ for US and Singapore locations and may depend on the product. Check the current allowance and overage terms for the exact plan and location before purchasing. Hetzner’s billing FAQ says outgoing traffic is billed; excess included traffic is charged in 100 MB blocks. Its 75% and 100% notices are warnings, not automatic caps.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows 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 reinstallFor scale, YouTube’s recommended H.264 video bitrate for 1080p at 30 fps is 14 Mbps. At a constant 14 Mbps, 30 days of video data is approximately 4.54 decimal TB, calculated as bitrate multiplied by 2,592,000 seconds and divided by eight. This estimate excludes audio and protocol overhead, and is not a Hetzner usage figure or price quote. Other outbound server traffic also counts under the applicable plan terms.
Set YouTube’s ingest settings
Create or open the live stream in YouTube Live Control Room and copy its current ingest URL and stream key. Follow the settings shown for that stream if they differ from general recommendations. YouTube recommends RTMPS, the encrypted extension to RTMP. Its encoder guidance recommends CBR and a two-second keyframe interval, with four seconds as the maximum. Confirm that the installed FFmpeg build supports the input, codecs, and RTMP-family output protocol you need.
| YouTube H.264 mode | Recommended video bitrate | Minimum video bitrate |
|---|---|---|
| 1080p at 30 fps | 14 Mbps | 5 Mbps |
| 720p at 30 fps | 8 Mbps | 3 Mbps |
These figures are from YouTube’s encoder settings guidance accessed in 2026 and refer specifically to its H.264 column, not the AV1 or H.265 columns. They are video bitrates; include audio and transport overhead when planning total upload bandwidth.
Provision and prepare the Hetzner server
- Create a Cloud Server: In Hetzner Cloud, choose an operating system, location, and server class suited to your tested workload. Ensure it has public networking to reach YouTube. Public IP selection is a separate consideration in Hetzner’s documentation; verify current plan pricing and any IP charges before creating the server.
- Install FFmpeg: Use the package or build appropriate for your operating system, then check the installed binary and version. Confirm that it includes the input demuxer, media codecs, and RTMP-family protocol support your source and output require. FFmpeg options and availability vary by version and build.
- Prepare credentials securely: Put the URL and key in a restricted configuration or environment file rather than embedding the key in a public script. Restrict file access to the account that runs FFmpeg and avoid printing credentials in diagnostic output.
- Build input-specific output: Choose the correct input and looping method for your media and installed FFmpeg version. Match YouTube’s current output requirements, including protocol, bitrate mode, and keyframe interval. Do not assume a loop option for a local file will also work for a playlist, live input, or generated scene.
Test the stream before leaving it running
Start with a representative source that includes the audio and motion you expect in production. YouTube recommends testing the encoder and checking stream health, messages, and outbound bandwidth. Watch the Live Control Room preview and verify both picture and sound before treating the service as deployed. A process that starts successfully is not proof that YouTube is receiving a healthy broadcast.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Confirm the stream appears in Live Control Room and its preview plays.
- Check for encoder or ingest warnings and verify the output resolution, frame rate, and audio.
- Measure the server’s actual outbound rate and compare it with your planned bitrate plus audio and overhead.
- Stop and restart FFmpeg deliberately so you know how YouTube and your supervision setup behave after a disconnect.
Keep FFmpeg running and recover from failures
A terminal session or a shell command by itself is not a recovery plan. Run FFmpeg under a process supervisor configured to start it at boot, restart it after an unexpected exit, and retain useful logs. Add monitoring or notifications for a stopped process and for YouTube reporting an unhealthy stream. Test the restart path while you can observe the result.
FFmpeg protocol reconnect options, where supported by the installed version and relevant protocol, do not replace supervision of the whole process. Nor can a process restart fix every YouTube-side or network problem. Keep a documented procedure for checking logs, confirming the current stream key, and restarting or replacing credentials if compromised.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Understand continuity, availability, and archiving
Hetzner’s Cloud and vServer service agreement, in the version accessed in 2026, describes a commercially reasonable effort toward 99.9% monthly availability for an individual Cloud Server. This is not a guarantee that your FFmpeg process or YouTube broadcast will stay live: application crashes, ingest disconnects, maintenance, and YouTube-side issues can interrupt it.
Recommended Free Tools
YouTube says streams under 12 hours are automatically archived. Do not rely on a single automatically archived video for a continuous 24/7 broadcast. If you need a complete archive, arrange separate recording or segmentation and verify YouTube’s current archive behavior for your stream.
Troubleshooting common failures
YouTube does not receive the stream
- Check the URL and key: Copy the current values from Live Control Room; confirm they were not truncated or swapped. Rotate a key that may have been exposed.
- Check protocol support: Verify the FFmpeg binary supports the output protocol and try the RTMPS ingest settings YouTube recommends if your build supports them.
- Check connectivity: Confirm the server can reach the ingest endpoint and that outbound traffic is not blocked by local firewall rules or another network restriction.
The stream starts, then stops or repeatedly disconnects
- Inspect both sides: Review FFmpeg logs and YouTube Live Control Room messages to distinguish process exits from ingest or YouTube issues.
- Check capacity: For a transcode, inspect CPU use and whether the output can sustain real time. For either approach, verify outbound bandwidth is stable at the configured rate.
- Verify supervision: Confirm the service manager detects a failed process and restarts it, and that alerts identify an outage rather than silently looping restarts.
Video or audio is missing, stuttering, or rejected
- Validate the source: Confirm FFmpeg can read the file or feed, and that the chosen codecs and stream-copy approach are compatible with the intended output.
- Recheck encoder settings: Match the current YouTube stream settings for codec, bitrate, frame rate, and keyframe interval. A copied stream cannot be altered without encoding.
- Test audio explicitly: Use a source with known audio and confirm the Live Control Room preview includes it; check the selected audio stream and output mapping.
Or let it run in the cloud
If you want an always-on YouTube stream without administering a VPS and FFmpeg, StreamNeo runs uploaded videos from the cloud: upload a recording or build a playlist, add your YouTube stream key once, and go live. Nothing has to stay powered on at home. Uploaded video streams as made, up to 4K 60fps, at one flat price per slot; the service automatically recovers if YouTube drops the stream. The first day is free with no card. Monthly billing is $9.99 per month. StreamNeo is for YouTube streams from uploaded videos, not camera-based live capture. Start the free first 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.
