Download · rDownloader 1.1.0 — GNU GPL v3.0 or later
Run rDownloader where your downloads live.
Choose a native build or a multi-architecture container. One binary carries the web application, scheduler, API and internal runners — open it on the machine and network you configure.
Recommended
Docker · amd64 / arm64
01 — All platforms
Every build of 1.1.0.
Native builds ship the server and the desktop capture agent — Click'n'Load 2, clipboard monitoring, NZB association. On Linux the agent is deliberately headless; the container carries the server only.
Windows
Portable server and capture binaries. The capture agent lives in the tray and takes the NZB file association.
macOS
Native builds for Apple Silicon and Intel, plus a menu-bar capture agent. Autostart runs as a LaunchAgent.
Linux
Native server and a headless capture agent, suitable for a systemd user service on a workstation or NAS.
Docker
Server image with persistent /config and /downloads volumes, PUID/PGID and a health check.
The server binds exclusively to 127.0.0.1 by default. Reaching it from another device is a deliberate configuration step through a TLS reverse proxy — not a default.
02 — Container
One compose file on the NAS.
services:
rdownloader:
image: ghcr.io/degoya/rdownloader:1.1.0
environment:
- PUID=1000
- PGID=1000
volumes:
- ./config:/config
- /mnt/downloads:/downloads
ports:
- "127.0.0.1:8710:8710"
restart: unless-stoppedBundled at pinned versions
ffmpeg, yt-dlp, streamlink, gallery-dl, 7-Zip and par2 ship inside the image.
Deliberately absent
unrar is not included, because it is non-free and 7-Zip reads RAR5. Apprise and rclone are supplied by the operator.
No capture agent
Capture through the PWA, the browser extension, or a desktop agent on another machine.
03 — First run
Four steps to a working queue.
Start and open
Run the binary or the container, then open
http://127.0.0.1:8710.Create the administrator
Register a passkey, or set a password and add an authenticator code.
Allowlist storage roots
Name the directories downloads may reach, then add categories with relative paths.
Connect a capture surface
Install the extension or capture agent, the PWA, or issue a scoped token for CLI, REST or MCP.