Unpublished landing page · planned-unpublished · not indexed

RTMP ingest

RTMP live streaming with managed ingest and delivery

Keep the encoder workflow your team already knows, point it at a managed RTMP ingest endpoint, and serve viewers browser-ready HLS playback through the player, embed or direct URL.

  • You supply a compatible encoder that accepts a custom RTMP server and key
  • DynTube supplies the ingest endpoint and the HLS playback URLs
  • Managed ingest and delivery infrastructure
Start free trial

RTMP in, HLS out

Encoder → managed ingest → viewer

Three hops, and you only own the first one

RTMP carries the feed from your encoder to a receiving server. HLS is what a browser can actually play. The part in between is the part you were going to have to build.

1 · Your encoderYou run this
A compatible encoder — software such as OBS, or a hardware unit that lets you enter a custom RTMP server and key — publishes your feed to the ingest region you picked when you created the stream.
2 · Managed ingestWe run this
The ingest endpoint receives what your encoder publishes and turns it into HLS segments for delivery. There is no server for you to provision, patch or scale, and no ingest configuration to write.
3 · HLS to viewersYou hand out the links
Viewers watch over HLS using the player, embed snippet or direct URL your Dashboard provides for that stream. They are never given the RTMP address — ingest and playback are two different things.

Step one

Create the stream, then copy the pair

Ingest details belong to a stream that exists, so there is nothing to paste into an encoder until you have created one.

  1. 01

    Create a New stream

    Give it a name, choose the ingest region you want your encoder to publish to, and set the per-stream options you need. Pick the region closest to the machine that is broadcasting — that field is about your encoder, not your audience.

  2. 02

    Open its Connect tab

    The stream’s detail page shows a read-only Server URL and a stream key that is masked until you reveal it. Each has a copy action, and the key carries a keep-this-private warning because anyone holding it can broadcast to your channel.

  3. 03

    Copy both values exactly as displayed

    Use the copy actions rather than retyping. DynTube has more than one ingest shape, and a New stream and an older legacy stream do not present their server and key the same way, so a hand-built address can pair the wrong halves. Copying the displayed pair is the reliable method.

Step two

Send the feed, and read what the Dashboard tells you

Publishing is what makes a stream live. The Dashboard reflects that state rather than causing it.

Point the encoder at the copied pairIn OBS: the “Custom…” service
Set OBS to the “Custom…” service, paste the Server URL into its server field and the stream key into its stream key field, and leave OBS’s “Use Authentication” checkbox unticked — the credential is already inside the pair you copied. That guidance is for OBS specifically; on another encoder use its own custom-RTMP server and key fields as that encoder documents them, and invent no separate username and password, because the Connect tab issues none.
Press start, then confirm the statusLive means a publisher was observed
Once your encoder is actually publishing, the backend records the stream as live and the detail page shows that status while you have it open. Treat it as your confirmation that a publisher has been observed, rather than assuming success from the encoder alone.
Read the viewer count as audience, nothing elseZero can be correct
The viewer count beside the status reports your audience only. It does not diagnose whether your encoder is reaching DynTube, so a genuinely live stream with nobody watching yet correctly shows zero.
End it from either sideEncoder or Dashboard
Stopping your encoder closes the publisher session. A New live stream can also be ended from the Dashboard using its authorised End Stream control, which disconnects the active publisher.

Step three

How the audience watches, and what you keep

Playback URLs come from the Dashboard. Recording is a separate, optional choice made per stream.

  • A player URL

    The Dashboard gives you a player URL for the stream, so the broadcast is watched on a surface you control rather than on someone else’s site.

    HLS delivery

  • An embed snippet

    An embed snippet is provided for the stream so it can sit inside your own page. You copy it from the stream’s embed tab; there is nothing to write yourself.

    Copy from the Dashboard

  • A direct URL

    A direct URL is available when you need to hand out a link instead of embedding — an email, a chat message, a calendar invitation.

    Share as a link

  • Recording is optional

    Enable recording for an eligible stream and plan when you want a library copy, then choose the project where the recording should be stored.

    Per-stream, plan-gated

    Learn more

  • The key is a credential

    The stream key is what authorises publishing, which is why the Dashboard masks it and warns you to keep it private. Give it only to the person or machine that is broadcasting.

    Keep it private

  • Test the audience path

    Live status confirms the ingest side only. Once it shows live, open a Dashboard-provided player or direct URL separately from the encoder machine and confirm it plays before you send the link out.

    Before you announce

Before you start a trial

RTMP ingest questions

What is RTMP ingest?

RTMP is the contribution protocol your encoder speaks: it publishes a live feed to a receiving server and expects a server address plus a key proving the sender is allowed to publish. “Ingest” is that receiving side. DynTube runs it for you and converts what arrives into HLS, which is the format a browser can play. You never operate an ingest server yourself.

Which encoder can I use?

Use an encoder that accepts a custom RTMP server and stream key, including widely used software such as OBS. In OBS, choose the “Custom…” service, enter the copied pair and leave “Use Authentication” unticked. For another encoder, use its documented custom-RTMP fields and test a private broadcast before the event.

Where do I find the stream key?

On the stream’s Connect tab in your Dashboard, once the stream has been created. It sits next to the read-only Server URL, masked until you reveal it, with a copy action and a warning to keep it private because anyone holding it can broadcast to your channel. Copy both displayed values exactly rather than assembling an address yourself — a New stream and an older legacy stream present their server and key differently.

How do viewers watch the stream?

Over HLS, using the player URL, embed snippet or direct URL the Dashboard provides for that stream. Viewers need a browser and the link you give them. They are never given the RTMP ingest address, and there is no RTMP playback path for an audience.

Keep your encoder and use managed live delivery.

Create a stream, copy its Server URL and stream key, publish from the encoder you already run, and hand viewers a Dashboard-provided playback URL.

Start free trial