finds.dev

asdfghj1237890/WebVideo2NAS

Self-hosted Chrome → NAS pipeline: capture HLS / DASH / MP4 streams from any site and download to your NAS. Single multi-arch Docker image (FastAPI + worker + ffmpeg) distributed via GHCR.

View on GitHubHomepage ↗

★ 1,168PythonNOASSERTIONupdated Oct 2026

// the take

WebVideo2NAS is a self-hosted Chrome extension plus a Docker-based API/worker stack that detects HLS, DASH, and MP4 streams as you browse and ships them to a NAS, including a browser-side relay path for streams whose tokens are bound to your session cookies. It's for NAS owners (Synology gets first-class support) who want an automated way to grab video from sites that don't offer a download button.

The browser-side pipeline is a real engineering solution to a hard problem — an offscreen document keeps a long-lived fetch loop alive past the service worker's 30s eviction, and declarativeNetRequest rules spoof Referer/Origin per host so cookie-bound segment fetches behave like the original player. Security defaults are better than most self-hosted tools: server-side plan URL validation (SSRF protection) runs unconditionally at /api/jobs/init regardless of the optional SSRF_GUARD flag, plus API key auth, per-IP rate limiting, and CIDR allowlisting. The changelog shows actual root-cause debugging rather than vague fixes — e.g. tracing a silently-truncated HLS merge to the concat demuxer mis-computing PTS offsets across segments, with a byte-concatenation fix and a backfill script to catch previously-affected downloads. There's a real test suite backing this (~300 extension tests plus API/worker test suites covering zombie job reaping and stale browser-job cleanup), not just a README full of checkmarks.

The core function is downloading video streams from sites that deliberately didn't give you a download button, which puts a chunk of its target use cases outside most streaming sites' terms of service — DRM bypass is explicitly out of scope, but plenty of non-DRM content is still 'we don't want this downloaded'. The README is upfront that it shouldn't be exposed past your LAN or a VPN tunnel, which undercuts the normal NAS expectation of reaching your own box from anywhere. It's run by a single, anonymously-named maintainer with no visible team or org behind a project that has meaningful attack surface (a network-facing API, a worker, and a browser extension requesting broad host permissions) — if they stop maintaining it, there's no succession path. The changelog itself is a record of a steady stream of subtle correctness bugs surfacing only under real use (duplicate detections, stale progress state, zombie jobs, the half-length-merge issue above), which tracks with how brittle stream-scraping tools generally are — expect detection to break again whenever target sites change delivery, and expect to update often to keep up.

We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
1,168
Forks
70
Language
Python
License
NOASSERTION
Last commit
23 Oct 2026

// nearby

If WebVideo2NAS isn't quite it.

All repos →