Guide

Why I Open-Sourced GetVideos Locally

A downloader handles links, cookies, and files on your PC. Here is why I made the code public and kept accounts and subscriptions out of it.

Trust is a feature

A video downloader touches URLs, cookies, and files on your disk. Closed-source apps ask you to trust a black box. Open source lets anyone audit how downloads run, how cookies are handled, and where files are written.

GetVideos Locally is built to be inspected: fork it, change defaults, and keep using your build even if upstream priorities shift.

Cost without the rake

Subscriptions make sense for cloud sync and multi-seat teams. A local converter that already runs yt-dlp and FFmpeg on your PC does not need a monthly fee to justify itself. Open source removes the incentive to nickle-and-dime quality tiers.

No licence server checking in on your PC.
No “HD unlock” paywall for resolutions the source already offers.
No surprise sequel purchase after a “lifetime” sale.

Longevity through forks

When a commercial product pivots or sunsets, your licence PDF does not keep the binary useful. With open source, the community or you personally can maintain a branch. That is the difference between renting a tool and owning a workflow.

Pair that with local-first design — no mandatory account — and your archive strategy survives vendor churn.

FAQ

Do I need to compile anything?

No. GetVideos Locally ships as Windows desktop software with a bundled engine, while still remaining open source for people who want to build from source.