To livestream with FFmpeg from an AWS VPS, start a Linux EC2 instance, install FFmpeg, copy the RTMPS ingest URL and stream key from YouTube Live Control Room, then run FFmpeg with settings that match YouTube’s encoder guidance. The VPS must sustain both the encoding workload and outbound stream. The example below loops a prerecorded video; it is a starting point, not a tested command or universal preset.
What you need before starting
- An AWS account and an internet-connected EC2 instance running Linux.
- A prerecorded video file on the instance, or a suitable live input source for FFmpeg.
- A YouTube channel with livestreaming enabled and a stream configured in Live Control Room.
- An RTMPS URL and stream key from that stream’s settings. Treat the key like a password.
This walkthrough uses a Debian- or Ubuntu-style image for installation. Package availability and codec support depend on the image and its configured repositories.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ZOERAX 100-Pack M6 x 16mm Rack Mount Cage Nuts, Screws and Washers | $23.99 | Buy on Amazon |
Prepare the AWS VPS
Choose capacity for encoding and network traffic
Do not select an EC2 instance based on video bitrate alone. Software encoding can use substantial CPU, depending on codec, resolution, frame rate, filters, and preset. Network capacity also varies by instance type; some advertised bandwidth is a baseline with burst behavior, not a promise of sustained throughput. Choose and monitor an instance that can handle the intended workload. AWS does not establish one instance size that suits every stream. AWS EC2 network bandwidth guidance
Check network access and secure administration
The instance needs outbound internet routing to reach YouTube’s ingest endpoint. Check the VPC route and security-group egress rules if it cannot connect. For administration, restrict SSH access to trusted source IP addresses rather than opening port 22 to everyone. This workflow does not require an inbound public video port on the VPS. AWS security groups
#1 Best Overall
- Wide Compatibility & Versatile Use: ZOERAX M6 rack mount screw kit is ideal for installing server racks, network cabinets, rack shelves, patch panels, A/V equipment, and more. Designed for standard square-hole racks and cabinets, these M6 cage nuts and screws ensure a secure fit for most 19-inch rack systems used in data centers, offices, and home labs
- Heavy-Duty Carbon Steel Construction: Made from premium carbon steel, these M6 cage nuts and screws deliver high strength and long-lasting durability. The material provides excellent resistance to rust, corrosion, and oxidation, performing reliably in demanding environments such as high humidity, temperature fluctuations, and long-term rack installations
- Precision Metric Standard M6: Manufactured to strict metric standards, each M6 screw and cage nut features precise dimensions with minimal tolerance. Clean, sharp threads without burrs allow smooth installation without stripping or slipping. The deep Phillips head design ensures better torque control and faster, more efficient mounting
- Safe, Reliable & Eco-Conscious Materials: ZOERAX uses non-toxic, environmentally friendly carbon steel materials to ensure safe handling and use. Heat-treated for optimal hardness, ductility, and impact resistance, these rack screws and cage nuts offer dependable performance while meeting safety and quality expectations for professional installations
- Complete Mounting Kit with Washers: This essential M6 rack hardware kit includes screws, cage nuts, and heavy-duty washers. The included washers help distribute pressure evenly and reduce scratches or marks on rack rails and equipment, providing a cleaner, more secure installation right out of the box
Install FFmpeg and get the YouTube ingest details
Install and check FFmpeg
- Connect to your Linux instance over SSH.
- On a Debian- or Ubuntu-style image, run
sudo apt update && sudo apt install ffmpeg. - Confirm the installed build and its available configuration with
ffmpeg -version. Package and codec availability can differ across images and repositories.
Copy the stream URL and key
- In YouTube Live Control Room, open the stream’s settings.
- Copy the stream URL and stream key. YouTube says the RTMPS URL can be revealed using the lock icon in the Stream URL field. YouTube: Set up your encoder for live streaming
- Use the RTMPS endpoint, not an unencrypted RTMP endpoint, when secure delivery is the goal. Google documents RTMPS ingestion on port 443 and notes that the hostname is needed for TLS/SNI authentication. Preserve the hostname and endpoint format provided for your stream. Google: YouTube ingestion protocols
Never publish the stream key in screenshots, source control, or logs. Avoid putting it in a broadly readable script or command history. For unattended use, retrieve it through a protected environment or an appropriate secret-management method. Process listings may also expose command-line secrets.
Run FFmpeg to loop a prerecorded video
Place the video on the VPS and replace the example values below. This illustrative command uses a modest 30 fps H.264 stream and loops the input. Its 4,500 Kbps video bitrate is not a YouTube universal recommendation: adjust bitrate, frame rate, and resolution to the actual source and YouTube’s current table.
VIDEO=/path/to/video.mp4
RTMPS_URL='rtmps://<server-from-live-control-room>:443/<app-or-path>'
STREAM_KEY='<secret-stream-key>'
ffmpeg -re -stream_loop -1 -i "$VIDEO"
-c:v libx264 -preset veryfast -pix_fmt yuv420p
-r 30 -g 60 -b:v 4500k -maxrate 4500k -bufsize 9000k
-c:a aac -b:a 128k -ar 44100 -ac 2
-f flv "$RTMPS_URL/$STREAM_KEY"The -re option reads the file in real time; -stream_loop -1 repeats it indefinitely. At 30 fps, -g 60 requests a 60-frame GOP, equivalent to a two-second keyframe interval. The example’s video settings are an illustrative baseline for 720p/30 or similar, not an official preset or a tested command.
Check how Live Control Room formats the endpoint before composing the final URL. If its provided endpoint path already incorporates the stream key, follow that format rather than blindly appending the key as shown in the example. For a live camera or another real-time source, replace the file input with the appropriate FFmpeg input and remove -re when the input is already arriving in real time. Input flags depend on the source and operating system.
Match YouTube’s encoder settings
YouTube recommends RTMPS, constant bitrate (CBR) encoding, and a two-second keyframe interval that does not exceed four seconds. Its RTMP/RTMPS guidance supports H.264, H.265/HEVC, and AV1 ingestion, with frame rates up to 60 fps. Select a bitrate from YouTube’s current table for your codec, resolution, and frame rate rather than treating a single value as universal. YouTube encoder settings, bitrates, and resolutions
| Setting | YouTube guidance | How to apply it |
|---|---|---|
| Transport | RTMPS recommended | Use the secure URL from Live Control Room and preserve its hostname. |
| Video rate control | Constant bitrate (CBR) recommended | Use matching target and maximum rates where appropriate; validate the result in stream health. |
| Keyframe interval | Two seconds recommended; no more than four seconds | At 30 fps, a GOP of 60 frames corresponds to two seconds. |
| H.264 video bitrate | 10 Mbps for 1080p at 30 fps; 17 Mbps for 1080p at 60 fps | These are YouTube’s listed recommendations; use its table for other combinations. |
| Stereo audio | AAC, 128 Kbps, 44.1 kHz | The example command sets these audio values. |
YouTube transcodes incoming streams into multiple output formats for viewers, but the VPS still needs a stable upload to the ingest endpoint. Run a preflight using material with motion and audio similar to the real program, then monitor stream health during the event. YouTube’s current help page, accessed in 2026, provides the guidance above; it does not state a publication year. YouTube live encoder guidance
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test the stream and check YouTube Live rules
Before a scheduled broadcast, run a representative test and inspect Live Control Room’s stream health. This can reveal problems that a successful FFmpeg connection alone does not: bitrate mismatch, unstable upload, or audio/video settings that do not suit the source.
A stream key and working encoder do not grant rights to the video or music you broadcast. Use material you own or are authorized to stream, and check YouTube’s applicable copyright and monetization policies. Repeated or reused material can raise separate monetization-policy questions; a technically valid 24/7 loop is not, by itself, evidence of permission or eligibility.
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 reinstallTroubleshoot common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| TLS or certificate error | Incorrect protocol, hostname, or port | Copy the RTMPS URL from Live Control Room, retain its hostname, and verify the endpoint uses port 443. Google ingestion protocol guidance |
| Connection timeout | No outbound route or egress is blocked | Check instance internet routing and security-group egress to the ingest service. AWS security groups |
| YouTube reports poor stream health | Encoder settings do not match the selected stream or the upload is unstable | Compare codec, bitrate, frame rate, keyframe interval, and audio settings with YouTube’s current recommendations; repeat a representative test. YouTube encoder guidance |
| Stream starts, then becomes unstable | CPU saturation or insufficient sustained network capacity | Monitor CPU load and actual network throughput. EC2 bandwidth depends on instance type and may include baseline and burst behavior. AWS network bandwidth guidance |
| Unexpected AWS bill | Instance runtime or outbound data transfer is higher than expected | Review compute runtime and transfer volume; estimate costs for the chosen region, instance type, duration, and traffic. AWS EC2 pricing |
Estimate the cost of leaving an AWS stream running
A continuous stream can incur EC2 compute charges and outbound data-transfer costs; storage may also contribute depending on how the instance and video are set up. Exact cost depends on AWS region, instance type, runtime, and transferred data. Check current pricing for the configuration you select before leaving it unattended. AWS identifies compute, storage, and outbound transfer as cost drivers. AWS pricing
Or let it run in the cloud
If your goal is a 24/7 YouTube loop rather than managing an EC2 instance and FFmpeg, StreamNeo is a cloud option: upload the recording or playlist, add your YouTube stream key, and go live. The cloud keeps the stream running without a computer or home connection staying on. It plays uploaded videos, not a live camera feed, and streams to YouTube.
- Each slot streams your upload as made, up to 4K 60fps, at one flat price per slot with no re-encode or quality tiers.
- It automatically recovers if YouTube drops the stream.
- The first day is free with no card, one free day per account.
- Each slot includes 10 GB of storage, pooled across active slots, plus 24/7 looping, playlists, and StreamNeo team support.
- Billing options are a day, a week, a month, six months, or a year, and you can cancel any time. UPI and cards are available in India; card checkout is available worldwide. Contact support for five or more slots.
Monthly pricing: $9.99 per month. The same product is included on every plan; only the billing length changes. See StreamNeo or start the free day at https://app.streamneo.com/register.
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.
