Motrix 2.1.1

English | 简体中文

Motrix 2.1.1 increases the configurable download concurrency and fixes false
path conflicts during legacy task migration.

Changes since 2.1.0

• Raise the simultaneous-download setting from 1–100 to 1–200, keeping
  the default at 10. Values above 100 remain intact after saving other
  settings and restarting the application. Addresses the requested limit
  increase in #2439.
• Stop treating display names and output hints from unresolved legacy magnet
  tasks as owned file paths. Multiple magnet tasks can be imported without
  false path conflicts, and those hints no longer block unrelated HTTP or
  BitTorrent task activation. Existing-file protections for tasks with actual
  output ownership remain in place. Fixes
  #2437.
• Update form resolvers, virtual lists, layout and icon dependencies, along with
  Biome and pnpm. Update electron-builder to 26.18.1 and electron-updater to
  6.8.12, including fixes for differential-download redirects and cached
  block maps. vscode-jsonrpc remains at 9.0.3, Electron at 45.1.0, and
  the bundled engine at aria2 1.37.0-motrix.21.

Downloads and updates

Desktop packages support macOS 13 or later, Windows 10 or later, and Linux,
with native x64 and ARM64 builds. No 32-bit desktop packages are provided.
macOS DMG and ZIP packages are signed and notarized. Windows NSIS installers
and ZIP archives are unsigned and may trigger SmartScreen; download them from
the official GitHub Release.

Stable publication updates both latest*.yml and beta*.yml feeds to 2.1.1.
Flatpak bundles and Native Host companions are separate downloads. Snap builds
first reach latest/edge; the same verified amd64 and arm64 revisions are then
promoted through candidate to stable.

Server images use the immutable tags docker.io/motrixapp/motrix-server:2.1.1
and ghcr.io/agalwood/motrix-server:2.1.1. After public multi-platform runtime
verification, the 2.1, 2, stable, and latest aliases advance to this version.

Back up your profile and download files before upgrading. Users migrating
from Motrix v1 should follow the
migration guide
and retain their original profile and engine database backups.

Known limitations

BitTorrent hash checks during restart or recovery still share the download
concurrency quota. Raising the limit does not add parallel hash checking or
separate verification scheduling. Tasks that have entered seeding remain
excluded from the quota with the default bt-detach-seed-only=true setting.

Full changelog

What's Changed

• fix(migration): avoid reserving unresolved magnet path hints by @agalwood in #2458
• fix(settings): raise concurrent download limit to 200 by @agalwood in #2460
• chore(release): prepare 2.1.1 by @agalwood in #2461

Full Changelog: v2.1.0...v2.1.1