Quick answer: RTMP streaming sends a continuous audio-and-video feed from a broadcaster to a platform’s ingest server. For a prerecorded broadcast, a service plays your finished file and sends that feed to the destination. You need the destination’s server URL and stream key; a normal video watch link is not a substitute.

This guide explains the connection itself: which values belong where, how to check that the right event receives the feed, and what to inspect when it does not. It applies whether the source is a finished lesson, a recorded programme or a single looping video.

Understand the four pieces of an RTMP live stream

  1. Source: the approved video file you want people to watch
  2. Broadcaster or encoder: the software or cloud service that sends the live feed
  3. Ingest destination: the receiving server identified by the platform’s server URL
  4. Viewer page: the page where the audience watches the resulting broadcast

The stream key routes or authorizes the feed at the destination. Treat it as a secret: do not put it in screenshots, public support posts, tutorial examples or shared planning documents. A watch-page URL is shareable; a stream key is not.

“Custom RTMP” usually describes entering the server and key yourself instead of choosing an account-linked destination. It does not remove the receiving platform’s eligibility rules, content rules or technical requirements. You still need a valid destination that accepts the kind of output you are sending.

RTMP versus RTMPS

RTMPS adds TLS encryption to the connection between the sender and ingest server. Where both ends support it, use the secure endpoint supplied by the platform. Copy the complete address rather than guessing an endpoint or changing a prefix by hand. YouTube explains the distinction and how to retrieve its secure URL in its RTMPS setup guide.

Transport encryption does not set the audience visibility of a broadcast. Check public, private or unlisted visibility at the destination independently. It also does not grant permission to broadcast copyrighted material.

Set up a prerecorded RTMP broadcast

1. Prepare the receiving event

Create the intended live event on the destination platform and obtain its server URL and stream key. For YouTube, use Live Control Room and follow the official encoder connection instructions. Keep a note of the event title and watch-page URL so you can verify the correct event without recording its secret key in your checklist.

2. Make the source ready

Import the approved file into your broadcaster and confirm that it is ready to play. Review audio, aspect ratio and the ending. Decide whether playback should stop after one showing or repeat. A file being present in storage does not prove that the intended output settings are compatible.

3. Enter the destination values separately

In the broadcaster’s destination configuration, enter the platform-provided server URL and stream key in their corresponding fields. Avoid leading or trailing spaces. Do not paste the viewer URL into the server field, and do not combine the key with the server address unless the receiving application specifically requires a combined format.

DriveStream Pro currently supports manual RTMP/RTMPS output. Direct YouTube account connection and on-demand Drive-to-YouTube uploads remain coming soon, according to the public product FAQ. Manual streaming does not depend on those planned upload features.

4. Test the entire route

Use a private or unlisted test event with a short, recognizable clip. Confirm the destination receives the correct picture and audio, then check viewer playback. If your event requires a separate public start action, complete that only when ready. Finish the rehearsal by confirming both the destination event and sender have stopped.

Troubleshoot by following the signal

  • No incoming signal: confirm the sender is running, the imported video is ready, and the server/key pair belongs to the intended destination
  • Authentication or key error: compare against the current destination settings; if a key was rotated, update the authorized sender rather than reusing an old copy
  • Certificate or secure-connection error: recheck the official RTMPS endpoint and sender support; do not bypass security warnings
  • Preview works but viewers cannot watch: inspect event visibility and its public live state
  • Picture works but audio does not: listen to the source, then the destination preview, to identify where sound disappears
  • Playback stops later: inspect source ending, loop settings, service usage limits and destination stream-health notices

Change one variable at a time and record the non-secret error message. Repeatedly replacing every setting makes it harder to tell which change fixed the problem. If the key was accidentally exposed, use the platform’s official key-reset controls and reconnect the intended sender.

A valid connection still needs a suitable plan

RTMP carries the broadcast; your plan determines the available capacity. DriveStream Pro plans start at $5 USD per month. Choose the output quality, destination capacity and resource allowances your broadcast needs; continuous use requires a suitable plan. Storage, preparation and outgoing-data limits apply, including to a long-running loop. The service says streams pause at an allowance limit with no automatic overage charges. Check the published plan data and compare plans before choosing the output. For continuous channel planning, use the 24/7 YouTube live-stream guide.

For a broader operating checklist, continue with the recorded-video live-stream checklist. If your source is in Drive, use the Google Drive source workflow.