One primary action
Open the popup and press Download best quality. The highest compatible source is selected for you, every time.
One-Click Video Downloader detects the best source the page is already playing, then saves a clean MP4. Direct files go straight through your browser. Adaptive and split streams are merged locally by FFmpeg. Best quality, local processing, no cloud.

The normal path hides manifests, fragments, stream pairing, codecs, and FFmpeg flags. You start playback, open the popup, and press one button.
The extension watches what the active page requests and ranks every candidate: direct MP4, HLS, DASH, or separately delivered video and audio.
A direct MP4 goes straight through your browser’s download manager. Anything adaptive or split is handed to a small local helper instead.
A local Python host runs FFmpeg to merge, remux, or transcode only what is incompatible. Media bytes never leave your machine.
A validated MP4 lands in your Downloads folder, named from the page title. One explicit action, start to finish.
No resource lists, no manual parser controls, no engine settings. One automatic plan replaces the busywork, while the hard cases still work.
Open the popup and press Download best quality. The highest compatible source is selected for you, every time.
Direct MP4, HLS (.m3u8), DASH (.mpd), and separately delivered video and audio are detected and paired automatically.
Capture live streams with Stop and save. The host finalizes the file and validates it before it is marked done.
Compatible streams are copied untouched; only incompatible video or audio is transcoded. Faster saves, cleaner quality.
Run up to three downloads at once with live progress. Bounded reconnects and retries ride out temporary failures, even if you close the popup.
Everything runs on your machine. No analytics, no remote parser, no cloud service. Only HTTP(S) media you are authorized to save.
The extension only sends control data to the local host: URLs, an allowlisted subset of request headers, and job commands. FFmpeg fetches and processes the media directly. The bytes stay between the page and your disk.
This is a focused tool for media you own or are authorized to save. Several popular capabilities are out of scope on purpose, and that restraint is the point.
Direct MP4 downloads need only the extension. Adaptive, split, and live jobs use a small local host built on Python and FFmpeg.
Open chrome://extensions, enable Developer mode, choose Load unpacked, and select the project’s extension/ folder. Copy the 32-character extension ID.
Run the installer with the project’s .venv and your extension ID. It creates an isolated production environment and registers the host for that exact ID.
Play a video you are authorized to save, open the popup, and press Download best quality. The file lands in your Downloads folder.
.venv/bin/python native-host/install_host.py \
--extension-id YOUR_EXTENSION_ID \
--browser chrome \
--with-yt-dlpWindows, Linux, and WSL instructions, plus troubleshooting, live in the project README.
Honest answers about scope, privacy, and setup.
Chrome or Edge 102 and newer (any Chromium-based browser at that floor). It loads as an unpacked Manifest V3 extension.
Yes. It is licensed GPL-3.0-only. The request-observation approach is informed by Cat Catch, which is also GPL-3.0.
No. DRM circumvention and paywall bypass are out of scope by design. It only saves media you own or are authorized to save.
For direct MP4 files, no. For HLS, DASH, split tracks, or live streams, a small local host using Python 3.10+ and FFmpeg/ffprobe does the processing on your machine.
No. Everything runs locally. The extension sends only control data (URLs and allowlisted headers) to the local host, and FFmpeg fetches the media directly. There is no analytics and no cloud.
Into your operating system’s Downloads folder, with a clean kebab-case filename derived from the page title, for example showcase-video.mp4.
Yes, up to three at once, each with its own live progress. Downloads keep running in the background if you close the popup.
Supported. Use Stop and save: the host asks FFmpeg to finalize the file and validates it before presenting it as complete.
One explicit action. Authorized media only. No cloud required.