A Download Manager That Skips aria2 and Builds Its Own Engine in Dart
You've probably got a download manager installed. Maybe it came bundled with your browser, maybe you grabbed something like aria2 years ago and never thought about it again. But have you ever wondered what's actually happening under the hood when a download crawls along at a fraction of your connection speed? Brisk is a download manager that answers that question by throwing out the usual suspects (no aria2, no external utilities) and building its download engine from scratch in Dart.
What It Does
Brisk is a cross-platform download manager with its own custom-built engine. Instead of leaning on existing download libraries or command-line utilities, the engine is written entirely from scratch using only Dart's http package. That's a deliberate architectural choice, and it's the core of what makes the project worth a look.
The app runs on Windows, macOS, and Linux, with distribution through the usual channels: direct releases for Windows and macOS, Flatpak and Snap for Linux users who prefer those, an AUR package for Arch, and a plain tarball if you want to manage things yourself. There's also a separate browser extension repository that integrates Brisk with your browser, plus support for downloading video streams with soft-subtitles. You get download queues with scheduling and a custom hotkey that grabs a URL from your clipboard to start a download.
Why It's Cool
The engine is the headline here, and it's worth understanding why. Brisk doesn't just open a fixed number of connections and hope for the best.
-
Dynamic connection spawning. Downloads start with a single connection, and new connections get added on the fly as the download progresses. The idea is that you only use a higher number of connections when the download actually needs them, rather than blasting your bandwidth with parallel requests from the first byte. That's a smarter approach than the "more connections equals more speed" assumption a lot of tools make.
-
No dependency on aria2. Plenty of download managers are essentially fancy frontends wrapped around aria2. Brisk isn't. Building the engine from scratch means the developers control the entire download path, and it means you're not debugging a stack of two separate applications when something goes wrong.
-
The browser integration is a first-class feature. The extension lives in its own repository, and the README is upfront about a practical gotcha: you'll want to disable other download manager extensions so they don't fight over your downloads. That kind of honesty about real-world friction is a good sign.
-
It respects your platform. Flatpak on Flathub, Snap, AUR, tarballs, native installers for Windows and macOS (both x86_64 and arm64 on the Mac side). That's a lot of packaging work for a project that could have just shipped a single binary and called it done.
-
The clipboard hotkey. A small thing, but if you copy download links regularly, having a global hotkey to fire one off without switching windows is the kind of feature you miss once you've had it.
How to Try It
Getting started depends on your platform, but the install path is short for all of them.
-
Head to the Brisk repository and grab the release for your OS from the latest releases page.
-
On Linux, you've got options. If you're on Flathub, install from there. Snap users can grab it from the Snap Store. Arch users can pull it from the AUR. Otherwise, the tarball works — but check the Linux prerequisites section in the README first, since the tarball has some requirements the packaged versions handle for you.
-
On Windows, if you hit the "Windows protected your PC" warning (you probably will, since this isn't a signed installer from a big publisher), click "more info" and then "run anyway."
-
For browser integration, install the extension from the brisk-browser-extension repository. Then disable any other download manager extensions you have running so they don't intercept downloads before Brisk gets a chance.
Once it's running, you can queue up downloads, schedule them, and use the clipboard hotkey to add URLs on the fly.
Final Thoughts
Brisk is a niche tool with a specific bet: that a purpose-built Dart engine can deliver better download performance than the established utilities everyone else wraps. Whether that bet pays off for you depends on your use case — if you download large files regularly and want fine-grained control over connection behavior, it's worth testing against whatever you're using now. If you're a Dart developer curious about what the language can do outside of Flutter apps, the engine alone makes the repo an interesting read. Either way, it's a solid example of a project choosing the harder path (build the engine yourself) and shipping it across every major platform.
Follow @githubprojects for more developer tools and open source projects.