Motrix Download Manager: aria2 GUI for Desktop
Motrix is worth installing if you want HTTP, FTP, BitTorrent, and magnet-link downloads in one queue instead of a browser download list plus a separate torrent client. Reach for it if you also want a headless Docker instance for a NAS that pairs with the desktop app over MDXP. Skip it if you only need a single-purpose torrent client and don't want to manage plugin permissions.
What is Motrix?
Motrix is a desktop download manager built on a Motrix-maintained fork of aria2, handling HTTP, FTP, BitTorrent, and magnet links through an Electron app for macOS, Windows, and Linux. The same core also runs headless via Docker for NAS boxes, and browser extensions plus an official CLI talk to it over MDXP, a JSON-RPC 2.0 protocol.
Key features of Motrix
- ✓BitTorrent downloads with per-file selection and native magnet-link support
- ✓Built-in tracker list management that auto-updates and health-checks trackers
- ✓SQLite-backed sessions that restore in-progress downloads after a restart
- ✓QuickJS-sandboxed plugins with fine-grained permissions and an in-app marketplace
- ✓Chrome and Firefox extensions that hand off browser downloads in one click
- ✓Official @motrix/cli client for shell use and AI agents, plus a device-code pairing flow for remote and headless instances
- ✓Multiple speed-limit profiles for upload and download caps, plus UPnP/NAT-PMP port mapping
- ✓Support for motrix:// and magnet: URLs, plus .torrent file associations
Installing Motrix on your platform
Download Motrix from motrix.app and pick the package for your OS: on macOS choose the Apple Silicon .dmg unless you're on an Intel Mac, on Windows the NSIS .exe installer is the default with a .zip as a portable option, and on Linux you can use .AppImage, .deb, .rpm, Flatpak, or Snap. The official CLI installs separately with `npm install -g @motrix/cli` (Node.js 22 or later), or from Settings → Integration → Command-line tools inside the desktop app. For a headless NAS or home-server setup, the project publishes a multi-architecture Server image to Docker Hub and GHCR; the included compose.yaml keeps app state separate from downloaded files: ```bash mkdir -p motrix-data downloads sudo chown 1000:1000 motrix-data downloads export MOTRIX_PUBLIC_URL='http://nas.example.lan:8080' docker compose pull server docker compose up -d --wait ``` The standard setup exposes the web UI on port 8080 and MDXP on port 16801; set MOTRIX_PUBLIC_URL to a URL remote clients can actually reach, since the compose files don't fill in a placeholder for you.
What you can do with Motrix
- •Running a headless download box on a NAS or home server, driven over the network by the CLI or paired agent clients
- •Pulling BitTorrent and magnet-link content with per-file selection instead of grabbing an entire torrent
- •Centralizing browser-triggered downloads from Chrome or Firefox into one queue with speed limits
- •Scripting downloads from the shell or an AI agent via @motrix/cli, including NDJSON progress streaming
- •Building a custom plugin (Filename Template, Page Scraper, or a site-specific URL Resolver) with the Plugin SDK
Strengths
- ✓One app covers HTTP, FTP, BitTorrent, and magnet links instead of separate tools for downloads and torrents
- ✓SQLite-backed sessions mean a crash or restart doesn't lose the download queue
- ✓The desktop app and the headless Docker server share the same core, so behavior stays consistent whether you're running it locally or on a NAS
- ✓Official CLI and MDXP protocol make it scriptable for shell workflows and AI agents, not just point-and-click use
- ✓Built-in tracker list management updates and health-checks trackers automatically instead of leaving that to the user
Motrix drawbacks and limitations
- △Motrix Turbo (v2) is a ground-up Electron/React/TypeScript rewrite of v1, so plugins, extensions, and workflows built for the older version need to be re-evaluated against the new MDXP-based architecture.
- △Plugins run in a QuickJS sandbox and must declare host capabilities (notifications, secret storage, FFmpeg detection) up front — a plugin that needs something outside its declared manifest simply can't get it without a new release.
- △First-time browser-extension pairing goes through native messaging with the desktop app; the headless Docker server on its own doesn't provide that pairing step, so remote and agent clients rely on the separate device-code flow instead.
- △Direct HTTP access to the headless server is only appropriate on a trusted LAN — reaching it over the internet or an untrusted network requires setting up a TLS reverse proxy and firewall rules yourself.
- △UI language is Simplified Chinese and English, with more languages only planned, not shipped yet.
Motrix alternatives
Frequently asked questions about Motrix
Motrix is free and open source, released under the MIT license. The desktop app, headless Docker server, CLI, and browser extensions all live in the same open codebase, and release packages include a generated dependency inventory plus an SPDX 2.3 software bill of materials alongside the license texts.
Motrix downloads over HTTP, FTP, BitTorrent, and magnet links, all handled by a Motrix-maintained fork of aria2 bundled with the app. Browser extensions and the CLI talk to the desktop app or headless server using MDXP, an open JSON-RPC 2.0 protocol, so a download queued from a browser or script goes through the same engine.
Motrix ships a headless Server mode with a web UI, distributed as a multi-architecture image on Docker Hub and GHCR for NAS boxes and home servers. It runs without a desktop environment, keeps downloads and sessions in a separate data volume, and exposes the web UI on port 8080 and MDXP on port 16801 by default.
Motrix plugins run inside a QuickJS sandbox and declare the host capabilities they need — notifications, secret storage, or FFmpeg detection, for example — in a manifest; Motrix asks the user before granting access. Plugins are built with the Plugin SDK (create-motrix-plugin and related packages) and distributed as signed .moext packages through an in-app marketplace.
Motrix has Chrome and Firefox extensions (Manifest V3) that intercept downloads a site triggers and hand them to the desktop app instead of the browser's own download list, pairing over native messaging. That pairing flow is specific to the desktop app; the headless Docker server doesn't provide first-time extension pairing on its own.
MDXP (Motrix Download eXchange Protocol) is the open JSON-RPC 2.0 protocol that lets browser extensions, the official CLI, and remote or agent clients talk to Motrix's download core independently of the desktop UI. It matters because it's what lets the same core run as a GUI app or a headless server and still be driven by scripts, plugins, or AI agents through one shared wire format.
The problem it solves
Grabbing a large file, a torrent, and a batch of magnet links usually means juggling a browser's download list, a separate BitTorrent client, and no shared history when either one crashes. Motrix merges all four into one queue. Sessions persist in SQLite, so a killed process or a restart doesn't lose track of what was mid-download, and a browser extension hands off intercepted downloads instead of running two separate apps.
Who should try it — and who should skip
Try Motrix if you run a NAS or home server and want one download queue for torrents, magnet links, and regular HTTP/FTP files that you can also drive from a script or an AI agent over MDXP. It also fits anyone who wants browser downloads handed off automatically instead of babysitting a separate download bar. Skip it if you only ever download torrents and don't need FTP/HTTP handling, a plugin marketplace, or CLI scripting — a dedicated torrent client is less to set up and maintain.
Related repositories
Is Motrix worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of Motrix.
