What YouTube documents about a stream that never stops

The replay of a long stream never appeared. Rewind stopped working partway through. Or the stream dropped for a moment, came back, and the link you had already given out was pointing at nothing.

Read a few explanations of any of those and they will contradict each other. So everything below that is YouTube’s position is quoted from its own help pages, each one linked where it is used. Where the joins between those quotations are our reasoning rather than YouTube’s, it says so. And where YouTube does not document something, that is what it says instead. On this subject, a surprising amount is not documented at all.

One word you will meet in the quotations: YouTube says “encoder” for whatever software is sending your video to it. If you use OBS, OBS is your encoder.

The short version:

• Nothing in YouTube’s documentation stops a stream at 12 hours. That number governs what you get out of a stream rather than how long it may run.
• Past 12 hours you may get no recording at all, and rewind may stop working.
• A strike stops you streaming for 14 days.
• Whether a reconnect continues your broadcast or starts a new one is not documented anywhere, and that is the question most people arrive with.

Is there a 12-hour limit?

Twelve hours is the number everyone arrives with, and it turns up in more than one of YouTube’s articles. On every page where we found it, it governs what you get out of a stream rather than how long the stream may run. Nothing in YouTube’s documentation stops a stream at 12 hours.

Will you get a recording afterwards?

YouTube’s article on archiving says:

If your live stream is less than 12 hours, YouTube can automatically archive it for you.

Note the “can”. The walkthrough for setting one up puts the same threshold as a certainty instead: “All streams under 12 hours will be automatically archived.” It says that twice on the one page, so the categorical version is the one you are more likely to meet first.

We are going with the hedged one anyway, and it is worth being open about why, because the count does not favour it. The reason is provenance: “can automatically archive” is on the article whose whole subject is archiving, and that article is also the one carrying the failure case.

Note: If your stream exceeds 12 hours, it may not be captured at all.

The “may not” is a possibility, not a promise of loss. The “at all” means the outcome described is that no recording exists, not that you get the first 12 hours of one. On none of the pages we read does YouTube describe a half-saved recording, so if you were hoping for one, that hope is not coming from its documentation.

There is no escape hatch in how you stream, either. Automatic archiving “applies to all types of live streams, including: encoder, webcam, and mobile”, and the next sentence adds that “YouTube will also automatically archive streams of 1440p and 2160p (4K) video resolution”. YouTube’s own advice on the same page, for anyone who needs the recording to exist, is “We recommend recording a local archive as a backup”. That assumes you are running software you can record from, and not everybody is.

Why did rewind stop working?

Twelve hours turns up again in what YouTube calls DVR, the ability to move around inside a stream while it is still going: “Enabling DVR lets viewers pause, rewind, and continue during your stream.”

If your live stream becomes very long, your viewers will only be able to rewind up to a limit as DVR capabilities may be limited or unavailable for streams longer than 12 hours.

That offers two different outcomes, limited or unavailable, and the page never says which applies when. Some ways of watching are tighter still: “Viewing on Apple TV, Apple AirPlay, or older app versions is subject to lower limits.” The page does not say how much lower.

Something else catches people out on a channel meant to run day and night: “These limits also apply when a viewer uses pause and resume.” Pausing eats the same allowance as rewinding does, rather than sitting outside it.

The strongest word that page uses about rewind is “never”:

Viewers can never seek back to before you went live.

Whatever the rewind limit turns out to be, it stops at the start of the current broadcast. A stream that began at four this morning has nothing behind four this morning, for anybody.

One sentence on that page is easy to find on its own and easy to misread: “If you choose to disable DVR, viewers cannot seek back while you are streaming, but viewers can still see a recording of your entire stream once it is available.” It explains what switching DVR off does and does not cost you, and it assumes a recording exists. Whether one exists is the archiving article’s subject, and that is the page with the 12-hour caveat on it.

What ends a broadcast?

For an unscheduled stream, YouTube’s instruction for ending one is a single line: “To end the stream, stop sending content from your encoder.” For a scheduled stream the same page adds a button: “To end the stream, click End Stream and stop sending content from your encoder.” Stopping the video is part of it either way.

Whether a gap in that video ends your broadcast comes down to a setting called auto-stop. The stream settings page describes auto-start and auto-stop in two sentences and gives no timing at all: “When these settings are on, you can start or stop streaming from your encoder.” The number lives only in YouTube’s technical documentation:

YouTube will automatically end the broadcast around a minute after you stop sending video on the bound live stream.

The same page says it a second time in different words. The broadcast ends “about a minute after you stop transmitting video”, and the reference says “around one minute” again. Three statements, two saying “around” and one “about”, and not one of them commits to a figure. It is an approximation in the original, and it only describes what happens with auto-stop switched on.

With auto-stop off, we could not find a page that says what happens when the video stops arriving. We read the stream settings page, the walkthrough, the troubleshooting page, the getting-started guide and the page on avoiding restrictions, plus four technical documents, and none of them states it. The closest is a note in YouTube’s guide to retiring default broadcasts, which says that with those settings off, ending the broadcast becomes the job of whatever software is driving the stream. What YouTube does by itself in that situation, if anything, is not written down on any page we checked.

Worth knowing if you set a stream up by copying an old one: “Copying a stream by selecting ‘Reuse settings’ will also copy your auto-start and auto-stop selections.” Whatever you chose once travels forward with you.

What else can end it?

Video is not the only thing. “All live streams are scanned for matches to third-party content”, and if a match stays in the stream, “your live stream will be temporarily interrupted or terminated”. Your stream “can also be terminated if you get a copyright or Community Guidelines strike”.

What a strike then costs you is on the getting-started page: “A strike will prevent you from live streaming for 14 days.” That is 14 days in which nothing can be restarted.

Why did my link stop working?

Two things here both feel like “the stream”, and they do not behave the same way.

Start with the watch page, the page people actually open. YouTube’s walkthrough puts its creation at the moment you go live: “Set up your encoder, then start the stream with your encoder. A watch page is now created for your stream, and you’re now live on YouTube.” It belongs to that streaming session, and it is made when the session starts.

Now the stream key. A stream can be attached to more than one broadcast: YouTube’s technical documentation has a setting for whether “the stream is reusable, which means that it can be bound to multiple broadcasts”, and adds that “It is common for broadcasters to reuse the same stream for many different broadcasts if those broadcasts occur at different times.” The help pages describe the ordinary case in terms a returning streamer will recognise: “Your previous stream settings will load, including your stream key, which means you won’t need to update your encoder.” And YouTube’s own analogy for the key: “Stream keys are like your YouTube stream’s password and address.”

What that adds up to is a conditional rather than an answer. If a second broadcast begins, it gets its own watch page, and the link people already have is not that one, while the key sitting in your software is very likely untouched. That asymmetry is what makes the symptom so disorienting: the thing you configured once turns out to be fine, and the thing you handed out is the one that stopped working.

What none of it tells you is whether your stream started a second broadcast in the first place. A blip, a reconnect, a deliberate restart: nothing we found says which of those begins a new broadcast and which continues the old one. That is exactly the gap the symptom sits in.

Does Live Redirect fix it?

No, and it is worth saying because it is the first thing you find when you go looking. Live Redirect’s documented destinations are “a Premiere to build excitement” or “another channel’s live stream to help other creators grow”, and its instructions say to “Choose a Premiere or search for another channel’s live stream to redirect to”. The stream settings page summarises this more loosely as “a Premiere or another live stream”, which is easy to read as your own next broadcast; the dedicated article is the one to go by. Redirecting to another channel needs that channel’s permission, and the feature is gated to “creators sending a redirect that have more than 1,000 subscribers and no Community Guideline strikes”.

How often can you start again?

A stream that keeps having to restart itself runs into two limits.

There is a limit of 10 active streams allowed per channel and 3 active streams per stream key. These limits are applied at the same time.

The consequence is the sentence immediately after it: “Once either limit is reached, you will not be able to start additional streams.”

What “active” means is not defined on that page, and neither is how long a finished stream goes on counting as active. Without those, the arithmetic for a channel that restarts every few hours cannot be done, by us or by anyone reading the same page.

The second limit is on creating streams in the first place. It sits on the page about avoiding restrictions, in the catch-all “Other restrictions” section rather than anywhere you would think to look for it: “If you’ve reached your daily limit for creating live streams, you can try again in 24 hours.” The page does not give the number. Only the reset window.

What YouTube does not say

Every one of these is YouTube not saying something on any page we read, which is not the same as YouTube saying it does not happen.

• A maximum stream length. We found none, and the 12-hour thresholds govern what you get out of a stream rather than how long you may run. A missing ceiling is not the same as documented permission to run forever, but it does mean nobody should be quoting you a limit.
• What happens when the video stops and auto-stop is off. Not stated on any page we read.
• Whether reconnecting quickly continues the same broadcast or starts a new one. Probably the question that brought you here, and no page we checked addresses it. The one-minute figure describes a broadcast ending with auto-stop on. It is not described as a window to get back in, and reading it as one is a guess rather than a citation.
• Streams measured in days rather than hours. Past 12 hours the documentation stops making distinctions, and a fortnight is described exactly as thoroughly as two days: not at all.
• The figures behind the rules. How much lower the Apple TV and AirPlay limits are, and the number behind the daily creation limit. Both are documented as existing. Neither is quantified.
• What counts as an “active” stream for those two caps. The page that sets them does not define it.

What to do about it

None of this is anything a streaming tool can change, ours included. It is YouTube’s from end to end, so the answer is to plan around it: treat the channel as a live destination rather than an archive of recordings, and accept that if something ends the broadcast, something has to start it again.

Every quotation above was read on 23 September 2026. These articles get reworded without notice, and the hedged archiving sentence and the two-sentence auto-stop section in particular read like they are waiting to be rewritten. If you are reading this a long way from that date, open the sources and check them yourself.