Fast, resumable downloads for Linux.
Tug pulls every file over many connections and picks up exactly where it stopped, after a pause, a crash or a dropped connection.
Features · Install · Status · Architecture · Build · Contributing
tug-sizzle-1080p.mp4
The video runs Tug's interface on simulated downloads, from a file's live connections to a download that the browser hands over.
Tug is a download manager for Linux, made for KDE Plasma first. Its keyboard-first interface shows what each download does, down to each connection.
- Many connections per file. Up to 32, and 8 by default. When a connection finishes its part, Tug splits the largest part that remains, so every connection stays busy to the end.
- Resume after a stop or a crash. Tug saves its place every 2 seconds, next to the file. The data goes to a
.partfile, and Tug renames it only when the download is complete. - Built for flaky servers. A failed connection tries again at once, then after a delay that doubles up to 30 seconds. Tug learns how many connections each server accepts.
- Web links and torrents. HTTP(S) and FTP(S), and magnet links and
.torrentfiles. Tug checks certificates against the system's store. For a torrent, you choose the files and see each peer. - From the browser. The extension hands each download to Tug with its referrer, cookies and User-Agent, so a signed-in download works. By default, Tug asks first, and it leaves the sites that you list to the browser.
- From anywhere else. Paste or drop links into the window, or run
tug add <link>in a terminal. The system can open magnet links and.torrentfiles with Tug.
- A queue. Set how many downloads run at once, and drag them into the order you want.
- Speed and time. Turn a speed limit on in one click. Set a lower limit for the hours you choose, or let downloads run only on a schedule.
- Options for each download. Give a download its own folder, connections, speed limit, name and headers when you add it.
- The inspector. A map of the file's parts, each connection's speed, bytes and status, the server's address, round trip and CDN, and the engine's log.
- A dense table. Pick the columns, sort on any of them, and set their widths. Search, saved views and file types narrow the list.
- Many downloads at once. Select with Shift and Ctrl, then pause, resume, remove or move them in one action.
- A tidy list. Clear finished takes the finished downloads off the list. Remove… can delete the files too, and a right-click on a download opens all of its actions.
- The keyboard. Ctrl+K opens the command bar, and the keyboard shortcuts dialog lists the rest.
- A tray icon with a progress ring. Close the window, and Tug stays in the tray.
- Notifications with Open and Show in folder, and download progress on the task manager.
- Light and dark themes that follow the system.
- Rust with
unsafeforbidden. CI pins each action by SHA, and cargo-deny, cargo-audit and OSV scans gate every change. - Tug pins the engine to one reviewed commit, and the engine's tests run offline against a local server that injects faults.
- Details are in SECURITY.md.
Tug runs on 64-bit Linux, as an AppImage or a Flatpak. Each release has an AppImage and a Flatpak bundle, and Tug's Flatpak repository gets the same version. To use the browser extension, install the AppImage: from inside its sandbox, the Flatpak can't connect a browser to Tug.
-
Download
Tug_<version>_amd64.AppImagefrom the newest release. -
Make it executable, and start it:
chmod +x Tug_*_amd64.AppImage ./Tug_*_amd64.AppImage
Tug has its own signed Flatpak repository, and each release adds its version there. Add the repository once, then install Tug. It uses the GNOME 51 runtime from Flathub.
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak remote-add --if-not-exists tug https://andymai.github.io/tug/tug.flatpakrepo
flatpak install tug io.github.andymai.TugThe remote-add asks for your password, because it changes the whole system. Bazaar before 0.10.0 doesn't read a remote of one user. If you installed the bundle before, run flatpak uninstall --user io.github.andymai.Tug first, or the bundle keeps starting in place of the repository's Tug. Your downloads and settings stay.
After that, Bazaar and other Flatpak stores list Tug, and flatpak update keeps it current. A store can also install it from io.github.andymai.Tug.flatpakref.
Each release also has the bundle io.github.andymai.Tug.flatpak, for an install without the repository. A bundle doesn't update.
The extension hands your browser's downloads to Tug, with the cookies that a signed-in download needs. It also adds Download with Tug to the menu of each link.
For Chrome, Chromium, Brave, Vivaldi or Edge (version 120 or later):
- Download
tug-extension-chromium.zip, and unzip it into a folder that you keep. - Open the browser's extensions page, for example
chrome://extensions, and turn on Developer mode. - Click Load unpacked, and choose the folder.
- Run
./Tug_*_amd64.AppImage browsersonce. It connects Tug to each browser that ran at least once, and Tug does the same at each start.
To update the extension, unzip the new release into the same folder. Then click the reload button on the extension's card. A browser from Flatpak also needs permission to reach Tug outside its sandbox: the browsers command prints the flatpak override command that gives it.
Firefox (version 128 or later) keeps an add-on after a restart only when Mozilla signed it. To try the extension until the next restart:
- Download
tug-extension-firefox.zip. - Open
about:debugging#/runtime/this-firefox, click Load Temporary Add-on…, and choose the zip.
By default, Tug asks before it takes a download from the browser. To change that, use Ask before each browser download in Settings → Browsers. The extension leaves downloads from private windows, and files under 1 MiB, to the browser.
Tug is before 1.0. Each merged feature or fix cuts a release, so releases come often.
browser extension ──► tug-host ──► local socket ──┐
▼
desktop app (Tauri 2, React) ──► tug-core ──► download engine (pinned)
| Path | Role |
|---|---|
crates/tug-core |
Transfers, the library, the queue, settings and the SQLite store. It is the only crate that reaches the engine, and it maps the engine's types into Tug's own. |
apps/desktop |
The React interface and the Tauri shell, which builds the tug binary. |
crates/tug-ipc |
The local socket. It keeps one Tug for each session, and it serves tug add and tug list. |
crates/tug-host |
The browser's native messaging host. It passes the extension's downloads to Tug over the socket. |
apps/extension |
The browser extension, from one source for Chromium browsers and Firefox. |
design/, brand/ |
The design system's tokens, and the mark, icons and wordmark. |
You need Rust (rust-toolchain.toml pins the version), a C compiler, and Node.js 24 or later with pnpm. You also need the development packages for WebKitGTK and GTK. On Ubuntu:
sudo apt install libwebkit2gtk-4.1-dev libgtk-3-dev libsoup-3.0-dev \
libjavascriptcoregtk-4.1-dev libayatana-appindicator3-dev librsvg2-devThen build and start Tug:
git clone https://github.com/andymai/tug
cd tug
pnpm install
pnpm --filter @tug/desktop exec tauri build --no-bundle
cargo build --release --locked -p tug-host
./target/release/tugtug-host connects the browser extension to Tug, and Tug looks for it next to tug.
To build the browser extension, run pnpm --filter @tug/extension build. It writes apps/extension/dist/chromium, dist/firefox and dist/chrome-web-store, the Chromium build without key for the store. See CONTRIBUTING.md for the tests, the commit hooks and the checks that CI runs.
GPL-3.0-or-later. Tug's download engine is Mister Download Manager by Ahmed Nefzaoui, also GPL-3.0-or-later. Tug is an independent project.