RadarKeep

Finds video on a page and saves it as one MP4, with a local library. Anonymous diagnostics help fix bugs.

RadarKeep finds video streams on the pages you visit and saves them to your own disk as normal video files you can keep, open offline, or archive. How it works: when a page's video is delivered as an HTTP Live Stream (HLS .m3u8 playlists, in MPEG-TS or fragmented-MP4 form), RadarKeep detects it, lists the available qualities and resolutions, and rebuilds your chosen quality into an MP4 file entirely inside your browser. Segments are fetched, decrypted where the playlist requires AES-128, and remuxed with FFmpeg compiled to WebAssembly — no upload step, no server-side processing, no account. Long recordings are processed in bounded chunks in memory and on private local storage, and are delivered either as one file or as clearly numbered sequential parts, so multi-hour videos never exhaust available memory. Deliberate limits: RadarKeep does NOT circumvent DRM. Streams protected by Widevine, FairPlay, PlayReady or equivalent schemes are detected and refused with a clear message before any download starts. This refusal is intentional: the tool is for content you have the right to save. It also does not bypass logins or paywalls, and it never modifies or blocks other websites' traffic — it only reads response headers to notice playlists, and adjusts headers on its own download requests. Access model: instead of asking upfront to read data on every website, RadarKeep asks for access one site at a time, only when you start using it there. Privacy: all processing happens locally on your machine. RadarKeep sends small anonymous diagnostic reports when a download succeeds or fails, so bugs can be fixed. Each report can only contain: a random per-install identifier, the extension version, the browser version, the event type, an error category and stage, numeric technical counters (segment counts, resolution, variant index, HTTP status, error and FFmpeg exit codes), whether the stream had a separate audio track, and — only when file joining fails — the last lines of FFmpeg's log, which refer to internal temporary file names. Reports cannot contain page addresses, hostnames, page titles, filenames or any browsing history: an exact allowlist of fields is enforced before anything is sent. Full details: https://radarkeep.com/privacidade No ads, no tracking, no account.