How to Route Chrome, Firefox & Edge Downloads to aria2

Replace your browser's slow, single-threaded native download manager with a high-speed 16-connection aria2 engine. Capture cookies, bypass 403 Forbidden barriers, and dispatch downloads directly to your local PC or remote NAS.

1. The Problem with Default Browser Download Managers

Browsers like Chrome, Firefox, Safari, and Edge use basic single-socket HTTP engines for file downloading. When downloading multi-gigabyte files (ISOs, game archives, media files), you encounter three major bottlenecks:

🐌

Single TCP Bottleneck

CDNs and file hosts frequently throttle individual connections to 500 KB/s – 2 MB/s. Browsers cannot open multiple parallel byte streams.

💥

Fragile Resume Capabilities

If your Wi-Fi flickers or the browser crashes, the entire download often corrupts into a .crdownload and restarts from 0%.

🔒

Tied to Browser Lifetime

Closing your laptop or browser terminates the download. aria2 runs as an independent daemon on your machine or home server 24/7.

2. Recommended Browser Extensions

These open-source browser extensions use the Chrome/Firefox downloads.onCreated API to capture download requests and seamlessly redirect them to aria2's JSON-RPC interface:

Extension Name	Supported Browsers	Key Highlights	Official Links
Aria2 Explorer ★ (Recommended)	Chrome, Edge, Firefox, Brave	Integrated AriaNg UI popup, cookie capture, auto-intercept by file size threshold.	Chrome Web Store
Camtd	Chrome, Edge	Lightweight background monitor, context-menu download triggers, custom RPC profiles.	GitHub Repo
Tampermonkey + BaiduExporter	All Web Browsers	Bypasses cloud drive client limitations to generate direct aria2 RPC download links.	Userscript Hub

3. Step-by-Step Configuration Guide

Ensure aria2 Daemon is Running with RPC Enabled

Make sure aria2 is listening on port 6800 with an authentication token:

aria2c --enable-rpc --rpc-listen-all=true --rpc-secret=MySecretToken123 -D

Configure the Browser Extension

Open the Aria2 Explorer settings page:

RPC URL: ws://localhost:6800/jsonrpc (or http://localhost:6800/jsonrpc)
RPC Secret Token: Enter your MySecretToken123
Auto-Capture Downloads: Toggle Enabled
Minimum File Size: Set to 20 MB (prevents tiny image files from triggering aria2)

Automatic Cookie & Referer Header Forwarding

When enabled, the extension automatically inspects the active browser tab's session cookies and referer headers, passing them as --header="Cookie: ..." to aria2. This completely eliminates HTTP 403 Forbidden and session expiry errors on protected download sites!

4. Interactive RPC Connection Checker

Test if your browser can communicate with your local or remote aria2 instance:

RPC Host IP / Domain:

RPC Port:

RPC Secret Token:

5. Troubleshooting & FAQ

Q1: What is the "Mixed Content" error when connecting to a remote NAS?

If you visit a webpage over HTTPS (e.g. https://aria2.org/webui/), the browser prevents connections to an unencrypted http://YOUR_NAS_IP:6800 endpoint. To resolve this, configure an SSL reverse proxy (Nginx or Caddy) with a valid certificate, or use the extension's local background script routing.

Q2: How do I stop aria2 from intercepting small images and PDFs?

In the extension settings, set the File Size Filter to at least 20 MB or 50 MB. Any file smaller than this threshold will download through Chrome/Firefox's standard native downloader.

Q3: Can I send downloads from my work laptop to my home NAS?

Yes! Expose your home aria2 RPC via Cloudflare Tunnel or an Nginx SSL reverse proxy, enter the remote domain in your browser extension, and every download you initiate will be downloaded directly by your home NAS server at full speed.