Ghost Downloader 3: A Cross-Platform Downloader for Six Protocols and Video Platforms
A four-platform downloader unifying HTTP, BT, and video sites, with task control through ghd and aria2 RPC.
GitHub XiaoYouChR/Ghost-Downloader-3 Updated 2026-11-20 Branch main Stars 12.7K Forks 794
Python TypeScript HTTP/BT/FTP downloads M3U8 and MPEG-DASH Windows/macOS/Linux/Android

🧭 Decision Guide

Try it if you

  • You need one application for HTTP, Magnet/BT, FTP, M3U8, and MPEG-DASH tasks.
    The README's “Features” section lists these protocols.
  • You frequently download selected clips, subtitles, playlists, or multi-part episodes from YouTube or Bilibili.
    The README's “Features” section explicitly supports YouTube and Bilibili clip selection, quality, subtitles, playlists, and multi-part episodes.
  • You need to automate download tasks with scripts and require aria2-compatible RPC or the ghd CLI.
    The README's “Always in control” and “Command Line” sections describe the aria2-compatible RPC API and ghd commands.
  • Your device runs Windows 10+, macOS 13.0+, Linux with glibc 2.35+, or Android 9.0+.
    The platform table in “About The Project” lists these version and architecture requirements.

Skip it if you

  • Your CPU lacks the AVX instruction set and your environment uses Qt 6.6+.
    The README warning states that Qt 6.6+ no longer supports CPUs without AVX.
  • Your Linux system is older than glibc 2.35, or your macOS version is older than 13.0.
    The README platform table requires Linux glibc 2.35+ and macOS 13.0+.
  • You need to develop a public Feature Packs plugin immediately.
    The README roadmap shows that making the plugin API public is unfinished and that the Feature Packs API is still stabilizing.
  • You require complete localization while your target language has less than 60% of desktop text translated.
    The README's “Translation” section says a language enters the app at 60% desktop-text translation, with untranslated text shown in English.

Requirements

  • Windows 10+, with x86_64 or arm64 support
  • macOS 13.0+, with x86_64 or arm64 support
  • Linux with glibc 2.35+, with x86_64 or arm64 support
  • Android 9.0+, with arm64-v8a listed
  • A CPU with AVX when using Qt 6.6+
  • Install ghd from Settings -> Command Line Tool before using the CLI

First step (verbatim from README)

ghd probe "https://example.com/a.torrent"

Watch out

  • Android background downloads depend on the Android 9.0+ and arm64-v8a support range.
    The README platform table lists Android 9.0+ and arm64-v8a.
  • ghost-downloader-bin and ghost-downloader-git on AUR are community-maintained packages.
    The README's Arch Linux AUR support note explicitly labels them as community-maintained packages.
  • Translation files should not be changed through pull requests; use Crowdin and Discussions instead.
    The README's “Translation” section says not to send pull requests that change translation files.
  • The roadmap still includes task editing such as binding multiple Sessions to one task, so this capability is unfinished.
    The README's “Roadmap” lists enhanced task editing as incomplete.

Alternatives

  • aria2:It is more focused when you only need aria2's native command-line downloading and do not need YouTube, Bilibili, four-platform UI, or multi-protocol integration.
    General domain knowledge; the README only states that Ghost Downloader provides an aria2-compatible RPC API.

Not stated in the README

  • The README provides no real-world throughput, concurrency, or failure-rate figures for each protocol.
  • The README does not describe feature differences between Windows, macOS, Linux, and Android.
  • The README does not list the supported browser names or versions for the browser extension.
  • The README does not explain authentication configuration details for YouTube, Bilibili, GitHub, or HuggingFace.
  • The README does not specify which browsers or anti-bot systems are covered by Real-browser TLS fingerprints.
  • The README does not list existing Feature Packs plugins or explain their installation process.
  • The README does not state the release intervals or long-term maintenance plan for the 5 releases.
  • The README does not establish a causal link between the 12,718 stars, 341 stars gained today, and any specific feature or release.

💡 Deep Analysis

6
No I am familiar with Python and Qt/PySide6 and want to build third-party extensions for Ghost Downloader 3's Feature Packs. I need the plugin API to be a stable long-term integration boundary. Is this a good time to start?
For: An open-source contributor who wants to build Feature Packs for the Python/PySide6 desktop downloader and rely on the plugin API as a stable third-party extension interface

No, not if you need a stable long-term plugin interface. It is reasonable to study the existing Feature Packs, but the README explicitly says the public API is still being stabilized.

  • About The Project says there is a growing Feature Packs plugin ecosystem, showing that the plugin direction is already operational.
  • The Roadmap explicitly lists “Make the plugin API public” and states that the Feature Packs system is operational while the API is stabilizing.
  • Python is the main language, with about 1,868,023 lines in the project data, so the technology stack matches Python contributors.

The blocker is that the API is not yet officially public. The README provides no interface documentation, compatibility promise, extension packaging format, sandbox permissions, or deprecation policy. If the plugin must be maintained long term or distributed to external users, it is better not to depend on the API until its public contract is defined.

  • README: About The Project; excerpt: has a growing Feature Packs plugin ecosystem
  • README: Roadmap; excerpt: Make the plugin API public (Feature Packs system is operational, API stabilizing)
  • Project data: main_language is Python; Python code size is 1,868,023
Not stated in the README:The public plugin API release timeline is unspecified;The plugin interface, lifecycle, permissions, and packaging format are unspecified;Compatibility guarantees and migration plans after API stabilization are unspecified
Yes I need to provide a unified download entry on Windows 10, macOS 13, Linux with glibc 2.35+, and Android 9+, covering x86_64, arm64, and Android arm64-v8a. Is Ghost Downloader 3's platform coverage sufficient?
For: A cross-platform application integrator maintaining Windows 10, macOS 13, Linux with glibc 2.35+, and Android 9+ environments

Yes, because the README explicitly lists all four platforms with minimum versions and architectures, although Linux and CPU instruction-set requirements must be satisfied.

  • The About The Project table covers Windows 10+, macOS 13.0+, Linux with glibc 2.35+, and Android 9.0+.
  • Architectures include desktop x86_64/arm64 and Android arm64-v8a, which matches a cross-platform distribution requirement.
  • The README says Android supports background downloads and live M3U8 recording, so the mobile build is not merely a static interface.

The constraints are that Qt 6.6+ no longer supports CPUs without AVX, and the Arch Linux AUR packages are community-maintained. The README does not state whether all features are equivalent across platforms, how Android background jobs behave under vendor power policies, or how packages are signed and updated.

  • README: About The Project; platform table: Windows `10+`, macOS `13.0+`, Linux `glibc 2.35+`, and Android `9.0+`
  • README: About The Project; architecture table: desktop `x86_64` / `arm64`, Android `arm64-v8a`
  • README: Native on every platform; excerpt: On Android, it records live M3U8 streams and keeps downloading in the background
  • README warning: Qt `6.6+` no longer supports CPUs without the `AVX` instruction set
Not stated in the README:Feature parity across all four platforms is not specified;The impact of Android vendor power management, background restrictions, and file permissions on continued downloads is not specified;Package signing, automatic updates, and enterprise deployment methods are not specified
Yes I am using Python to submit and manage HTTP, Magnet/BT, and M3U8 downloads. I need unified control through an aria2-compatible RPC API or CLI, including pause, resume, and wait operations. Is Ghost Downloader 3 suitable as this automation backend?
For: An automation developer who uses Python scripts to control HTTP, Magnet/BT, and M3U8 tasks and wants to reuse the aria2 ecosystem

Yes, because the project explicitly provides an aria2-compatible RPC API and a CLI that controls the task lifecycle.

  • The Command Line section lists probe, add, tasks, pause, start, remove, and wait, covering discovery, creation, querying, and state control.
  • The Always in control section says third-party tools can use the RPC API, while URLs, headers, or proxies can be changed during a download without losing progress.
  • HTTP, Magnet/BT, M3U8, FTP, and MPEG-DASH are all listed as supported download types.

However, the README does not specify RPC authentication, the complete API schema, concurrency limits, error codes, or a Python client example. Those details must be verified if the automation depends on a stable interface contract.

  • README: Command Line; excerpt: `ghd probe`, `ghd add ...`, `ghd pause ...`, `ghd start ...`, and `ghd wait ...`
  • README: Always in control; excerpt: `aria2`-compatible RPC API for third-party tools
  • README: One app instead of five; excerpt: `HTTP`, `Magnet/BT`, `FTP`, `M3U8`, `MPEG-DASH`, and `eD2k
ghd probe "https://example.com/a.torrent"
Not stated in the README:Whether RPC requires authentication and which mechanism it uses;The complete RPC methods, parameters, return values, and error codes are not documented in the README;Concurrent task limits, event notifications, and version compatibility policy are unspecified
Yes I run Linux with glibc 2.35+ on an arm64 device. My network is unreliable, and I need to download large Magnet/BT tasks while selecting only files 0 and 3 from a torrent. Does Ghost Downloader 3 fit this workflow?
For: A Linux arm64 user who manages large Magnet/BT downloads on unreliable networks and wants only selected files from torrents

Yes, because the project combines Linux arm64 support, BT/Magnet handling, resumable-download behavior, and torrent file selection in a workflow that directly matches the requirement.

  • About The Project requires Linux glibc 2.35+ and lists arm64 support.
  • One app instead of five explicitly supports Magnet/BT.
  • The Command Line example first uses ghd probe to inspect torrent contents and then uses --select 0,3 to download only selected files.
  • The feature description emphasizes smart chunking, no file merging, and automatic bandwidth detection; the project insights also identify resume support, which fits long-running tasks.

However, BT jobs still depend on seed availability and successful magnet metadata retrieval. The README does not specify DHT, tracker behavior, connection limits, disk preallocation, or tunable smart-chunking parameters, so improved speed on an unreliable network cannot be guaranteed.

  • README: About The Project; excerpt: Linux `glibc 2.35+`, architectures `x86_64` / `arm64`
  • README: One app instead of five; excerpt: `Magnet/BT`
  • README: Command Line; excerpt: `ghd add "https://example.com/a.torrent" --select 0,3 -o ./downloads`
  • README: Fast where it matters; excerpt: Smart chunking without file merging. Auto-detects bandwidth
  • Project insights: key_features; resumable downloads are supported
ghd probe "https://example.com/a.torrent"
Not stated in the README:DHT, tracker behavior, connection limits, and magnet metadata retrieval are unspecified;Whether smart chunking, concurrent connections, and bandwidth policies are configurable is unspecified;BT file integrity checks and disk preallocation behavior are unspecified
It depends I mainly process YouTube and Bilibili videos. I often need to select quality, subtitles, clips, playlists, and multipart episodes, while discovering media directly from the browser and carrying over authentication state. Can Ghost Downloader 3 replace several video download tools?
For: A video creator who needs different qualities, subtitles, clips, and playlists from YouTube and Bilibili

It depends: the feature set is a strong match, but site compatibility still depends on login restrictions, expiring URLs, DRM, and site API changes.

  • The One app instead of five section explicitly lists YouTube and Bilibili, arbitrary quality, subtitles, clip selection, playlists, and multipart episodes.
  • See it. Sniff it. Download it. says the browser extension can list media on a page, hand the task to the desktop app, and carry authentication state over.
  • M3U8 and MPEG-DASH are also supported, making the tool suitable for segmented media rather than only ordinary files.

However, the project insights identify dynamic encryption, DRM, CAPTCHA, login restrictions, and signed URLs as possible causes of failure. The README provides no current per-site success rate, DRM coverage, or detailed login flow, so complete replacement of specialized tools cannot be guaranteed.

  • README: One app instead of five; excerpt: `YouTube` and `Bilibili` with clip selection, any quality and subtitles, playlists and multi-part episodes
  • README: See it. Sniff it. Download it.; excerpt: The extension popup lists every medium on the page
  • README: See it. Sniff it. Download it.; excerpt: authentication state carries over
  • Project insights: common_pitfalls; dynamic encryption, DRM, login restrictions, expiring signed URLs, or site changes may cause parsing failures
Not stated in the README:The current compatibility scope for YouTube and Bilibili is not specified;DRM support is not specified;Supported browsers, the authentication-state transfer mechanism, and cookie security boundaries are not specified
It depends I use an Android 9+ arm64-v8a phone, mainly record live M3U8 streams, and need downloads to continue when the app is in the background. Is Ghost Downloader 3 suitable for this mobile scenario?
For: A mobile user on Android 9+ arm64-v8a who needs background downloads and live M3U8 recording

It depends: the README explicitly covers Android background downloads and live M3U8 recording, but mobile background restrictions may determine real-world continuity.

  • The platform table requires Android 9.0+ and targets arm64-v8a, matching the stated device constraint.
  • Native on every platform explicitly says Android can record live M3U8 streams and keep downloading in the background.
  • M3U8 is listed as a supported download type, and the project insights identify Android background downloading and live recording as supported capabilities.

The uncertainty is that live sources may disconnect, their segments may expire, or authentication may be required. The project insights also note Android power management, file permissions, and background behavior as platform constraints. The README does not explain foreground services, vendor allowlists, reconnect/resume recording, storage locations, or screen-off behavior, so continuous recording cannot be guaranteed on every phone.

  • README: About The Project; excerpt: Android `9.0+`, architecture `arm64-v8a`
  • README: Native on every platform; excerpt: On Android, it records live M3U8 streams and keeps downloading in the background
  • README: One app instead of five; excerpt: `M3U8`
  • Project insights: usage_limitations; Android background tasks, power management, file permissions, and live recording are constrained by the mobile OS
Not stated in the README:Whether Android foreground services are used to maintain background tasks is unspecified;Behavior under different vendor battery-optimization policies is unspecified;Automatic reconnect, continued recording, and segment integrity checks after live-stream interruption are unspecified

✨ Highlights

  • Combines HTTP, Magnet/BT, FTP, M3U8, MPEG-DASH, and eD2k
  • Supports YouTube and Bilibili clips, subtitles, playlists, and episodes
  • Provides an aria2-compatible RPC API and allows changing URLs, headers, and proxies mid-download
  • Supports four platforms: Windows, macOS, Linux, and Android
  • The project has 12,718 stars, 10 contributors, and 5 releases

🔧 Engineering

  • The desktop app takes over browser-extension downloads while carrying authentication state
  • Android can record live M3U8 streams and continue downloading in the background
  • The ghd CLI covers task operations including probe, add, tasks, pause, and wait
  • Smart chunking avoids file merging and automatically detects bandwidth

⚠️ Risks

  • Linux requires glibc 2.35+; systems below that version are outside the support table
  • Qt 6.6+ does not support CPUs without the AVX instruction set
  • The Feature Packs plugin API is not public yet and is still stabilizing
  • A new language requires 60% of desktop text translated; untranslated text appears in English

👥 For who?

  • Individuals or small teams needing one tool for HTTP, BT, FTP, and M3U8
  • Users frequently downloading resources from YouTube, Bilibili, GitHub, or HuggingFace
  • Developers needing aria2-compatible RPC or ghd CLI automation
  • Users on Windows 10+, macOS 13.0+, or Android 9.0+