To stream from a Raspberry Pi to YouTube with FFmpeg, copy the stream URL and stream key from YouTube Studio’s Live Control Room, then have FFmpeg send a compatible video and audio output to that exact endpoint. Use RTMPS if your FFmpeg build supports it, keep the key private, and test the Pi’s encoding and upload capacity before relying on it for a live event. The command depends on your video source, audio source and Pi model, so there is no single command that is guaranteed to work on every setup.
Before you start: identify your source and Pi
You need a YouTube channel with access to live streaming, FFmpeg installed on the Raspberry Pi, a working video source, and enough upload bandwidth for the stream. The camera and audio source might be connected directly, provided by another device, or already encoded in a file or stream. Find out how the source appears to FFmpeg before choosing capture options; device names and input flags vary by hardware and software.
As an Amazon Associate I earn from qualifying purchases.
- Record your Raspberry Pi model and the operating system and FFmpeg build you are using.
- Identify whether your source already provides encoded H.264 video and usable audio, or whether the Pi must capture and encode it.
- Check that your network can sustain the planned total bitrate, with extra capacity for normal variation.
Raspberry Pi’s camera documentation describes rpicam-vid as a video-capture option that can use FFmpeg/libav for audio and video encoding and output. Hardware H.264 encoding depends on the Pi model. Raspberry Pi 5 uses software video encoders; its --low-latency option can reduce latency but trades off coding efficiency and may affect maximum frame rate. Do not assume capture flags or encoding performance transfer from another Pi generation. See the Raspberry Pi camera software documentation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsGet the stream URL and key from YouTube Studio
- In YouTube Studio, select Create > Go Live to open the Live Control Room.
- Open the Stream tab. Create a stream or select one you already use.
- Copy the stream URL and stream key shown there. Use the URL exactly as supplied; do not substitute a host or guess a key format.
- Keep the URL and key as separate values while configuring FFmpeg. The URL identifies YouTube’s ingest endpoint; the key identifies and authenticates your stream.
YouTube describes stream keys as “like your YouTube stream’s password and address.” Treat the key as a secret: do not show it in screenshots, post it in a public forum, commit it to a repository, or leave it in shell history where others can read it. See YouTube’s live stream settings instructions.
#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
Choose RTMPS or RTMP
YouTube supports RTMP and RTMPS ingestion and recommends RTMPS, which encrypts the connection. Copy the RTMPS URL from the Live Control Room rather than editing an RTMP URL by guesswork. The installed FFmpeg build must support the TLS features needed for that endpoint. If it does not, check the build or choose a supported endpoint rather than treating an encryption error as a bad stream key. YouTube’s RTMPS troubleshooting guidance advises using port 443 for some SSL errors; apply that only with the endpoint and circumstances described there.
FFmpeg’s RTMP protocol documentation explains how output URLs and playpaths are handled. For YouTube, use the stream URL and key from your own Live Control Room in the format expected by the endpoint and FFmpeg build; do not assume that every service combines them the same way. See the FFmpeg RTMP protocol documentation.
Prepare an FFmpeg output that YouTube accepts
YouTube’s encoder guidance supports H.264, H.265 or AV1 video; AAC or MP3 audio; constant bitrate (CBR); and frame rates up to 60 fps. It recommends a two-second keyframe interval and says not to exceed four seconds. For H.264 at 720p30, YouTube’s guidance accessed in 2026 lists a recommended bitrate range of 3–8 Mbps. These are platform recommendations, not a guarantee that a particular Pi can encode at that setting or that your network can upload it reliably. Recheck YouTube’s encoder settings guidance before a production stream because its recommendations can change.
Rank #2
- Includes Raspberry Pi 4 4GB Model B with 1.5GHz 64-bit quad-core CPU (4GB RAM)
- Includes Pre-Loaded 32GB EVO+ Micro SD Card (Class 10), USB MicroSD Card Reader
- CanaKit Premium High-Gloss Raspberry Pi 4 Case with Integrated Fan Mount, CanaKit Low Noise Bearing System Fan
- CanaKit 3.5A USB-C Raspberry Pi 4 Power Supply (US Plug) with Noise Filter, Set of Heat Sinks, Display Cable - 6 foot (Supports up to 4K60p)
- CanaKit USB-C PiSwitch (On/Off Power Switch for Raspberry Pi 4)
YouTube automatically detects resolution and frame rate by default. Manual resolution is configured through a custom stream key. YouTube transcodes incoming streams for playback formats, so test the stream and inspect Live Control Room’s stream-health status instead of assuming that a specific input bitrate will look good for every viewer.
If the input is already encoded
If your input already contains compatible H.264 video, -c:v copy can pass the video through without asking the Pi to encode it again. This reduces processing, but only works if the source’s codec, pixel format, timestamps and bitrate are acceptable for YouTube and FFmpeg’s output container. You may still need to encode audio as AAC. Stream-copy does not let you change the copied video’s resolution or bitrate.
If the Pi must encode the video
Configure the input device first, then choose an encoder and output settings that the particular Pi can sustain. Re-encoding lets you control resolution, frame rate and bitrate, but consumes compute. Test with movement representative of the real stream and monitor both the Pi and YouTube’s stream health. Pi generation, input format and FFmpeg build determine which encoders and options are available.
Command structure and safe placeholders
The following is a structure, not a universal, tested command. Replace the input and output portions with options appropriate to your source and installed FFmpeg build. Use the exact ingest URL and key copied from the Live Control Room; do not publish or share a real key.
Free tools Windows power users keep installed
One-click scans. No signup required.
ffmpeg [input options] -i [your video and audio source] [encoding or stream-copy options] -f flv "<YOUTUBE_INGEST_URL>/<STREAM_KEY>"
Some endpoints or FFmpeg configurations use URL and playpath options differently. Check the RTMP protocol documentation and the format shown by YouTube rather than blindly appending the key if your endpoint does not use that structure. If your setup has no audio source, do not add a silent audio track unless the actual stream requires one. Map the intended audio and video streams explicitly when the input has multiple tracks.
Rank #4
- Broadcom BCM2711, quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1. 5GHz
- 2. 4 GHz and 5. 0 GHz IEEE 802. 11b/g/n/ac wireless LAN, Bluetooth 5. 0, BLE
- 2 × USB 3. 0 ports, 2 x USB 2. 0 Ports
- 2 × micro HDMI ports supproting up to 4Kp60 video resolution
- Micro SD card slot for loading operating system and data storage
Set up capture on a Raspberry Pi
For a Raspberry Pi camera, Raspberry Pi documents rpicam-vid capture and a libav backend for network streaming; its guidance recommends libav for most applications. Start by confirming that capture works independently, then connect that output to the FFmpeg path you intend to use. Other cameras and capture devices may appear through different interfaces, so determine the correct FFmpeg input rather than copying an input string for another device.
- Verify the camera or other source is detected and produces the expected video.
- Verify audio separately if the stream needs it; identify the correct audio input instead of assuming the camera supplies sound.
- Confirm that the Pi’s chosen encoder is available in the installed FFmpeg build and appropriate to the Pi generation.
- Test the assembled FFmpeg command locally or with a private test stream before using it for an event.
Raspberry Pi’s camera documentation includes capture and streaming details at raspberrypi.com/documentation/computers/camera_software.html. Pi 5’s software encoding makes it especially important to test the intended resolution and frame rate rather than assuming hardware-encoder performance from an older model.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Start the stream and go live
- Start FFmpeg and read its output for connection, input, codec or muxer errors.
- In the Live Control Room, wait for YouTube to receive the signal and display a preview. Check the detected video, audio and stream-health indicators.
- For a scheduled stream, select Go live in YouTube when the preview and stream state are correct.
- To finish, stop the FFmpeg encoder and end the stream using YouTube’s Live Control Room workflow.
Do a full test before the real event. Include typical movement and sound, since a static image or silent test will not reveal all encoding, audio or bandwidth problems. YouTube recommends leaving 20% bandwidth headroom above the total stream bitrate and monitoring stream health. See YouTube’s streaming tips.
Best Value
- 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
Troubleshoot common failures
No preview or connection failure
- Compare the URL and key in the command with the current values in Live Control Room; check for a copied space, missing character or stale key.
- Read the FFmpeg log for DNS, TLS, authentication or muxer errors. These point to different causes, so do not assume every failed connection means the key is wrong.
- If you reset the key, replace the old key in the encoder configuration.
RTMPS certificate error or timeout
- Confirm that the copied endpoint is actually an RTMPS URL and that the FFmpeg build supports the required TLS protocol.
- Use the port 443 guidance only where YouTube’s SSL troubleshooting page recommends it, and retain the YouTube-supplied endpoint.
Dropped frames or unstable output
- Compare the total video-plus-audio bitrate with measured upload capacity and retain YouTube’s recommended headroom.
- Reduce resolution, frame rate or bitrate if the connection cannot sustain the target; reduce encoding load if the Pi cannot keep up.
- Test with representative motion and watch YouTube’s stream-health indicators.
Wrong or missing audio or video
- Check that the command reads the intended input and maps the intended streams.
- Confirm output codecs are supported by YouTube and that the input actually contains the audio you expect.
Suspected stream-key exposure
Reset the key in Live Control Room, then update the encoder configuration. YouTube says only channel owners or managers can reset a stream key. Do not continue streaming with a key that may have been exposed.
DIY FFmpeg or a cloud service?
FFmpeg on a Pi is useful when you need to stream a live camera or other live input and are prepared to configure and maintain the capture, encoding and network path. A cloud looping service is a different fit: it plays uploaded videos rather than broadcasting a live camera feed, and it removes the need to keep a home computer or Pi running for that uploaded-video stream.
Or let it run in the cloud
StreamNeo keeps a YouTube channel live from uploaded videos, not a camera. Upload a recording or build a playlist, add your YouTube stream key once, and go live. The cloud loops the video, so nothing has to stay on at home. Each slot streams the upload as made, up to 4K 60fps, at one flat price per slot; there are no quality tiers. If YouTube drops the stream, StreamNeo automatically attempts recovery. The first day is free with no card. Monthly billing is $9.99 per month. See StreamNeo for details, or 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.
