Aria2 Explorer hands Chrome downloads to an aria2 daemon over RPC

The extension is a front end for a daemon that has to be running already

Aria2 Explorer is an extension for Chromium based browsers that exports URLs to aria2 so the download completes under aria2 instead of the browser's own downloader. The stated purpose is plain: take over the download process and lead to what the project calls a high-speed download experience. The interesting part is that the extension contains no download engine. It is a bridge, and the thing on the other end of the bridge is an aria2 process that the user starts and configures themselves.

That constraint defines the audience. The extension is for someone who has already decided that aria2's multi-connection and segmentation behaviour is worth the setup, and who wants the browser to stop fighting it. For a reader who just wants fast downloads, a plain browser download or a dedicated desktop download manager is a smaller commitment. The extension bundles a frontend for aria2 tasks, so you do not have to open a separate management tab, but the daemon itself is a separate piece of software you install and run yourself.

Auto-capture routes browser tasks into aria2 by domain, extension and size

The interception path is the core of the tool. When auto-capture is enabled on the options page, the extension watches for download tasks the browser starts, shows a capture notification, and can handle magnet links. The toggling is deliberate rather than automatic: the default shortcut is Alt plus A, so capture can be switched off for a single download without editing settings.

Filtering is where the design gets specific. Intercepted tasks can be filtered by domain, file extension or file size, and the project documents a strict priority order for those filters: domain first, then file extension, then file size, and white-list rules beat black-list rules. That ordering matters in practice, because a rule set that mixes the three criteria behaves differently from what a user expects if they assume the last matching rule wins. Before each download, the aria2 options can be configured manually, so a user can adjust per-task settings instead of living with one global profile.

RPC server and download path are chosen by matching URL patterns

Aria2 Explorer is not tied to one aria2 instance. The second feature in the project list is auto-selection of the aria2 RPC server and download location by matching the downloading URL against preset URL patterns. A user can therefore keep a local daemon for local work and a remote one for large transfers, and have the extension pick the right target based on the URL. The same mechanism covers the download directory, since the destination is selected in the same step.

This is the piece that makes multi-machine use possible, and also the piece that needs the most care. A pattern that matches too broadly will send traffic to a host you did not intend, and an RPC endpoint that is reachable from the browser has to be reachable from wherever the extension runs. The extension supports falling back to downloading URLs through the browser automatically if aria2 is disconnected, which keeps a download from failing outright, at the cost of the speed the whole setup was for.

AriaNG Enhanced is embedded, and settings sync to a cloud account

The built-in management frontend is AriaNG Enhanced, and it can be presented in several ways: as a popup, in a new tab, in a new window, or in a side panel. That choice is a small thing that matters for daily use, since the side panel and popup suit quick status checks while a tab suits managing a large queue.

Two other pieces of the feature set deserve a mention. A badge icon on the extension shows aria2 download status, so the state of the daemon is visible without opening the frontend. And the extension synchronises and stores all of its settings, both its own and AriaNG's, on the cloud, which means the configuration can move between machines. The privacy policy states the scope: the extension captures download tasks and related website cookies from the browser so it can connect to the user's own aria2 server, and any connection and configuration information for aria2 is stored locally or optionally uploaded to the logged-in cloud account. It states that no personal data or network activity is collected or shared with third parties. The cookie access is the part a security reviewer should read twice, since the extension asks the browser for site cookies on your behalf.

Running aria2 with RPC enabled and pointing the extension at it

There is no installer to run. The project documents a four-step procedure, and the only command in it is the one that starts the RPC interface. On Windows, the project points at a downloadable Aria2 Manager and asks you to run Aria2Manager.exe. On other platforms, you download the Aria2 utility from the aria2 releases page and start the daemon in a terminal with RPC enabled:

aria2c --enable-rpc

That single flag is the whole handshake, and the documentation does not specify the RPC port, secret token or bind address, so those details are left to the aria2 side of the setup. After the daemon is up, you install the extension from the Chrome Web Store or the Microsoft Edge add-ons page, open the options page, enable auto-capture, and configure the rest as needed. The extension then starts routing browser downloads into the daemon. A second path exists for people who already use aria2: the extension also accepts download requests sent from other extensions, and there is a documented JSON message format for that.

Other extensions can push download items through Aria2 Explorer

The integration point is worth examining because it is the cleanest way to script against the tool. A sending extension constructs a download item object with a url, a filename, a referrer and an options object whose keys are passed straight through as aria2 RPC options, then sends a chrome.runtime.sendMessage to the Aria2 Explorer extension id. The documented example looks like this:

const downloadItem = {
    url: "https://sample.com/image.jpg",
    filename: "image_from_sample.jpg",
    referrer: "https://sample.com",
    options: { 
        split: "10", // aria2 RPC options here
        xxxxx: "oooo"
    }
}

chrome.runtime.sendMessage(`Aria2-Explorer extension ID`, downloadItem)

The options object is passed through uninterpreted, which is a strength and a risk in one design. You can set any aria2 option the daemon accepts without the extension needing to know about it, but a wrong key is passed straight to aria2 too, and the example even includes a placeholder key to show the shape. The referrer field is how a downloaded resource keeps the page it came from attached, which matters for hosts that check it.

Context menu extraction, shortcuts, languages and the limits of the approach

The extension also reaches beyond the browser download button. A context menu entry batch exports webpage resources, covering image, audio, video and magnet links from the page you are looking at. That is a different use case from aria2 integration: it turns a page into a download list, which is what people running a local mirror or an asset collector want. Options page shortcuts cover saving, resetting, downloading and uploading, with Alt plus S, Alt plus R, Alt plus J and Alt plus U as the defaults. The interface ships in zh-CN, zh-TW, en, fr, ja, ko, it, ru, uk, cs and es.

The limits are real. Anything the browser itself refuses to fetch, such as DRM protected streams, is out of reach because the extension intercepts links rather than the media pipeline. The extension also does not replace the daemon: without a running aria2 it falls back to browser downloads, so the main benefit disappears. And a browser extension that can read download tasks and site cookies is a different security posture from a desktop application, which is a decision about your environment rather than about the code. The project is BSD 3-Clause licensed, and the last push was on 2026-10-06 with release v2.8.3 on the same day, after v2.8.2 in July and v2.8.1 in May, so releases arrive a few times a year rather than on a fixed schedule.

Editorial conclusion

Adopt Aria2 Explorer if you already run aria2 on a reachable host and want the browser to hand over large downloads automatically, and skip it if you have no aria2 daemon, if you need DRM-protected streams, or if an extension with access to download tasks and cookies does not fit your security policy. Before installing, verify that aria2c accepts remote RPC calls on your network, since the extension's only job is to drive that interface, and check the domain and file-extension filters on the options page before turning on auto-capture, because the default behaviour intercepts every download the browser starts.

Frequently asked questions

Official sources

1. alexhua/Aria2-Explorer on GitHub
2. License: BSD-3-Clause
3. Project website
4. README
5. Releases