Item logo image for Add Remote Torrent

Add Remote Torrent

4.7(

48 ratings

)
ExtensionWorkflow & Planning5,000 users
Item media 5 (screenshot) for Add Remote Torrent
Item media 1 (screenshot) for Add Remote Torrent
Item media 2 (screenshot) for Add Remote Torrent
Item media 3 (screenshot) for Add Remote Torrent
Item media 4 (screenshot) for Add Remote Torrent
Item media 5 (screenshot) for Add Remote Torrent
Item media 1 (screenshot) for Add Remote Torrent
Item media 1 (screenshot) for Add Remote Torrent
Item media 2 (screenshot) for Add Remote Torrent
Item media 3 (screenshot) for Add Remote Torrent
Item media 4 (screenshot) for Add Remote Torrent
Item media 5 (screenshot) for Add Remote Torrent

Overview

Add magnets and .torrent URLs to remote clients. Multi-server, local-only settings.

Add Remote Torrent is a browser extension for power users who manage remote file-transfer clients. It streamlines adding new transfers (via magnet links or .torrent file URLs) to various client WebUIs. It supports multiple server profiles, giving you a centralized experience directly from your browser. Privacy and security: all server configurations are stored locally on your device and are never transmitted to external servers. It also works with private trackers by fetching the .torrent file content in the browser (with your session cookies) before sending it to your client when needed. Key features: - Add via magnet links or .torrent URLs - Multiple server profiles (different clients / different seedboxes) - Right-click context menu “send to…” per server - Optional on-page link catching / quick add - Per-server defaults (tags/categories/directory/paused; varies by client) - URL-based rules to auto-select a server by site Reporting issues: If you encounter a bug, please open an issue on GitHub: https://github.com/jgkme/Add-Remote-Torrent/issues Please include: - Extension version - Torrent client name + version - Steps to reproduce (what you did / expected / what happened) - Exact error text from the popup under “Last Action” For deeper logs: - Options page → Debug & Log Settings → enable content-script + background-script logs - Reproduce the issue - Options page → Inspect → Console → copy relevant lines - Please remove sensitive info (passwords/tokens/IPs) before posting Recent updates: v0.4.59 (2026-08-13): Fix / Feat: Fix on-page link catching when Chrome site access is specific sites only, not On all sites (#67). v0.4.58 (2026-08-12): Fix / Feat: Clarify ruTorrent private-tracker URL-add failures instead of dumping noty() JS into Recent Activity (#70). v0.4.57 (2026-08-10): Fix / Feat: Fix ruTorrent 401 by preferring browser session auth and only retrying Basic Auth after Unauthorized (#69). v0.4.56 (2026-08-08): Fix / Feat: Fix Chrome link catching when a stale <all_urls> content-script registration survives upgrades (#67). Build: Chrome + Firefox release artifacts for v0.4.56. v0.4.55 (2026-08-08): Fix / Feat: Show Site access granted/missing per server (Options + Dashboard) with Grant access; link-catching site-access status (#66). v0.4.54 (2026-08-08): Fix / Feat: Private-tracker .torrent download via page session (fixes HTTP 403); ruTorrent Basic Auth for seedboxes; re-request host permissions on settings import (#66). v0.4.53 (2026-08-08): Fix / Feat: Fix ruTorrent crash when browser-session .torrent download fails (Buffer.from null / Received type object); clearer cookie/session Recent Activity errors for private trackers (#66). v0.4.52 (2026-08-01): Feat: Advanced Add remembers your last tags, category/label, and download directory per server after a successful add. Fix: Advanced Add tag prefill now uses the server profile tags field (with fallback for older defaultTags data). Feat: Label→directory map applies when the dialog opens for the initially selected category, not only after you change the dropdown. Docs: README product landing (badges, features, client list); GitHub topics and store homepage metadata. Chore: Dependency updates (webpack, webpack-cli, postcss); bun test for confirmAdd defaults helpers. v0.4.51 (2026-08-01): Fix: Choosing a download directory from the right-click context menu now also assigns the uniquely mapped category/label (qBittorrent and other category-aware clients). Ambiguous mappings (multiple categories → same path) are left alone. Thanks @peter-fillmore (#64). v0.4.50 (2026-07-24): Chore: Dependency updates (webpack, Tailwind CSS, PostCSS, terser, and related build tooling). Security: Transitive dependency overrides to clear bun audit findings. v0.4.49 (2026-07-04): Fix: On-page link catching requests site access when enabled—works immediately without a browser restart (#63). Chore: Babel 8 dev dependency bump. v0.4.48 (2026-05-25): Feat (qBittorrent): RSS Reader — feeds, articles, double-click add, download rules on server; import feeds to extension auto-add. Feat: Per-server delete torrent with files (qBittorrent, Transmission, Deluge, rTorrent). v0.4.47 (2026-05-25): Fix (MV3): One background bundle—no broken lazy chunks; Options/Popup load correctly after reload. Fix (qBittorrent): v5+ start/stop API for pause/resume after add. Feat: Torrent status/actions in popup; dashboard per-server torrent list and filters (recent/active/all). Fix (Dashboard): Server list and responsive manage-torrents layout. v0.4.46 (2026-05-22): Fix: Per-server sessions for major non-qBittorrent clients (multi-profile safe). Feat: Transmission completion notify; Flood/Porla richer adds; Synology API version + opt-in auto-resume. v0.4.45 (2026-05-22): Feat (qBittorrent): fetchMetadata magnet file lists; Web API Basic auth; rotate/delete API key on server; global speed limits in popup (2.16+). Docs: README and Options hints for auth and metadata APIs. v0.4.44 (2026-05-22): Feat (qBittorrent): Options tools to sync/import categories, sync tags, and sync default save path; import categories.json locally with optional push via Web API. Feat (qBittorrent): Popup Search provider using installed qBittorrent Search plugins (active server). Feat (qBittorrent): Confirm-add skip checking, sequential download, first/last piece priority, rename, free-space hint (Web API 2.15.2+), and metadata API fallback for file selection. Feat (qBittorrent): Web API 2.14+ add feedback (added_torrent_ids) and add-time file priorities for uploaded .torrent files. Fix (qBittorrent): Search job ID matching, partial results on slow searches, host permission preflight, clearer sync/import errors. Security: Escape search plugin names in Options. Docs: FAQ for categories sync/import and qBittorrent Search. Build: Generated release artifacts for v0.4.44. v0.4.43 (2026-05-22): Perf: Lazy-load client API handlers (smaller service worker). Perf / Privacy: Link-catching content script only when enabled in Options; preserved setting for existing users; optional host permissions unchanged (LAN/VPS/custom URLs still work). Fix: activeTab clipboard quick-add; advanced dialog after service worker restart. Docs / Chore: Privacy & store metadata; dev dependency updates. v0.4.42 (2026-05-22): Fix (Shortcuts): Quick-add-from-clipboard has no default shortcut (was Ctrl+Shift+V / ⌘⇧V, which blocked Chrome paste-without-formatting). Assign at chrome://extensions/shortcuts if wanted; clear the old Ctrl+Shift+V binding there after update if paste-without-formatting still fails (#59). v0.4.41 (2026-05-13): Fix (Synology Download Station): Restore SID-only Web API auth like v0.4.23 (no enable_syno_token / SynoToken on requests). Newer builds had added SynoToken flow; some DSM setups responded with API 105 or failed adds until reverted—validated against working v0.4.23 behaviour. Fix / UX (Synology): Clearer user-visible messages for common Synology API error codes (e.g. 105 permission). Feat / Fix (Diagnostics): Persist last connection error per server for offline checks; dashboard Show Details lists it; failed adds append a short technical hint to “Last Action” / notifications when available. v0.4.40 (2026-05-12): Fix (qBittorrent): Accept successful auth/login with an empty body or HTTP 204 (Web API 5.2+), not only legacy Ok. text—fixes false “connection failed / CSRF” errors when username and password are correct. v0.4.39 (2026-05-13) Fix (qBittorrent): Cookie-based Web UI login is now tracked per server profile instead of one global session. After logging into one qBittorrent server, calls to another profile no longer skipped auth/login, which previously caused HTTP 401 on the API and confusing messages about needing a Web API key (common with multiple seedboxes and qBittorrent 5.2+). Fix (qBittorrent): Refined unauthorized and connection-test wording so users check username/password and CSRF first; the optional Web API key (5.2+) is described only as a fallback when cookie access still cannot reach the API. Build: Generated release artifacts for v0.4.39. - v0.4.38 (2026-05-08): Deluge — apply custom label/category after adding (Label plugin); create missing label; retry for Deluge 2.x timing. - v0.4.37 (2026-05-05): qBittorrent — Web API 2.14+ torrents/add JSON responses (incl. 202/409) with legacy “Ok.” fallback; optional Web API key (Bearer); clearer auth vs network errors; startup status checks; packaging/signing fixes. Supports qBittorrent 5.2. Full changelog: https://github.com/jgkme/Add-Remote-Torrent/releases

Details

  • Version
    0.4.59
  • Updated
    August 22, 2026
  • Offered by
    jayapc87
  • Size
    215KiB
  • Languages
    English
  • Developer
    Email
    jgkme@jeya.my
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps