agalwood/motrix

A full-featured download manager.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on August 17th, 2026
Created on December 18th, 2018
Open Issues & Pull Requests: 781 (+0)
Number of forks: 4,968
Total Stargazers: 54,146 (-1)
Total Subscribers: 489 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.9 days
Mean response time: 188.0 days
90th percentile: 643.2 days
Tracked items: 115

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 125
New in 7 days: 16
Closed in 7 days: 4
Avg open age: 773 days
Stale 30+ days: 109
Stale 90+ days: 102

Recent activity

Opened in 7 days: 16
Closed in 7 days: 4
Comments in 7 days: 9
Events in 7 days: 14

Top labels

  • enhancement ✨ (77)

Detailed Description

Motrix is a full-featured desktop download manager that supports HTTP, FTP, BitTorrent, and magnet links across Windows, macOS, and Linux.

The tool addresses the need for a straightforward way to manage downloads from multiple sources without unnecessary complexity. Motrix separates its download core from the user interface, allowing it to run either as a desktop application or as a headless server. Communication between the UI, browser extensions, and command-line tools happens through MDXP, an open protocol built on JSON-RPC 2.0. Plugins run in isolated sandboxes to maintain stability and security.

Motrix suits developers and users who want a single application to handle diverse download types without bloat. The headless server mode makes it particularly valuable for NAS devices and home servers, where a web UI provides remote access. The project offers flexibility in deployment: run it as a traditional desktop app on consumer operating systems, or deploy it on Node.js or Docker for server environments. The separation of download logic from presentation means the same core powers both modes, reducing maintenance overhead.

Development activity shows consistent engagement with the codebase through regular commits addressing both features and stability. The project maintains active communication with users through issue responses and documentation updates. Testing infrastructure receives attention, with beta releases carefully staged and migration paths documented to help users transition between versions. The maintainers provide detailed release notes and explicitly warn users about data backup requirements during beta testing, indicating a cautious approach to stability.