Arroxy and yt-dlp.app both position themselves as desktop GUIs for yt-dlp on Windows, macOS, and Linux. The pitches sound similar: paste a URL, pick quality, download, no command line. The difference is in the app layer: install channels, Linux formats, telemetry stance, SponsorBlock, and workflow.
TL;DR
- Arroxy ships through Winget, Scoop, Homebrew Cask, AppImage, Flatpak, and GitHub Releases; is MIT licensed; includes optional SponsorBlock chapters or trims for local copies; and ships in 21 languages.
- yt-dlp.app is also MIT-licensed and open source. Its site advertises Windows, macOS, Linux AppImage, and
.debbuilds, automatic yt-dlp/FFmpeg setup, 0 telemetry/tracking, and 1,510+ supported sites. - Both wrap yt-dlp, so site support and quality options are similar at the engine level. Pick by the desktop workflow around the engine.
Definition blocks
Arroxy — Free, MIT-licensed open-source desktop app from antonio-orionus. Available on Windows 10/11, macOS 11+ (Intel + Apple Silicon), and Linux (AppImage, Flatpak, tar.gz). Distributed via Winget, Scoop, Homebrew Cask, AppImage, Flatpak, and GitHub Releases. Auto-fetches yt-dlp at runtime; FFmpeg/ffprobe ship with each release. Source on GitHub. No premium tier, no feature gating, no usage limits.
yt-dlp.app — A separate, similarly-named MIT-licensed desktop GUI project at yt-dlp.app. Its site advertises Windows, macOS (Intel + Apple Silicon), Linux AppImage and .deb, automatic yt-dlp/FFmpeg download on first launch, one-click engine updates, private-content cookie import from major browsers, and 0 telemetry/tracking. Do not confuse it with the yt-dlp command-line tool itself, which is the engine both apps wrap.
Disambiguation
This is the most common confusion: there are three things called something with “yt-dlp” in the name.
| Name | What it is |
|---|---|
| yt-dlp | The CLI download engine. Powers most other tools listed here. |
| yt-dlp.app | A separate desktop GUI project. MIT-licensed and open source per its public site. |
| Arroxy | A desktop GUI project at arroxy.orionus.dev, separate from both above. |
Arroxy is not affiliated with the yt-dlp.app project. We share the same upstream engine (yt-dlp) but the apps are unrelated codebases and teams.
Feature axes that distinguish them
Because both wrap yt-dlp, the engine-level features (site support, format options, 4K + HDR, playlist) are similar. The differences live in the surrounding app: license, distribution, post-processing extras, and platform polish.
| Axis | Arroxy | yt-dlp.app |
|---|---|---|
| License | MIT, full source on GitHub | MIT, source on GitHub |
| Distribution channels | Winget + Scoop + Homebrew + AppImage + Flatpak + tar.gz + direct | Direct downloads + GitHub Releases |
| Apple Silicon native | Yes | Yes |
| Linux formats | AppImage + Flatpak + tar.gz | AppImage + .deb |
| yt-dlp setup | Fetched automatically on launch | Fetched automatically on first launch |
| FFmpeg setup | FFmpeg/ffprobe bundled with each release | Fetched automatically on first launch |
| SponsorBlock at download time | Yes, built-in | Not advertised on the public site |
| Languages (i18n) | 21 | English public site; verify app locales |
| Queue persistence across restarts | Yes | Verify in app |
| Telemetry default | Anonymous aggregate OpenPanel; opt-out; no URLs/titles/paths | 0 telemetry/tracking per public site |
The site-support number is not a meaningful deciding factor here. yt-dlp.app advertises 1,510+ supported sites, while Arroxy uses yt-dlp’s broader supported-sites list and describes it as 2000+. Both are wrapping the same upstream class of extractor engine. The app-level details matter more.
The naming confusion in practice
This post exists because the confusion is real. Common patterns I’ve seen in support threads and Reddit:
- “I installed yt-dlp.app from
pip install yt-dlp” — that’s the yt-dlp CLI, not yt-dlp.app the GUI. - “Is Arroxy a fork of yt-dlp.app?” — no. Different team, different codebase. Both call yt-dlp underneath.
- “I downloaded yt-dlp from yt-dlp.app” — usually means they downloaded yt-dlp.app the GUI from its website; the CLI is at github.com/yt-dlp/yt-dlp.
- “Which is the official one?” — yt-dlp the CLI is the canonical engine. yt-dlp.app and Arroxy are both third-party GUI projects built on top of it, not “official” in any sense. yt-dlp’s own FAQ lists GUIs as community projects.
The cleanest mental model: yt-dlp is the engine. yt-dlp.app and Arroxy are two of many third-party GUIs that wrap that engine. The yt-dlp project doesn’t endorse any specific GUI.
When to pick Arroxy
- You want a GUI you can install via Winget / Scoop / Homebrew Cask in a single command.
- You want full MIT-licensed source you can audit, fork, or patch.
- You apply optional SponsorBlock chapters or trims for local copies and don’t want a separate post-process step.
- You want the UI in one of 21 supported languages.
- You’re on Linux and want the Flatpak or tar.gz distribution alongside AppImage.
When to pick yt-dlp.app
- You want a clean yt-dlp GUI with 0 telemetry/tracking stated on the product page.
- You prefer
.debon Linux over Flatpak or tar.gz. - You want browser-cookie import from Chrome, Firefox, Safari, Edge, or Brave presented as a first-class feature.
- You want a GUI that tries to expose “every yt-dlp feature” rather than Arroxy’s more guided workflow.
How to install Arroxy
If you’ve already evaluated yt-dlp.app and want to try Arroxy alongside or instead:
- Windows:
winget install AntonioOrionus.Arroxy(or Scoop:scoop bucket add arroxy https://github.com/antonio-orionus/scoop-bucket && scoop install arroxy) - macOS:
brew tap antonio-orionus/arroxy && brew install --cask arroxy - Linux: AppImage, Flatpak, or tar.gz from Releases
Both apps wrap yt-dlp. Running both side by side won’t conflict — they each maintain their own yt-dlp binary cache.
FAQ
Is yt-dlp.app safe?
yt-dlp.app is a third-party GUI project for yt-dlp. As with any unsigned installer (Arroxy included), verify the download with VirusTotal before running on a clean machine. Check the project’s current state at yt-dlp.app for source-availability and distribution details.
Is yt-dlp.app the same as yt-dlp?
No. yt-dlp is the command-line download engine. yt-dlp.app is a third-party desktop GUI project that wraps the yt-dlp CLI. Arroxy is another third-party GUI that wraps the same CLI. Neither GUI is “official” — yt-dlp the project doesn’t endorse any specific GUI.
Is yt-dlp.app open source?
Yes. The public yt-dlp.app site says it is MIT-licensed and links to github.com/yt-dlp-app/yt-dlp-app. Arroxy is also MIT-licensed with full source on GitHub.
Can I install Arroxy without affecting an existing yt-dlp.app install?
Yes. Arroxy installs to its own location (%LOCALAPPDATA%\Programs\Arroxy on Windows, /Applications/Arroxy.app on macOS, AppImage anywhere you put it on Linux) and maintains its own yt-dlp binary cache in its user-data folder. No shared state with yt-dlp.app.
Which yt-dlp GUI does the yt-dlp project recommend?
None specifically. yt-dlp’s README and wiki list community GUIs without endorsement. Pick by license, distribution, and feature fit.
Methodology
Data on Arroxy compiled 2026-05-19 and refreshed 2026-06-15 from the Arroxy README. Data on yt-dlp.app compiled 2026-06-15 from yt-dlp.app and its linked GitHub repository. Both projects ship — if any factual claim here drifts, please open a GitHub issue.