Finishing a torrent download is not always the end of its network activity. A task can continue seeding according to its sharing rule. Flux exposes global and per-task sharing preferences so that the intended upload behavior is part of your decision rather than a surprise after completion.
Select only the files you need
Review the metadata file list and choose the intended output. Piece boundaries can span files, so internal storage and verification may involve more than the visible selected-file total. Choose a destination with suitable free space and avoid editing partially downloaded files while the engine verifies them.
Understand the sharing target
The project’s privacy disclosure describes a default sharing ratio of 1.0. That is a target based on uploaded and downloaded data, not a guaranteed amount of time. Global or per-task settings can change the behavior. You can disable or pause sharing explicitly; check the task’s actual state instead of assuming that a completed download has disconnected.
Control bandwidth and peers
- Set a suitable upload budget as well as the download budget.
- Review peer limits if your network is sensitive to many connections.
- Choose the seeding rule that fits your use.
- Pause sharing when you need the connection for another task.
- After reopening the app, check the persisted task state before resuming.
Verification and privacy
A damaged local piece may need rechecking and repair before the output is accepted. A high speed display is not a substitute for verified completion. Torrent transfers also contact a swarm rather than only one publisher’s server, so consult the privacy disclosure and obtain only content you have permission to share. The queue unifies the controls, but HTTP and torrent network behavior remain different.
Sources and release context
This guide describes the Flux 2.6.6 documentation. Check the current release record for package conditions.
