RTMP
RTMP stands for Real-Time Messaging Protocol. In a YouTube live-streaming workflow, it is commonly used to send encoded video, audio, and control data from a creator's encoder to YouTube's ingest server.
RTMP is part of the connection between the creator and YouTube. It should not be confused with the full delivery path YouTube uses to process the stream and play it for viewers on different devices.
How RTMP works with YouTube Live
- A camera, microphone, screen capture, or other source feeds a Live Encoder.
- The encoder compresses the production into a supported video and audio stream.
- The creator enters YouTube's stream server URL and a stream key into the encoder.
- The encoder sends the feed to YouTube through RTMP or a supported alternative.
- YouTube processes and distributes the live stream to viewers.
In many encoders, selecting a built-in YouTube service preset fills in the server details automatically. The creator may still need to connect the YouTube account or enter the stream key.
RTMP server URL vs. stream key
| Item | Purpose | Security |
|---|---|---|
| Server URL | Tells the encoder which YouTube ingest endpoint to contact | Usually not treated as the private credential |
| Stream key | Identifies and authorizes the creator's stream destination | Must be kept private and reset if exposed |
The encoder needs both pieces unless it connects directly through an authenticated YouTube integration.
RTMP vs. RTMPS
RTMPS is secure RTMP. YouTube describes it as RTMP sent through a Transport Layer Security connection, which encrypts the live data between the encoder and YouTube's servers.
| Protocol | Encrypted ingest | Current YouTube codec listing | Latency modes |
|---|---|---|---|
| RTMP | No | H.264 | Normal, Low, and Ultra-low |
| RTMPS | Yes | H.264 | Normal, Low, and Ultra-low |
When an encoder supports YouTube RTMPS, the secure option is generally preferable because it protects the ingest connection from interception or tampering.
RTMP vs. HLS and DASH ingest
| Protocol | Strength | Trade-off |
|---|---|---|
| RTMP/RTMPS | Broad encoder support and compatibility with all three YouTube latency modes | Current YouTube comparison limits these ingest options to H.264 |
| HLS | Encrypted ingest, HEVC support, HDR, and strong 4K suitability | Segment-based delivery generally creates more latency and does not support Ultra-low Latency |
| DASH | Encrypted ingest and VP9 support for high-resolution streaming | Generally higher latency and no Ultra-low Latency support |
The best protocol depends on the encoder, codec, resolution, latency needs, and production requirements.
How to connect an encoder with RTMP
- Open YouTube Studio and choose Create → Go live.
- Create or select the event in Live Control Room.
- Copy the stream URL and stream key from Stream Settings.
- Paste them into the server and stream-key fields in the encoder.
- Configure the recommended resolution, frame rate, bitrate, keyframe interval, video codec, and audio settings.
- Start the encoder and confirm that YouTube receives a healthy preview before going live.
How to use RTMPS on YouTube
First check whether the encoder includes a YouTube RTMPS preset. If not, YouTube says creators can reveal the RTMPS URL by selecting the lock icon next to the Stream URL in Live Control Room, then copy the secure URL and stream key into the encoder.
If an RTMPS connection produces an SSL error, verify that both the protocol and server use rtmps. YouTube's troubleshooting guidance also identifies port 443 as an option when the encoder requires an explicit secure port.
Common RTMP problems
- Invalid stream key: The key is mistyped, expired, reset, or connected to the wrong event.
- Cannot connect: The server URL, protocol, port, firewall, or network route is incorrect.
- Unstable stream: Upload capacity is insufficient or inconsistent, causing Dropped Frames.
- No preview: The encoder has not started, the event is using another key, or the feed does not match supported settings.
- Unexpected delay: The selected Low Latency or Normal Latency mode, protocol, buffering, and viewer conditions affect end-to-end delay.
Creator finances handled by someone who gets YouTube.
Tax prep and bookkeeping built for YouTubers — every income stream, every deduction, done right.
Tax Services for Creators Bookkeeping for CreatorsFrequently asked questions
What does RTMP mean on YouTube?
It is a protocol an encoder can use to send a live feed to YouTube's ingest server.
Should I use RTMP or RTMPS?
Use RTMPS when the encoder supports it. It provides an encrypted connection while retaining the familiar RTMP workflow.
Is my YouTube RTMP URL the same as my stream key?
No. The URL identifies the ingest server. The stream key is the private credential that directs and authorizes the feed for the channel or event.
Does YouTube only support RTMP?
No. YouTube's current developer documentation lists RTMP, RTMPS, HLS, and DASH as supported ingest protocols for third-party clients.