How to convert a torrent file to a magnet link
Keep the torrent’s identity. Choose which optional details travel with the link.
Free toolTorrent to Magnet ConverterTurn .torrent files into magnet links on your device. Inspect files, preserve info hashes and convert a whole batch without contacting trackers.Convert a torrentConvert the metadata, without downloading the content
Open a local .torrent file in a converter, then copy the generated magnet. You do not need seeds for this calculation.
- Find the actual
.torrentfile. A webpage URL or downloaded video is a different input. - Open it in the Torrent to Magnet Converter. Review its version, info hashes and file list.
- Choose whether to include its name and original tracker addresses.
- Copy or save the magnet. Use a torrent client that supports its version when you want the content.
Private torrents need extra care. Keep their original .torrent and use the private tracker’s approved client.
What changes between a torrent file and a magnet?
The torrent file carries metadata. The magnet carries an identifier and optional hints.
| Part | .torrent file | Magnet link |
|---|---|---|
| Info dictionary | Contains names, sizes and piece information. | Identifies it through one or more hashes. |
| File list | Available for local inspection. | Usually obtained later from peers. |
| Trackers | Can include ordered tiers. | Optional repeated tr parameters. Tiers are not preserved. |
| Content bytes | Not included. | Not included. |
A successful conversion does not fetch the files. Opening a magnet in a client is a separate network operation.
Understand v1, v2 and hybrid magnets
Use a client that recognises the torrent’s hash format.
- V1: a 40-character hexadecimal SHA-1 identity, usually written as
xt=urn:btih:…. Base32 BTIH is another valid representation. - V2: a SHA-256 identity written as
xt=urn:btmh:1220…. The prefix tags its hash algorithm and length. - Hybrid: one magnet can include both topics for the same hybrid metadata.
These formats are defined by BEP 9 and the v2 specification. A v1-only client cannot use a v2-only torrent just because you changed the link’s prefix.
A reproducible conversion example
Our synthetic example describes a 12-byte hello.txt. Its two example.org tracker addresses are illustrative and are never contacted.
The converter’s Try an example uses these same 303 metadata bytes. You can save the example torrent to inspect it elsewhere.
| Setting | Result for this example |
|---|---|
| Original identity | d944b0d293d2edd03ff130c2d26607844ba35bd7 |
| Name and trackers off | magnet:?xt=urn:btih:d944b0d293d2edd03ff130c2d26607844ba35bd7 |
| Display name on | Adds &dn=hello.txt. The identity stays the same. |
| Original trackers on | Adds two URI-encoded tr parameters. The repeated announce address is included once. |
Checked on 24 October 2026. The expected identity was calculated independently with Node’s SHA-1 over the original encoded info bytes, then compared with the converter. This tests identity, not content availability or transfer speed.
Why the exact info bytes matter
Hash the encoded info dictionary from the original file. Hashing the whole .torrent produces a different value.
Changing the encoded info changes its identity. Changing an outer tracker list does not. Our converter validates bencoding and hashes the original byte range, following BEP 3.
The display name is a hint
A magnet’s optional name can differ without changing its identity. Compare full hashes when comparing links.
A hash is not a safety certificate
It identifies metadata. It does not authenticate a publisher or prove that the content is harmless.
Choose a conversion method
A local converter is useful when you have the metadata file and only need its link.
| Method | Useful when | What to check |
|---|---|---|
| Local browser converter | You need a link, a batch export or metadata inspection without joining peers. | Supported versions, original-byte hashing and whether files leave the device. |
| An existing torrent client | You already have the torrent loaded. Check its Copy or Share menu for a magnet option. | The client may already be announcing or sharing. Client labels and version support vary. |
| A hosted converter | You deliberately choose a service that processes uploaded metadata. | Its upload, retention and account requirements. A browser interface does not imply local processing. |
Nutbread’s Torrent to Magnet is another local browser option. It produced the expected v1 identity in our synthetic test. Check version handling separately before using a v2 torrent.
Keep private torrents in their original form
A private torrent’s discovery is restricted to its approved tracker. Its file can also contain a personal tracker passkey.
The private flag lives inside the metadata. A magnet hash by itself does not carry all that context before metadata retrieval. The private-torrent specification restricts peer discovery.
floi therefore offers inspection, JSON and file-list exports for private torrents, while disabling magnet and QR output. Do not publish a tracker address containing your passkey.
Why magnet to torrent needs another source
An info hash cannot be reversed into filenames, piece hashes or the original info dictionary.
- If your client already has the metadata, use its torrent export feature where available.
- If you still have the original .torrent file, keep or share that copy directly.
- Otherwise, a client or service must retrieve metadata from a source such as compatible peers.
This converter does not perform that retrieval. It also cannot turn torrent metadata into MP4, ZIP or the content itself.