Torrent to Magnet Link

Everything runs locally in your browser — nothing is uploaded

Drop a file here, or click to choose

One file · processed entirely on your device

The file is read inside your browser only — nothing is uploaded. It keeps working offline.

Turn a `.torrent` file into a magnet link — just drop it in, nothing is uploaded. The point of a magnet is not depending on the torrent file itself: it carries the resource identity (the infohash) in the link, and anyone holding it can find the peers over the DHT. Delete the original file, lose it, watch a forum purge it — the link still works. What happens here is more delicate than it looks. The infohash is not the hash of the whole file — it is the SHA-1 of the `info` dictionary as it appears in the torrent, and it must be the raw bytes themselves. Parsing the file into a structure and re-encoding it before hashing yields a value of the right length and entirely valid shape that simply does not exist on the network, with nothing to indicate it is wrong. ⚠️ That is very likely why some online converters produce infohashes that clients can never connect with. Beyond the link, the page lays out what the torrent actually contains: name, total size, piece length, tracker list, creation tool and date, and whether it is private. That is usually exactly what you want to know before pasting anything into a client. Both generations are supported: the v1 infohash is SHA-1 (`btih` in the link) and v2 switched to SHA-256 (`btmh`). Hybrid torrents carry both, so both are emitted — older clients honour v1, newer ones v2.

Features

A paste-ready magnet link with dn, xl and every tracker
The infohash is taken from the raw info bytes, matching what clients expect
Supports v1 (SHA-1 / btih) and v2 (SHA-256 / btmh)
Name, total size, file count, piece length and piece count
Expands every backup tracker in announce-list
Flags private torrents — those that stay out of DHT and PEX
Nothing is uploaded; it keeps working offline

How to use

Drop the .torrent onto the dashed box
The link appears at the top — copy it with the button beside it
The table below shows every detail the torrent carries
Paste it into any BitTorrent client to start

FAQ

Why is this infohash different from one I got elsewhere?: Suspect the other source first. The infohash has a rigid definition: the SHA-1 of the `info` dictionary’s raw bytes. The trouble is that bencode permits equivalent spellings — key order, integer representation — so any tool that parses the torrent into objects and re-encodes it before hashing computes a different byte sequence. The result looks entirely normal (40 hex characters) but does not exist on the DHT, and the client will sit forever at "fetching metadata". This tool always uses the original bytes and never re-encodes. There is another possibility, of course: the `.torrent` you have and that infohash simply come from two different torrents.
What are all those parameters in the magnet link?: `xt` is the identity — the 40 hex characters after `urn:btih:` are the pre-v2 infohash. `dn` is the display name: a label for the client and the user, not part of the identity, so changing it cannot break connectivity. `xl` is the exact byte length, letting a client reserve space up front. `tr` is a tracker address; one link can carry many, each as another `tr` parameter. Drop the `tr` entries entirely and the link still works, because a client can find peers through the DHT instead.
What does a "private torrent" mean here?: A private torrent (`private: 1`) asks peers to exchange only through the trackers listed inside it, staying out of the DHT and PEX (peer exchange). Publishers do this to count seeding ratios and allocate access by traffic — that is how most private trackers operate. For this tool it means one extra line of output, but if you strip the `tr` parameters from a private torrent by hand, it will in all likelihood reach nobody at all.

Related tools

Magic Bytes

Web

Identify a file from its first bytes. Covers 59 common formats, handles signatures at an offset, and looks up the magic bytes for a given format.

Hash

Encoding

Compute MD5, SHA-1, SHA-256, SHA-512 or MD4 digests of any text, hashed as UTF-8 bytes so they match openssl exactly. Runs in your browser.

URL Parser

Web

Parse a URL into scheme, host, port, path, query parameters and fragment, with each parameter shown raw and decoded. Runs entirely in your browser.

User-Agent Parser

Web

Parse a user agent into browser, version, OS, device type and engine, and see which rules matched. Pattern matching only. Runs entirely in your browser.

HTTP Status Codes

Web

Look up an HTTP status code for its meaning, 1xx–5xx class, typical uses and common traps. Runs entirely in your browser.

MIME Types

Web

Look up a MIME type from an extension, or the default extension for a media type. Common types only. Runs entirely in your browser.

← Back to all tools