Nabby vs yt-dlp (CLI)
The engine versus its wrapper. When each one is the right answer.
The short version
yt-dlp is the command-line engine. It is more flexible than any UI, including Nabby. Nabby is a web form that calls yt-dlp. It exists so you don't have to open a terminal or remember flags.
At a glance
| Nabby | yt-dlp CLI | |
|---|---|---|
| Interface | Browser-based web UI | Command line |
| Flexibility | Common cases only | Full — every yt-dlp flag |
| Scripting / automation | No | Yes (bash, cron, systemd) |
| Non-technical users | Yes | No |
| Site support | Allowlisted (hosted) / all (self-hosted) | All yt-dlp sites |
| Install footprint | Flask + yt-dlp + ffmpeg | Single binary + ffmpeg |
| Where it runs | A server | Your laptop |
| Learning curve | Zero | Hours |
Choose yt-dlp CLI if…
- You're scripting bulk downloads, archiving channels, or integrating with other tools.
- You need obscure flags: format selection by codec, remuxing, post-processors, cookie files, custom headers.
- You're comfortable in a terminal and don't want to run a web server.
- You want the maximum possible flexibility.
Choose Nabby if…
- You want to send a link to a non-technical friend or family member to download themselves.
- You want to grab something from your phone's browser without SSHing anywhere.
- You have "future you in two years who forgot every flag" in mind.
- You want a UI with a format picker, an audio-only toggle, and a progress bar — without maintaining a desktop app.
Honest notes
Every Nabby user is also a potential yt-dlp CLI user. We won't pretend otherwise. If you know your way around yt-dlp -f "bv*[height<=1080]+ba/b" --write-sub --sub-langs en.*, the CLI is strictly more powerful. Nabby's whole value proposition is removing that cognitive load for the 90% of downloads where it isn't needed.
← back to Nabby · FAQ · About