Skip to content

Frequently asked questions

Why does DownloadIt require a customized Loader?

Section titled “Why does DownloadIt require a customized Loader?”

DownloadIt uses Firefox internal APIs and the legacy bootstrapped-XPI lifecycle to integrate with browser chrome, download prompts, processes, and privileged request context. A normal WebExtension cannot provide the same integration surface.

No. DownloadIt is not an AMO WebExtension. Install a compatible Loader, then install the XPI from a file in about:addons. Firefox Developer Edition and Nightly can use Bootstrap Loader instead of the customized userChrome.js-Loader.

Not currently. The website links to the Nightly pre-release built from master. The button and installation page label it as pre-release software.

No. DownloadIt publishes a legacy update manifest, but the current Loader does not check or install it. Download a newer XPI, install it over the existing copy, and restart Firefox when prompted.

Windows and non-sandboxed Linux Firefox installations are supported. Bundled Aria2Next on Linux requires x86_64. macOS, Snap Firefox, and Flatpak Firefox are outside the current support scope.

No. The native Firefox downloader is always available. External tools add protocol, queue, automation, or command-line capabilities according to their integration route.

DownloadIt ports selected FlashGot download-bridge behavior to current Firefox. On Windows it can use a packaged FlashGot helper to discover compatible managers, but DownloadIt has its own version line, settings, native provider, local protocol integrations, and custom downloader system. It does not yet implement every historical FlashGot feature.

It can pass Cookie data to capable external routes when Send cookies is enabled. The Firefox provider instead uses Firefox’s native cookie jar. Turn Cookie forwarding off unless the external tool needs the authenticated request context.

No. DownloadIt Links collects explicit page links. Network media sniffing and media element source discovery are not implemented.

Use GitHub issues. Include reproducible steps and environment versions, but remove private URLs, filesystem paths, RPC secrets, and Cookie data.