Wowza nDVR and YouTube Live DVR are separate features for different playback destinations. Wowza documents time-shift playback for streams delivered through its own supported playback paths; YouTube has a DVR control for people watching on YouTube, and the documentation reviewed here does not show Wowza rewind controls passing through to that player.
Before configuring anything, confirm which Wowza product you use and where viewers will watch. If they watch on YouTube, start with YouTube's live DVR settings and confirm the current Wowza-to-YouTube ingest procedure separately. If they watch a Wowza-served HLS or MPEG-DASH stream, investigate the relevant Wowza nDVR controls.
Identify the Wowza product and viewer destination
“Wowza nDVR” can refer to different configuration contexts. Wowza Streaming Engine has an nDVR feature configured on a live application. Wowza Video documents a Playlist Seconds setting on a Wowza CDN stream target. These are not two names for the same set of controls, and their documented settings should not be mixed.
The viewer destination matters just as much. A viewer playing an HLS or MPEG-DASH URL served through a Wowza workflow is not using the YouTube player. A viewer watching the broadcast on YouTube uses YouTube's player and its controls. A 24/7 source can be routed into a workflow that has more than one output, but you must identify which output each viewer will actually use before deciding that a rewind setting is relevant.
Write down these two facts before following a guide:
| Question | Why it changes your next step |
|---|---|
| Are you using Wowza Streaming Engine or Wowza Video? | The products have separate configuration paths and terminology. |
| Will the viewer watch on YouTube or on a Wowza-served player? | YouTube Live DVR and Wowza nDVR apply to different playback experiences. |
If you only know that a Wowza product is involved, do not begin by copying a setting from a guide with “nDVR” in its title. Check the product name in your account or deployment, then check the destination player. For a YouTube-only audience, you may not need Wowza nDVR at all. You still need a confirmed delivery route into YouTube, but the research available for this article does not establish the exact Wowza ingest endpoint, encoder values or key workflow. Check the current instructions for the product and destination you have chosen rather than filling those gaps by guesswork.
What Wowza nDVR does for Wowza playback
Wowza Streaming Engine's nDVR records an incoming live stream while making time-shift playback available to supported Wowza playback clients. Its documentation describes playback over HLS and MPEG-DASH. It is intended for a viewer who receives the stream through that Wowza playback route, not a general rewind switch that can be applied to any destination receiving the same live source.
In the Streaming Engine Manager, the documented setup starts by selecting a live application, opening its nDVR controls, enabling the feature and restarting. You then configure the DVR store and recording or playback behaviour, save the changes and restart to apply them. The XML route uses DVR recorder and store settings along with a DVR streaming packetizer and the packetizers needed for the output protocols. These are application-level steps: they are not instructions for changing YouTube's player.
The availability choice affects what a Wowza viewer can seek to. The “all material available” approach makes the recording available and retains it after the live stream ends. A rolling window exposes recent material and purges older content outside the selected duration. Wowza's setup documentation gives 60 seconds as the minimum window duration. Decide whether you need a short catch-up window or access to the longer recording before selecting a retention behaviour; they serve different purposes and have different storage implications.
The playback URL and application options also matter. Depending on configuration, a DVR query parameter may be required in the URL, and the application must support the relevant live and DVR playback modes. Test a normal live URL and then the DVR URL in the intended player. Wowza's guide says RTMP and RTSP do not support this DVR playback; an RTMP publishing path does not mean that an RTMP viewer can rewind through nDVR. For details on the application-level workflow, use Wowza's nDVR setup documentation, and verify the current guide for your software version.
What YouTube Live DVR does for YouTube viewers
YouTube Live DVR is the relevant feature when someone watches the live broadcast on YouTube. YouTube's Help page explains that viewers can pause, rewind and resume during a live stream when DVR is available. If a creator disables DVR, viewers cannot seek back while the stream is live; a recording may still be available after the live event ends. The current behaviour and controls should be checked in YouTube's live DVR help.
That is a YouTube playback feature. It does not follow from the fact that a stream originated in Wowza, nor does a Wowza nDVR recording automatically define the rewind range inside YouTube. Treat the YouTube setting and the Wowza playback configuration as separate decisions, even if they concern the same source programme.
For a devotional channel, for example, you might want viewers to rewind the current bhajan while watching a YouTube live stream. That means checking YouTube's live DVR behaviour for the broadcast. If you also maintain a separate Wowza HLS stream for a website, nDVR could be relevant to that website's viewers, but you would test that playback path independently. A setting in one player should not be assumed to change the other.
A long-running channel also needs a plan for what happens when the live event or source is interrupted. YouTube's archived recording behaviour and the availability of a rewind control during a live stream are distinct questions. Likewise, a Wowza recording store is distinct from a YouTube archive. Before relying on either for a full-day channel, check the official documentation and run a test with the actual destination account and player.
Why the two DVR controls are not interchangeable
The word “DVR” describes a viewer capability, but the systems that provide it are different. Wowza Streaming Engine records the incoming stream and serves time-shift playback using documented Wowza output protocols. YouTube provides controls to viewers in its own player. The research reviewed for this article does not document a Wowza nDVR rewind window or control being passed through to YouTube, so do not promise that configuring one will enlarge, enable or otherwise control the other's rewind experience.
| Decision | Wowza Streaming Engine nDVR | YouTube Live DVR |
|---|---|---|
| Viewer destination | Wowza-served playback | YouTube player |
| Documented playback context | HLS and MPEG-DASH | Live playback on YouTube |
| Main control described | Application recording, store and DVR playback settings | Whether YouTube viewers can seek back during the live stream |
| What is not established here | Control of the YouTube player's rewind range | Control of a separate Wowza playback window |
The distinction is useful when troubleshooting. If viewers on YouTube cannot rewind, first check the current YouTube live DVR options and the behaviour of the actual broadcast. Changing a Wowza rolling-window duration is not a documented fix for that YouTube playback issue. If viewers on a Wowza HLS page cannot seek back, inspect the application configuration, URL, supported protocol, source compatibility and player instead of changing a YouTube control.
This separation also affects how you explain the experience to viewers. Do not advertise a specific rewind period on YouTube based solely on a Wowza nDVR setting. Test what the viewer can actually do on YouTube, and describe that behaviour accurately. If you offer a second player on your own site, document its playback behaviour separately. For context on keeping a YouTube loop running from recorded material, see how a playlist can act as a 24/7 livestream source; that is a different question from controlling rewind in a Wowza player.
Confirm the delivery and playback path
Sketch the path from source to viewer before changing settings. Identify the live source or encoder, the Wowza product receiving it, the output or stream target, and the player the viewer opens. Mark the YouTube destination separately from any Wowza-served player. This simple map helps uncover a common mistake: configuring recording on an application that is not actually serving the playback audience you want to affect.
For a YouTube audience, verify the current ingest instructions for the exact Wowza product and YouTube workflow in use. The sources reviewed for this article do not establish a complete Wowza-to-YouTube procedure, including endpoint, stream-key steps, encoding profile or reconnect guidance. Do not infer those values from a general Wowza description of a 24x7 channel. Confirm them in current official product documentation and test with the intended YouTube account before scheduling a continuous broadcast.
For a Wowza Streaming Engine audience, publish a compatible live source to the intended application, establish ordinary live playback first, and only then test recording and seeking. Wowza notes that aligned audio and video are important, and that short keyframe intervals and aligned tracks work best. Its quick-start material lists H.264 video and AAC or MP3 audio among supported types, while warning that unsupported source codecs can prevent recording. A source that looks and sounds acceptable in one player is not proof that recording and time-shift playback will work; use the actual incoming stream and intended player in the test.
A 24/7 workflow makes interruptions and retention practical concerns. Wowza documentation warns that nDVR recording can be interrupted when the source disconnects and describes a default stream timeout of five minutes to allow for encoder disconnects and restarts. Treat that as a documented application behaviour to verify against your version and deployment, not as a guarantee that every interruption will be bridged seamlessly. Plan how you will detect a stopped source, confirm recording resumes, retain material you need and monitor storage. The reviewed sources do not provide a universal storage-capacity formula, so estimate using your own stream and retention requirements and validate before depending on it.
If the YouTube stream drops and reconnects, check the YouTube output quality as well as whether viewers remain on the intended live destination. Our guide to restoring quality after a YouTube stream reconnects covers that separate operational problem. Reconnection behaviour is not a substitute for verifying DVR: test rewind and resume after the broadcast is live, and check again after any reconnect or configuration change.
Choose the relevant configuration documentation
If you have Wowza Streaming Engine and want Wowza-served DVR playback, follow the Streaming Engine nDVR setup guide for the live application. Confirm that the software version, licence and playback protocol match the documentation. Wowza's current indexed setup material identifies Streaming Engine 4.7.6 or later for MPEG-DASH nDVR. Licensing details can vary, particularly for older licences, so check Wowza's current licensing documentation and your account rather than assuming a feature is enabled.
If you use Wowza Video, do not apply Streaming Engine Manager steps to it. Wowza Video documentation describes Playlist Seconds on a Wowza CDN stream target as the rewind depth. The documentation lists a range from 6 to 28,800 seconds, with a stated default of 100 seconds; those are Wowza Video values, not YouTube settings and not Streaming Engine application settings. Consult Wowza's Playlist Seconds configuration guide and its API documentation for the exact product version and target type you use. The API guide also cautions that player support varies and that nDVR does not work with Wowza Player, so test the player you intend to use rather than relying on the setting alone.
The configuration choice becomes clearer when you write the goal as a sentence: “I need viewers in this player to rewind this much of this live source.” Name the product, player and destination in that sentence. If the destination is YouTube, use YouTube's current live-stream settings and official help for the viewer control, then verify the ingest route independently. If the destination is a Wowza-served player, use the documentation for the exact Wowza product and test its supported playback protocol.
Do not copy a setting because the number sounds suitable for a full day. A rolling window, retained recording and YouTube's live DVR control address different behaviours. Make the retention choice based on whether viewers need only a recent catch-up interval or whether you need the recording to remain accessible, and make that choice only for the Wowza path it is documented to control. If the main pain is keeping a looping video online without leaving a personal computer running, StreamNeo can take the uploaded file and run it as a YouTube live stream, which avoids relying on a local computer to stay on; it does not replace Wowza nDVR for a separate Wowza playback destination.
For another perspective on routing prerecorded material to a continuous YouTube broadcast, see setting up a stream that plays recorded videos overnight. Choose that kind of workflow only after you have settled the source and destination; it does not change which platform controls the viewer's rewind feature.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can viewers rewind a 24/7 YouTube live stream?
YouTube's live DVR feature lets viewers pause, rewind and resume during a live stream when it is available. Check YouTube's current settings and test from the viewer's perspective, because this is separate from a Wowza nDVR window.
Does Wowza nDVR control YouTube DVR?
The documentation reviewed here does not show Wowza nDVR controls passing through to YouTube. Wowza documents nDVR for playback through its supported Wowza paths, while YouTube describes its own live DVR feature.
Which Wowza guide should I follow?
First confirm whether your product is Wowza Streaming Engine or Wowza Video, then identify the intended playback destination. Streaming Engine uses live-application nDVR configuration; Wowza Video documents Playlist Seconds for a CDN stream target. Do not mix their settings.
Does setting a Wowza rewind window ensure uninterrupted 24/7 playback?
No. A rewind setting describes playback behaviour, not uninterrupted delivery. Validate source compatibility, reconnect handling, recording retention, storage and monitoring in the actual deployment, and confirm YouTube ingest instructions from current official documentation.