Motrix
An open-source aria2 desktop manager for HTTP, FTP, BitTorrent and magnet tasks, with queues, limits, proxies and request-header controls across Windows, macOS and Linux.
What Motrix does
Motrix is a desktop front end for aria2. It manages HTTP, FTP, BitTorrent and magnet tasks with queues, pause/resume, bandwidth limits, proxies and request headers. It exposes aria2 RPC and task history through a graphical interface, which makes both configuration and credential hygiene important.
Version and platform scope
1.8.19 is the latest formal release listed for the original project, with Windows, macOS and Linux assets covering common x86, x64 and ARM builds. Repository activity or a third-party rebuild does not automatically represent a new stable Motrix release; check the package and upgrade path separately.
Headers, cookies and RPC
Cookie, Referer and authorization headers can reproduce a request that the user already has permission to make. They may also represent an active login session. Keep RPC on a local or controlled address, use a strong secret, restrict firewall sources and clean logs and history after sensitive tasks.
Maintenance note
This page reviews Motrix 1.8.19, aria2, HTTP/FTP/BT/magnet tasks, request headers, RPC boundaries and MIT licensing. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Motrix to this cloud drive
Baidu Netdisk
Save Motrix to this cloud drive
Motrix 1.8.19 aria2 tasks and RPC security guide
Install the package that matches the platform, test a small HTTP task, then configure BT, magnet, limits and proxy settings. Enable RPC only for a clear controlled use case.
Before you start
- Match Windows x86/x64, macOS Intel/Apple Silicon or Linux x86_64/ARM64/ARMv7, and back up existing tasks, settings and unfinished files.
- Prepare separate temporary and completed directories with enough disk space; review the sensitivity of any Cookie, Referer or authorization header before importing it.
- Record current RPC listen address, secret, firewall rules and logging settings before upgrading or adding a remote client.
Installation steps
- 01
Select the 1.8.19 package
Use the Windows EXE, APPX or ZIP, the correct macOS DMG/ZIP or the Linux AppImage, DEB or RPM for the target architecture.
- 02
Set directories and limits
Start with low task concurrency, separate temporary and completed files, and leave enough bandwidth for normal browsing and other services.
- 03
Review RPC and logs
Keep RPC local when remote control is unnecessary. If it is needed, use a unique strong secret, restricted address and firewall source, and avoid recording request headers in verbose logs.
Quick start
- 01
Test HTTP pause and resume
Add a small authorized file, pause it, restart the application and resume, then check the final size and a trusted checksum.
- 02
Inspect a BT or magnet task
Review the file list, destination, upload limit and auto-start policy before accepting a large task or leaving it seeding.
- 03
Import headers carefully
Import only the Cookie, Referer and headers required for the current authorized session, then remove task history and logs that contain sensitive values.
Usage tips
- The formal 1.8.19 package is from 2023, while later source activity or third-party projects require separate package, signature and compatibility checks.
- RPC provides task and file-control capabilities; a weak secret or public listener turns it into a remote control surface.
- Browser handoff extensions have their own publisher, version and site permissions and should be reviewed separately from the MIT application.
Troubleshooting and uninstall
Why does a task have no speed or a magnet have no metadata?
Check the link, trackers, DHT, proxy, firewall, disk and concurrency, then use a small HTTP task to separate network issues from peer-discovery issues.
Why can the RPC client not connect or show an unknown task?
Inspect the listen address, port, secret and access log immediately, stop unknown tasks, rotate the secret and test locally before allowing a restricted source.
- Stop tasks and remove the RPC entryStop downloads and seeding, export only the tasks you need, remove remote clients and secrets, and close unused firewall or proxy ports.
- Remove application dataUninstall the package or remove the portable directory, then decide how to handle aria2 configuration, task databases, logs and temporary segments while retaining verified completed files.
Frequently asked questions
Can Motrix download every protected web video?
It can pass request headers such as Cookie and Referer for an authorized request, but it is not a DRM or account-access tool. Treat cookies as login credentials and clean them after use.
May I expose aria2 RPC directly to the public internet?
Keep it on the local machine or a controlled network, use a strong secret and firewall restrictions, and place authentication in front of any required proxy path.
Why is 1.8.19 still listed when newer commits exist?
A repository commit and a formal release are different artifacts. Check the published package, signature, release notes and upgrade path before treating a newer build as stable.