GitHub

Manual

Using Plugins

Plugins extend what Motrix does with your downloads: renaming files automatically, resolving download pages to real file links, reacting when downloads finish, and more. Each plugin runs in an isolated sandbox and can only do what you allowed it to at install time — the Plugins page in the sidebar is where all of this lives.

Motrix ships with three plugins already installed — see Built-in plugins.

Installing from the marketplace

The Available plugins section on the Plugins page lists the official plugin registry. Each entry shows the author, version, a “what it does” summary, a Permissions preview, and a compatibility badge; the best ones carry a Featured badge. Click a plugin for details, then Install.

Note

The permissions shown in the registry are a preview. The consent prompt you confirm is always based on the manifest inside the actual plugin package.

Installing from anywhere else

Plugins also come as .moext files. Click Add plugin and give it any of:

  • A GitHub address — owner/repo[@tag], installing from that repository’s release.
  • A URL — a direct link to a .moext bundle.
  • A local file — pick a .moext or just drop it onto the dialog.

The input auto-detects which kind you pasted. Installation is deliberately two-step: first Check this plugin, then review what it asks for, then Allow and install.

The consent screen — read it

Before anything is installed, Motrix shows exactly what the plugin wants:

  • Required permissions and Optional permissions, each in plain language — “Read websites”, “Use FFmpeg”, “Manage your downloads”, and so on.
  • Host access — which sites the plugin may reach. This is enforced while the plugin runs: requests outside the listed sites are blocked. A plugin that asks for any URL gets a red Broad host access warning and deserves extra scrutiny.
  • Whether it calls commands in other plugins, and the exact source it’s being installed from.

Caution

Plugins from outside the registry are marked not verified. Only continue if you trust the author and expect the plugin to use the access listed. If FFmpeg is required and missing, Motrix blocks the install and points you to Settings → Integration → Media tools.

Upgrades get a lighter prompt: Changes since last consent shows only what’s new — added permissions, new host access, new public commands — so you review the delta, not the whole list again.

Managing installed plugins

Each installed plugin is a card with a status and a plain-language safety line (for example, “It only saves its own settings and does not read any websites”). Click through for the detail page:

  • Overview — status, health, and recent issues.
  • Settings — the plugin’s own options, generated from its manifest.
  • Access — what the plugin can already do; grant or review optional permissions here.
  • Logs — behind the small scroll icon at the right of the tab strip: live output with a level filter, Copy, and Clear. Verbose mode captures full URLs and headers for one hour — use it for debugging, carefully.

The enable toggle turns a plugin off without uninstalling. Uninstall removes the plugin and its data.

Updates

Check for updates on the Plugins page scans the registry. Updated plugins show Update available with a one-click update; some updates finish after a restart. Built-in plugins update through their own consent dialog and can always be rolled back with Revert to bundled version.

Handy to know

A motrix://plugins/<id> link — for example from a plugin’s website — opens that plugin’s marketplace page inside Motrix. It only navigates; it never installs anything by itself.

Want to build your own? Start at Developing plugins.