Version 0.1.0 · live

Pick up whereit stopped.

Splits files across parallel connections and keeps every byte on disk. Pause or restart: it continues where it stopped.

Coming Soon See what it does
  • Windows
  • macOS
  • Linux

What it does

The hard part is finishing.

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.

Segmented transfers

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
Resume

Resume, not restart.

A crash-safe manifest records every finished range. Pause, close the app or lose power; the next run reads the bytes already on disk.

  • Manifest beside the part files
  • Overlaps and out-of-order ranges rejected
  • FTP REST offsets for the same job
HTTP, HTTPS and FTP

Range requests where they work.

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.

  • Range-first requests
  • FTP data connection per range
  • One-connection fallback
Limits

A ceiling you choose.

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.

  • Global and per-download caps
  • KB/s or MB/s
  • Applied per connection
Browser hand-off

Send links from the browser.

Firefox, Chrome and Edge extensions pass a link to the app over a versioned loopback bridge. No native messaging host and no registry entry.

  • Right-click hand-off
  • Firefox video button
  • Chrome and Edge build
Tray

Close the window, keep the queue.

The tray restores the window, starts or stops the queue, and is the way out. Closing the window hides it; nothing stops downloading.

  • Queue keeps running
  • Start and stop from the tray
  • Quit from the tray

Get the app

The source is the release.

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.

Coming Soon

Windows, macOS and Linux · no account · no telemetry

Platforms and what they need

  • Windows 10 and 11WebView2 runtimeTuned targetSteps
  • macOS 11 or laterUniversal buildBuilds from sourceSteps
  • Major distributionsWebKitGTKBuilds from sourceSteps

Browser Extension

Hand off links from your browser.

Chrome and Firefox extensions are coming soon.

  • ChromeComing Soon
  • FirefoxComing Soon
  • EdgeComing Soon
  • BraveComing Soon

Straight answers.

These are the answers the current build can support. If you hit something else, the troubleshooting page is the next stop.

Go to troubleshooting
Is there an installer?

Not 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 requirements
What happens if a download is interrupted?

The 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.

Which browsers can send links to the app?

Chrome and Firefox extensions are coming soon. They will hand links from the browser to the app over a local bridge.

Can I limit the download speed?

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.

Is scheduling available?

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