Flux include a native asynchronous BitTorrent engine, so magnet tasks no need an external heavy daemon. A magnet identify content, but peers must provide metadata and pieces before transfer fit progress. A valid link alone no guarantee seeders dey available.
Add the task
Paste the magnet URI or import a .torrent file. Review destination before starting. A magnet fit first wait for metadata discovery. A .torrent already contain metadata, but both still need working peers to supply content.
Discovery and verification
DHT and trackers help find peers. Downloaded pieces get verified against torrent hashes. Slow discovery fit mean no reachable peers, tracker problems or network restrictions. Increasing HTTP connection count no fix a swarm wey no get data.
Control traffic and sharing
Use task limits and queue controls. Upload fit continue after completion while the torrent dey seed. Check sharing limits and actual task state instead of assuming that download completion automatically stop every network connection.
Protect your private information
Peers fit see your public IP address during transfer. Local history no make BitTorrent anonymous. Use content wey you get permission to share. Remove private tracker passkeys and private magnet links before reporting problems.
Drop am for folder. E go enter queue.
Watch up to 16 folders for .torrent files. Choose make Flux ask first or add am automatically, plus optional destination. Restart no go add the same content twice. Original files remain; Flux must dey run.
Open Settings → Torrent watch folders, turn monitoring on and save. Files wey don finish changing get checked every three seconds, even when Flux dey tray. Subfolders no join. Choose confirmation or automatic import; same content no go enter again after rename or restart.
Sources and release details
This guide follow Flux 2.6.6 documents. Check the current release record for the conditions wey follow each package.
