Every release.

A small patch release. Two fixes, no behaviour changes — both are things in the library view that were drawn wrongly rather than working wrongly.

A long save path no longer pushes the library sideways

Expanding a torrent saved somewhere with a long path gave the list a horizontal scrollbar and scrolled the whole pane, taking the name column's figures off the left edge with it.

The path was always meant to shorten with an ellipsis and keep the full value in its tooltip. What was wrong sat above it: a column of text will only shorten if everything containing it agrees to give way, and two levels of that chain did not. So the shortening could never happen and the path shoved everything along instead — which is why it overflowed even when the path was narrower than the name column beside it.

Figures no longer wrap into a clipped second line

A long status line squeezed the size beside it until it broke in two — 49.0 GB showing as 49.0 with a sliced GB underneath — and the figures in the bottom bar could do the same.

Both now hold their width and let the sentence beside them shorten instead, which is the right way round: a shortened sentence still reads, and half a number does not.

Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing

Choose where each torrent goes

The add sheet now shows the folder a torrent will be written to and lets you change it, defaulting to wherever your last add went — so a run of torrents bound for the same disk is one choice rather than one per torrent.

Changing the destination re-asks the two questions the sheet exists to answer. Free space belongs to a volume and "you already have this file" belongs to a folder, so both figures it arrived with describe the default destination and neither survives picking another one. Picking a different disk is usually why you are changing it, so carrying the original volume's free space over would be wrong exactly when you are relying on it.

Your file selection is left alone. A file that is absent from the new folder shows unmarked and unselected rather than being quietly ticked back on.

This is set when the torrent is added and not afterwards — moving a torrent's data later is a different operation and is not built yet. If the folder has gone by the time you press Add, the add is refused rather than redirected, and nothing is written to a dead mount point.

Reorder the queue, and see where things stand

Right-click a waiting torrent for Move up in queue and Move down in queue. Before this the queue admitted strictly oldest-first with no way to change it. The expanded row now shows a torrent's place in the line.

There can be more than one line

A place is a claim about the torrents you are competing with, so it depends on which limit is holding you.

Cap only downloads and your seeds are not queued at all — no place and no move action, because there is no line for them to be in. Cap both kinds and you have two lines ranked separately: a download and a seed can both read "1", each being first of what it is actually waiting behind, and a download cannot be moved past a seed because that would change neither one's turn. Only a total limit puts them in one line together, and only when it can actually bite — one download and one seed cannot breach a total of ten.

A torrent you started past the limits now says Queue: Started by you. It runs on top of the limits rather than inside them, and without saying so, a limit being overridden reads as a limit that is broken.

Sort by any column, and have it remembered

Ten keys: name, size, progress, both speeds, ratio, time left, date added, state, and activity — the two rates together, which stays the default. The toolbar's three chips become a picker and a direction toggle.

Rows with no value stay last whichever way the arrow points, because "no estimate" is not "finishes soonest". Choosing a key starts it in the direction it is useful in: largest first for the numbers, A to Z for the name.

See and set the peer limit

Settings → Network now carries "Connect to at most", a per-torrent cap on connected peers, and the detail panel shows the live count against it — 28 / 128 rather than 28.

Worth being plain about: this makes an existing ceiling visible rather than introducing one. Flume passed the engine nothing for this, and nothing did not mean unlimited — it fell back to 128 per torrent. So the default is the number that was already in force, and upgrading changes how no existing install behaves.

It is per torrent, so ten torrents at 128 is a ceiling of 1280 connections, which is the figure a modest router has to hold. Changing it needs a session restart, and the panel reports the limit the engine is actually enforcing rather than the one saved on disk.

Refuse peers by address

Settings → Network takes a blocklist or allowlist URL — http://, https:// or file://. A blocklist refuses peers inside it; an allowlist refuses everything outside it.

The network footer reports how many ranges actually loaded, and that matters more than the setting does. A list that fetches with a clean 200 and parses to nothing reads exactly like one that worked, so an HTML error page, a login redirect or an unrecognised format gives you zero ranges and no complaint. Believing you are filtered when you are not is the failure this has to avoid, so the footer says "Blocklist loaded nothing" rather than staying quiet — and for an allowlist, that no peers can connect at all. Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing

Decide how many torrents run at once

Settings → Queue now caps how much runs at the same time. Three limits rather than one, because downloading and seeding do not cost the same thing: a download uses your connection in both directions and writes to disk, while a finished torrent only uploads. Set a limit on active downloads, on active seeds, or a total as a ceiling over both.

Nothing changes until you set one. Leave them all unset and there is no queue at all, exactly as before.

Queued is not paused

A torrent beyond a limit waits rather than stops. It shows a clock instead of a pause mark and says "queued — starts on its own when a slot frees", and it reads that way to a screen reader too.

That distinction is the whole point. A paused torrent and a queued one look almost identical and behave oppositely: one stays put until you touch it, the other starts itself the moment there is room. Conflating them is the classic way to get this wrong.

Torrents are admitted oldest first. A torrent added before Flume started recording arrival times sorts last rather than first — an unknown arrival time is not evidence of being early.

Your own actions still win

Resuming a queued torrent runs it straight away and takes it out of the queue for good. It keeps running past the limit until you pause it again, which is how you say otherwise — and the choice survives quitting, so the queue does not quietly park it again on the next launch.

It runs on top of your limits rather than displacing anything, so starting one torrent never stops a different one you did not touch.

Resuming a torrent you paused is unchanged and simply un-pauses it: it rejoins the queue and waits its turn.

A torrent already stopped by a seed limit is never started by the queue, and does not hold a slot it is not using.

Full detail in the User Guide and the changelog.

---

Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing

Tell Flume when to stop seeding

Flume can now stop a torrent at a seed ratio, after a length of seeding time, or both. Settings → Seeding sets the defaults for everything; any single torrent can be given its own from its detail panel. Both limits are optional, they work independently, and whichever is reached first wins.

Nothing changes until you set one. An upgrade on its own leaves every torrent seeding exactly as it was.

Seeding time means time spent seeding, not time since the torrent was added. A torrent paused for a week has not been seeding for a week, and the total survives quitting Flume — so a limit set in hours means the same thing across a restart.

A stopped torrent says why

A torrent Flume stopped reads as "stopped at your seed ratio limit" rather than a bare "paused", in the list and in its detail panel. That distinction is the point: a paused torrent and a failed one look identical otherwise, and one of them is fine.

Keep seeding lifts the limit for that torrent and starts it again. It replaces Resume rather than sitting beside it — resuming alone would leave the limit in force and stop the torrent a second later.

A per-torrent limit replaces the global one rather than blending with it, which is what makes "seed this one forever" something you can actually say. Per-torrent limits are removed along with their torrent.

Also in this release

• A collapsible sidebar. It folds to a 56px icon rail and back, from the toggle beside the wordmark or from Settings → Appearance, and the choice survives a relaunch.
• "Recently added" now sorts by when a torrent actually arrived. It used to sort by an internal id that gets reused when you remove a torrent. Torrents added before this release have no recorded arrival time and sort last, rather than being given an invented one.
• A missing .torrent file can no longer hang startup, and when a start does fail, Flume names the torrent responsible and says so in the window instead of only in the log. Nothing is deleted or repaired on your behalf — a file can go missing because a drive is not mounted yet.

Full detail in the User Guide and the changelog.

---

Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing

Only transfer through a tunnel

Flume can now work out which network interface your traffic would actually leave by, and hold everything while that is not a tunnel. Settings → Network. Off unless you turn it on.

It reads your own routing table and sends nothing to do it. There is no "what is my IP" request to a web service, which would mean handing your address to a stranger in order to be told it is protected.

Holding does not pause your torrents. Flume runs no torrent session at all — no transfers, no peer connections, no DHT, no listening port — and nothing is written to your torrents, so whatever you paused stays paused and whatever was running comes back running. The check runs before the engine starts, so nothing announces to a tracker from an address you did not intend.

A drop takes effect immediately. Recovery waits about ten seconds of a steady tunnel, so a reconnecting VPN does not re-announce your whole library to every tracker.

What it cannot tell you

It sees which interface traffic leaves by and whether that looks like a tunnel. It cannot see where the tunnel goes or who runs it:

• A PPPoE line or USB cellular modem is the same kind of point-to-point link with no hardware address, so it may be reported as a tunnel.
• On Windows with OpenVPN, the adapter is indistinguishable from an Ethernet card. Transfer will be held even though you are protected — pin that interface in settings to get through.

Full detail in the User Guide and Privacy.

---

Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing

Download the file for your platform below.

macOS builds are signed and notarized by Apple, so they open normally.

Windows builds are not signed. SmartScreen will show "Windows protected your PC". The Run anyway button is behind More info, which is easy to miss. Linux packages have no such gate.

SHA256SUMS.txt below covers every file here, if you would rather verify the download than trust the dialog:

sha256sum -c SHA256SUMS.txt --ignore-missing