A magnet link is not an ordinary HTTP address to one complete file. It identifies torrent content that an engine can discover and obtain from peers. Flux includes a native BitTorrent engine, so torrent tasks can live beside your file and media downloads without requiring a separate heavy daemon.
Two ways to add torrent content
You can provide a magnet URI or import a local or HTTP .torrent file. A magnet may first need metadata discovery before showing the complete file list. The time this takes depends on accessible peers and network conditions. A valid link does not guarantee that an active peer currently has the content you want.
Review files and sharing before starting
- Use a torrent for content you are authorized to obtain and share.
- Wait for metadata so you can review the file list.
- Choose the files and destination you need.
- Check download and upload limits.
- Review the global or per-task seeding rule before leaving the task running.
How verification differs from HTTP
Torrent pieces are checked against the torrent’s integrity information. Flux supports v1 and BEP 52 v2/hybrid workflows and can also produce selected-file SHA-256 values. Piece verification protects consistency with the torrent metadata; it does not by itself prove that the content is trustworthy or that a publisher created it.
Network participation is part of the workflow
BitTorrent communicates with peers and may use trackers, DHT and other discovery mechanisms. Your network address can be visible to participants. Seeding sends data after or during the relevant torrent workflow according to your preferences. If you only intended a direct server download, check that you have not selected a magnet by mistake and read the project’s privacy disclosure.
A folder that feeds your queue.
Watch up to 16 folders for .torrent files. Choose confirmation or automatic queueing, set an optional destination, and avoid duplicates across restarts. Source files stay untouched; Flux must be running.
Open Settings → Torrent watch folders, enable monitoring and save. Stable files are checked every three seconds, including while Flux is in the tray. Subfolders are excluded. Select confirmation or automatic import; identical content is not imported again, even after a rename or restart.
Sources and release context
This guide describes the Flux 2.6.6 documentation. Check the current release record for package conditions.
