Short answer: a local desktop tool keeps your cookies, tokens, and downloaded files on your own machine; a browser extension inherits access to your browsing but runs with the extension’s permissions; an online service receives the URL you submit and processes it on a server you do not control. If the video is login-gated, the local option is usually the only one that can work at all — and the only one where nothing leaves the device.
The three models, side by side
| Dimension | Local desktop app | Browser extension | Online paste-URL service |
|---|---|---|---|
| Where the request comes from | Your machine | Your browser | A remote server |
| Where cookies go | Read locally, stay on disk | Accessible to the extension per its permissions | Not available to the service — so login-gated media is normally out of reach |
| Login-gated video | Yes, with a session you supply | Sometimes, if the page exposes the media to the tab | Typically no |
| What you submit | Nothing leaves the device | Nothing submitted; the extension sees your page | The URL, and whatever the operator logs |
| Install required | Yes | Yes | No |
| Auditability | Runs offline; behaviour is observable locally | Permissions are declared in the manifest | Server-side behaviour is not observable from the client |
| Best fit | Regular saving, private or logged-in sources | Occasional saving from public pages | One-off saves from public, unsigned URLs |
None of these rows is a judgement about intent. Operators of online services may be entirely trustworthy; the point is that you cannot verify their retention policy from the client, and that is a different risk posture from a program that does its work offline.
What to actually check before you trust a tool
1. Where does the network traffic go?
The decisive question. A tool that never sends your cookies, tokens, or watch history anywhere is a categorically different proposition from one that uploads them for processing — even if both produce the same file at the end. “Local-first” should mean the request originates on your machine and no session material is transmitted.
2. What does it do with cookies?
Reading a browser profile and copying it into a separate working profile is a defensible design: the original browser is untouched, the working copy is on your disk, and the tool only uses it to open the pages you ask for. Be more cautious with tools that ask you to paste cookie strings into a web form — that is a credential leaving your control.
3. What does it record about you?
Look at what is persisted. Status and warnings about a migration or a download are reasonable. Secret values are not. If a tool keeps history, check whether that history is local and whether you can clear it.
4. Does it claim to bypass protections?
Treat any claim to defeat DRM, paywalls, or access controls as a red flag, both practically and legally. Tools that describe themselves honestly are describing what they do: capture what a browser can already play.
A note on legality
Downloading a video is governed by the site’s terms of service and by copyright law where you live. This article compares technical approaches; it is not legal advice. Save what you have the right to save.
Matching the tool to the job
Course and research material behind a login
You need a session-aware tool. The practical requirement is that it reuses the login you already hold — copying cookies and storage from a browser profile into a working profile, or letting you sign in once in its own browser window. An online service cannot do this; a browser extension may or may not.
Public clips and social media
Any of the three models can work. Here the deciding factors are convenience and volume: a desktop tool with a queue and live progress handles a batch better than pasting URLs one at a time, and keeps the files where you can organise them.
Occasional, throwaway saves
An online service is genuinely convenient for a single public URL — the trade-off is that the URL is now in someone else’s logs. For anything repeating, the install cost of a desktop tool pays for itself.
How VidBrowser is positioned
VidBrowser is a free desktop app for macOS and Windows built on the local-only model. The target browser renders the real page, so it works wherever a browser can play the video — there are no per-site plugins to install.
- Session reuse: copy cookies and storage from a Chrome, Edge, or Firefox profile into a working profile, or sign in manually in the target browser.
- Local-only privacy: cookies, tokens, watch history, and downloads stay on this device. The app does not upload your login state, viewing history, or downloads to a server.
- Broad format handling: direct files download as served; HLS and DASH are probed and remuxed to MP4 or MKV; extractor-driven sites get a yt-dlp pass.
- Separate working window: the target browser opens in its own window, apart from your everyday browser.
Migration results record status and warnings only — never secret values. That is the design constraint worth asking any tool about.
Keep the login on your machine
Free for macOS and Windows. Reuse the browser session you already have and save the video to your own disk.
Download VidBrowser freeFrequently asked questions
Is an online video downloader safe to use with my login?
Most cannot use your login at all — they fetch the URL from their own servers, which is why login-gated video usually fails there. The safety question is about what the operator retains from what you submit. You cannot inspect that from the client, which is why a local tool is the lower-risk choice for private or signed-in sources.
What does “local-first” mean for a video downloader?
It means the fetching happens on your machine and your session material stays there. Cookies and storage are read from a local browser profile into a separate working profile on disk, and the resulting file is written to your download folder. Nothing about your login state is transmitted.
Is a browser extension less private than a desktop app?
Different, not automatically worse. An extension runs inside your browser with permissions declared in its manifest, so it can see the pages you visit. A local desktop app that works from a copied working profile sees only what you point it at. Check the permissions in either case.
Do I need to hand over my password to a download tool?
No. Session reuse works from cookies and storage your browser already holds, or from you signing in directly in the tool’s own browser window. A tool asking for your password so it can “fetch on your behalf” is asking for something this workflow does not require.
Does any of this bypass DRM or a paywall?
No. These approaches cover video that plays for you in an ordinary browser session. Encrypted-media delivery and subscription checks are outside the scope of all three models.