Why “online” matters
There are three reasons most people search for an online YouTube downloader rather than a native one:
- No admin access. Work laptops, school computers, library terminals — you can’t install software. A web app sidesteps the entire permission question.
- No malware risk. “Free YouTube downloader” native apps have a long history of shipping bundled adware, browser hijackers and crypto miners. A web app cannot install anything; the worst it can do is show ads on its own page.
- Cross-device. Your laptop, your phone, a friend’s computer — same URL, same flow, no “is there a Mac version?” question.
What runs where
A real concern about online tools: where do the bytes actually go? Many of them route the entire video through their server — you upload the URL, their server downloads from YouTube, then forwards the file to you. That pattern means the operator sees every video you save.
VidPickr does not do that. The metadata lookup is the only thing that touches our server — a small JSON request that returns the format list for a given URL. The actual video bytes flow directly from YouTube’s CDN to your browser via signed time-limited tokens. We never hold the file. The muxing (combining the video and audio streams above 720p) happens on your CPU using the Web Codecs API, not on a server.
Practically: privacy gain (we cannot log what you saved because we never see it), speed gain (no upload-then- download server round-trip), and cost discipline (we do not pay for bandwidth on every download, which is why the service can be free).
Browser compatibility
The full feature set works in any 2022+ browser. Tested on:
- Chrome 100+ — full support including 8K AV1 and File System Access API.
- Edge 100+ — full support, same engine.
- Brave — full support; Shields can block File System Access on first use, then allow per-site.
- Arc — full support.
- Firefox 110+ — full support up to 4K. AV1 8K decoding works on most platforms.
- Safari 17+ (macOS Sonoma+, iOS 17+) — supported up to 4K; the File System Access API is more limited so the save UX falls back to a regular download.
On older browsers a graceful fallback path saves to your default Downloads folder via a standard browser-managed stream — you lose the “pick a folder” step but everything else works.
Mobile workflow
Same URL, same flow, same quality output. On iOS the downloaded MP4 lands in the Files app under Downloads and can be moved into Photos with a long-press. On Android Chrome it lands in the Download folder visible to every app. No app permissions to grant; the OS handles the file the same way it handles a PDF you just downloaded.