One file, up to 32 connections.
The engine cuts a file into byte ranges and gives each one its own connection, with a per-site cap and an application-wide budget.
- Up to 32 connections per file
- Per-site and global caps
- Ranges sized at 16 MiB
Version 0.1.0 · live
Splits files across parallel connections and keeps every byte on disk. Pause or restart: it continues where it stopped.
What it does
No account, no cloud, no editor you did not ask for. A focused engine and a Windows-style queue that stays out of the way.
The engine cuts a file into byte ranges and gives each one its own connection, with a per-site cap and an application-wide budget.
A crash-safe manifest records every finished range. Pause, close the app or lose power; the next run reads the bytes already on disk.
HTTP and HTTPS ask for identity-encoded ranges. FTP seeks with REST. A server that answers with a plain 200 is fetched on one connection.
Set one cap for the whole application and one for each download, in KB/s or MB/s. The engine applies the limit across every open connection.
Firefox, Chrome and Edge extensions pass a link to the app over a versioned loopback bridge. No native messaging host and no registry entry.
The tray restores the window, starts or stops the queue, and is the way out. Closing the window hides it; nothing stops downloading.
Get the app
Version 0.1.0 has no packaged installer. Build it once with Node.js, Rust and pnpm, and later updates are a pull and a rebuild.
Platforms and what they need
Browser Extension
Chrome and Firefox extensions are coming soon.
These are the answers the current build can support. If you hit something else, the troubleshooting page is the next stop.
Go to troubleshootingNot yet. The app is at 0.1.0 and builds from source with Node.js, Rust and pnpm. The installation guide covers Windows, macOS and Linux.
Installation requirementsThe part files and a JSON manifest stay on disk. On the next run the engine resumes from the recorded ranges, as long as the server still honours range requests.
Chrome and Firefox extensions are coming soon. They will hand links from the browser to the app over a local bridge.
Yes. Set one cap for the whole application and one for each download, in KB/s or MB/s. The engine applies the cap across every connection.
Not yet. Scheduling, media splitting and a few other download-manager features are still planned. The queue, pause and resume, and the tray work today.
Troubleshooting and known limits