Blog / Guide

How to Download a Live Stream in Chrome

How to Download a Live Stream in Chrome

You can download a live stream in Chrome, but with an important limit: what you can usually save is the broadcast from the moment your recording starts. The part that aired before you joined is a separate question, and the answer depends on what the service keeps available, not on which tool you use.

So the first thing to settle is not which extension to install. It’s what you actually want:

  • The part you missed: look for a replay, a rewind control in the player, or a download option from the publisher. A recorder that starts now can’t fetch what the server has already stopped serving.
  • The rest of the broadcast, from now on: record the live feed while it’s running. For a supported, unprotected stream, MAX Video Downloader does this in Chrome.
  • A protected or unsupported stream: there is no honest workaround. Use the service’s own offline or replay feature, if it has one.

The rest of this guide explains why the first case is so different from the second, how to tell which one you’re in, and how the two main ways of capturing a live broadcast compare.

Why a live stream isn’t a file yet

A video on demand has a known length and all its pieces already exist. A live stream is still being made. Most browser-playable live video is delivered as a sequence of short segments that the player requests one after another, and a playlist or manifest tells it which segments are currently available.

HLS, the most common case, shows the consequences clearly. Apple’s live playlist example describes a playlist that is updated by removing old media URIs as new ones are added, giving a “moving window into a continuous stream”. The playlist also has no EXT-X-ENDLIST tag while the broadcast is going on, which signals that more segments will follow. The HLS specification (RFC 8216) says that servers may limit the availability of segments by removing them from the playlist, and that when the final segment is published the playlist must contain EXT-X-ENDLIST.

Two simplified, abbreviated playlists, not taken from a real service, show the same stream at two moments. First:

#EXTM3U
#EXT-X-TARGETDURATION:6
#EXT-X-MEDIA-SEQUENCE:58
#EXTINF:6.0,
seg58.ts
#EXTINF:6.0,
seg59.ts
#EXTINF:6.0,
seg60.ts
#EXTINF:6.0,
seg61.ts
#EXTINF:6.0,
seg62.ts

A little later:

#EXTM3U
#EXT-X-TARGETDURATION:6
#EXT-X-MEDIA-SEQUENCE:61
#EXTINF:6.0,
seg61.ts
#EXTINF:6.0,
seg62.ts
#EXTINF:6.0,
seg63.ts
#EXTINF:6.0,
seg64.ts
#EXTINF:6.0,
seg65.ts

Segments 58 to 60 have left the playlist. A recorder that joins at the second moment sees nothing before segment 61, and that’s exactly what the reader who joined late is looking at. The service may keep older segments somewhere for a rewind feature or a replay, or it may not. The playlist alone doesn’t say.

Two other points from the specification are useful in practice:

  • A player normally doesn’t start at the very beginning of a live playlist. RFC 8216 says that, when the playlist has no EXT-X-ENDLIST, a client that intends to play normally should not start less than three target durations from the end. Players therefore begin near the live edge, not at the start of what the server has published.
  • A missing EXT-X-ENDLIST is a clue about the playlist, not about the platform. It tells you the stream isn’t marked as finished, but nothing about whether a replay will exist afterwards or how long it will be kept.

DASH describes live content with a dynamic manifest. The idea is the same: the manifest keeps changing, and a finished file doesn’t exist until the broadcast has ended. The DASH guide covers how to recognize one. For HLS playlists, segments and tracks in more detail, see How to Download M3U8 / HLS Videos in Chrome.

Decide what you’re looking at

A live badge, a scrubber, a replay and a changing playlist are different observations, and they call for different responses.

What you see What it suggests What to do
The broadcast is on and you joined from the start A recorder started now captures nearly everything. Start recording at once and keep the tab and connection stable.
The broadcast is on, but it began some time ago The earlier part may be unavailable to a recorder that starts now. Check the player for a rewind control; the earlier part can only be saved if the service still serves it or publishes a replay later.
The player has a rewind slider that works The service is exposing some earlier material. Rewinding in the player shows it is playable, not that a recorder will capture all of it. Start recording as early as you can.
The stream has ended and a replay or “past broadcast” appears The broadcast is now a normal recording. Treat it as a video on demand: use the publisher’s download option, or a regular download tool.
The stream has ended and nothing is published The service may not keep archives. Nothing a downloader does can bring back segments the server no longer serves.
The player shows a lock or an error, or nothing is detected The stream may be protected or served in a way the tool can’t read. Stop. Don’t try to defeat protection.

Whether the platform keeps a replay, for how long, and whether you can export it differs from service to service, and those policies change. Check the platform’s current help page before relying on any assumption. We haven’t listed retention windows here because a general number would only be wrong for some of them.

Capturing the stream versus recording the screen

There are two different ways to “download” a live broadcast, and they don’t produce the same result.

Source capture follows the media feed the page is already loading and saves the segments, as a stream downloader does. The result is the stream as the service delivers it, at the quality you choose, and it doesn’t depend on what’s on your display. It also doesn’t depend on the stream being visible, so the tab can stay in the background.

Screen recording captures what your computer shows and plays. A tool such as OBS can record almost anything you can watch, including streams a downloader can’t read. The tradeoffs are real, though:

  • The quality is limited by your screen’s resolution, and the video is encoded a second time.
  • Anything that interrupts the screen, such as notifications, a minimized window or a sleeping display, can interrupt the recording.
  • Audio needs to be captured as well, and capturing system audio takes extra setup on some systems.
  • It takes up real time and attention: it records at the broadcast’s speed and, in practice, wants the player kept visible.

Neither method changes what you are allowed to do with the content. A screen recorder gets around a stream’s technical format, not the publisher’s terms. If a service prohibits recording, or protects the stream to prevent it, that remains true for both approaches, and neither is advice to defeat a protection scheme.

For ordinary, unprotected streams, source capture is usually the better first choice: it keeps the original quality and doesn’t tie up your screen. Screen recording is the fallback to consider only where recording is clearly permitted and nothing else can read the feed.

How to record a live stream with MAX

MAX works with the page where the stream is already playing, and records supported live streams while they’re broadcasting, saving them as local files. Starting a recording doesn’t guarantee that every later segment is captured: a dropped connection, an expired link or a stream the service ends can all leave gaps. Its FAQ lists non-DRM live content such as Twitch, Twitter and VK streams as examples. MAX doesn’t support DRM-protected media or YouTube, and support for a particular platform’s live format isn’t guaranteed.

  1. Install MAX from the Chrome Web Store (free).
  2. Open the live broadcast and let it play, so the page requests the stream.
  3. Open the MAX popup and select the detected live stream. If nothing shows up, try Force Detection.
  4. Choose the quality and start the download. The recording covers the broadcast from that moment on.

A few things to expect:

  • A live recording can only contain what the source is still serving when you start. MAX can’t recover segments that have already left the playlist.
  • Live recordings have their own output-format setting: MKV by default, with fMP4 or MP4 as alternatives.
  • If a download is interrupted, MAX keeps the media that has already been saved so you can play it.
  • Recording runs in Chrome by default. The optional desktop app adds native FFmpeg processing and suits long recordings, which is where a broadcast lasting hours belongs.

Before you start a long recording

A live recording can’t be redone, so a few minutes of preparation matter more here than for a video on demand:

  • Check free disk space. Hours of video take real space, and a full drive ends the recording.
  • Make sure the machine won’t sleep and that the connection is stable. A gap in the connection can mean a gap in the segments, and the server may not hold the missed ones for long.
  • Start before the stream does, if you can. Opening the page a few minutes early removes the missed-start problem entirely.
  • Plan for a replay. If the platform publishes one, it may be a cleaner source than the live capture. A live recording is the backup, not the best case.
  • Do a short test run on a quiet stream if you’re relying on a setup for something important.

When to stop

Don’t spend time on a live stream when:

  • the media is DRM-protected,
  • the platform’s rules don’t allow recording or saving the broadcast, or
  • the page never exposes a usable media source, in which case the tool has nothing to record.

In all three cases the right step is the platform’s own replay or offline option, or asking the broadcaster. Recording a live feed you’re permitted to keep is straightforward. The broadcast you didn’t record, though, is only recoverable if the service kept it for you.