Platform capability
How live stream recording works in DynTube
Recording is a choice you make for one stream before you go live, and it depends on your plan. Turn it on, name the video project the recording should land in, and the broadcast arrives there as recording segments — each completed segment becomes one library video, so a broadcast may create one or more of them.
The replay plays in the DynTube player, or in an embed on your own page
The short answer
How live recording works and plan eligibility
Recording keeps the broadcast a live stream would otherwise leave behind — but only for the streams you enable it on, and only on a plan that includes it.
A live stream is, by default, a one-off. The encoder sends video, viewers watch it, and when the publisher session closes there is nothing left on the platform to link to. Recording changes that for a single stream: when it is enabled before the broadcast, the output captured during the session is uploaded into a video project you nominated, where it becomes one or more ordinary library videos.
Two things decide whether it is available to you at all. Recording has to be included in your plan, and it has to be switched on for that particular stream in advance. Neither is retrospective: a broadcast that ran without recording enabled cannot be recovered afterwards, because with recording off the local output is discarded rather than kept.
- Opt-in per stream. It is a setting on the stream, not an account-wide default, and it is made before you go live.
- Plan-gated. Your account's entitlement is checked when the recording is uploaded, not only when you enable the option.
- Destination-bound. You select the video project the recording belongs to as part of enabling it.
- Segmented. The broadcast is captured as recording segments; each completed segment is uploaded on its own and becomes one library video, so a recording may create one or more of them.
- Not retroactive. With recording disabled, nothing is kept from that broadcast.
Why it matters
Why teams preserve their broadcasts
The work that goes into an hour of live video rarely stops being useful when the hour ends.
Without control
Nothing to keep once the stream ends
Everything the event was worth stays locked to the people who happened to be free at the time. A missed session becomes a support request, and the material has to be produced again for anyone who arrives later.
- Only the live audience ever sees it
- Latecomers and other timezones get nothing
- The same session gets re-run for a handful of people
- Nothing to link to from an email, a course or a page
On your own terms
A video you own, in your own library
The recording lands in a project you nominated, so it is handled the way the rest of your video is handled: in the DynTube player or an embed on your own page, and there for the people who could not attend.
- One event serves the live audience and everyone after it
- A replay to point people to instead of repeating the session
- Sits in a project you chose, alongside related material
- Behaves like any other video you host from that point on
Destination
Choosing the video project the recording lands in
The destination is part of the decision to record, and it is checked twice — when you set it, and again immediately before the upload.
- A project in the same accountOwnership
- The destination has to be a video project in the same DynTube account as the stream. A project in another account is not a valid destination.
- Active and publishedLifecycle
- The project has to be active and published at the point the recording is uploaded. A project that has been archived, unpublished or removed in the meantime is no longer a valid destination.
- In the stream's regionRegion
- The project has to be in the same region as the live stream. Recording does not move the output between regions, so a cross-region destination is refused rather than silently relocated.
- Able to hold videoProject type
- The destination has to be a project that can hold video library items. A project that is not video-capable cannot take a recording.
Workflow
Enabling recording and running the stream
Four decisions, all of them before anyone is watching.
- 01
Confirm your plan includes recording
- 02
Enable recording on that stream
- 03
Nominate the destination video project
- 04
Broadcast as usual, then let the session close
The result
Publish the recorded result from your video library
A recorded broadcast becomes video library items in the destination project. What happens to them after that is yours to decide.
During the broadcast, the stream is captured as recording segments. Each completed segment is uploaded into the destination project on its own and becomes one video library item, so a recorded broadcast may create one or more videos there. From then on they are videos you own like any other: renamed, embedded, managed or removed through the same controls as anything else in that project.
The step to plan for is the one after the upload. Arriving in a project is not the same as being announced: what the replay is called, who is allowed to watch it and which page it appears on are decisions you make on the video, exactly as you would for anything else in your library. Nothing is published to an audience on your behalf.
| Recording enabled | Recording disabled | |
|---|---|---|
| During the broadcast | The session is captured as recording segments | No capture is kept |
| As each segment completes | That segment is uploaded to the project you nominated | The local output is discarded |
| Afterwards | One video library item per segment in that project, under your control | Nothing to recover — the broadcast was live only |
| Publishing the replay | You decide the title, access and placement | Not applicable |
Because uploading starts only once a recording segment or the publisher session has closed, the place to confirm a recording is the destination project itself. If a broadcast you recorded is not there, check the eligibility rules above and contact support with the stream and the project you nominated.
Scope and limits
What live streaming includes
- RTMP ingest, HLS playbackCompatible RTMP encoder
- Point an encoder that accepts a custom RTMP server and key at your DynTube ingest endpoint; viewers watch over HLS in the DynTube player, in an embed on your own page, or through the direct URL. Compatibility with every encoder or capture device is not claimed.
- SchedulingOne-off and recurring
- Prerecorded videos from your own library can be scheduled as a single dated broadcast or on a repeating pattern. The videos you select and the timing are checked when you save the schedule.
- RecordingOpt-in and plan-gated
- Recording is a per-stream choice. When enabled and included in your plan, each completed segment is uploaded into the video project you select.
Troubleshooting
Verify the recording workflow
Most missing recordings come down to one of four things: the plan, the per-stream setting, the destination project, or the session not having closed yet.
Does DynTube record every live stream automatically?
No. Recording is opt-in for each stream and depends on your plan. A stream that ran without recording enabled produced no recording, because with recording off the output from that session is discarded.
My stream has ended and there is no recording. What went wrong?
Check, in order: whether your plan includes recording, whether recording was enabled on that stream before the broadcast, whether the destination project was still active and published in the same account and region when the stream ended, and whether the publisher session has actually closed. Uploading begins only once a recording segment or the session itself has closed. If everything above checks out, contact support with the stream and the destination project.
Where does the recording end up?
In the video project you nominated when you enabled recording, as video library items — one per recording segment. They are then handled through the same controls as any other video in that project.
Can I choose or change the destination project after the stream?
No. The destination is part of enabling recording, so it is set before the broadcast. Once the recording exists as a video library item, you manage it like any other video in your library.
What happens if the destination project is archived or unpublished before the stream ends?
The project and your account's entitlement are re-checked immediately before the upload. If the project is no longer an active, published, video-capable project in the same account and region, the recording is not uploaded to it.
When does the recording start arriving?
Uploading begins once a recording segment or the publisher session has closed, so a recording can start arriving before the broadcast has finished. Check the destination project in your library, and contact support if a recording you enabled is missing.
Is the replay published to my audience automatically?
No. The recording arrives as a video library item; its title, access rules and placement on your pages are yours to set, exactly as they are for an uploaded video.
Is a recorded broadcast always one video?
Not necessarily. Recording is captured as segments, and each completed segment is uploaded separately and becomes one video library item, so a recorded broadcast may create one or more videos that together cover the session.
Related
Where to go next
Live streaming
The pillar page: encoder to viewer, what live includes, and how a stream is set up in the first place.
Capability overviewLive stream recording
The focused page for teams who already know they need the replay, with the first hour laid out end to end.
Get startedLive streaming pricing
Which plans include live streaming, recording and the rest of the live capability set.
Plans
Put the replay on your own pages
Host, deliver and measure your video, and embed it where your audience already is.