⌘ K
magnet · bittorrent · uri · live

Parse any magnet: link

Break a magnet: URI into BitTorrent info hash, display name, trackers, web seeds, and extras. Useful for archival, security review, and link debugging. Runs entirely in your browser.

Magnet URI Parser
Input
145 B
uri
Trackers
1
tr=
Web seeds
0
ws=
Status
parsed
live
Format: magnet:?xt=urn:btih:HASH&dn=…&tr=…
input · magnet uri
output · parsed
fields
info hashc12fe1c06bba254a9dc9f519b335aa7c1367a88a
display nameubuntu-22.04-live-server-amd64.iso
size(none)
trackers1
web seeds0
raw json
{
  "infoHash": "c12fe1c06bba254a9dc9f519b335aa7c1367a88a",
  "name": "ubuntu-22.04-live-server-amd64.iso",
  "trackers": [
    "udp://tracker.openbittorrent.com:80"
  ],
  "webSeeds": [],
  "sizeBytes": null,
  "acceptable": [],
  "raw": {
    "xt": "urn:btih:c12fe1c06bba254a9dc9f519b335aa7c1367a88a",
    "dn": "ubuntu-22.04-live-server-amd64.iso",
    "tr": "udp://tracker.openbittorrent.com:80"
  }
}
Quick Start

How to parse a magnet URI

Magnet URIs encode a BitTorrent info hash plus optional metadata as query parameters. No file or HTTP fetch needed — everything lives in the URI.

  1. 01

    Paste the magnet URI

    Must start with magnet:?. The rest is URL-encoded params.

    Bytes flow through TextEncoder/TextDecoder for predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.

    inputUTF-8TextEncoderlosslesslive
    input · raw bytesmagnet · UTF-8
    magnet:?xt=urn:btih:…
    loaded · UTF-8MIME · ready
  2. 02

    Pull the info hash

    The xt=urn:btih: portion is the BitTorrent identifier.

    Hash and signature operations call crypto.subtle from the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.

    xtWeb Cryptosubtledeterministiclive
    xt · optionsbtih · live
    c12fe1c06bba254a9dc9f5…
    options applied · livelive
  3. 03

    List trackers and seeds

    Multiple tr= and ws= params can repeat.

    Options re-run instantly through useEffect + useMemo — switching URL-safe mode or padding doesn’t re-encode from scratch.

    listsmemoisedoptionsinstantreactive
    tr / ws · encodedlist · ready
    udp://tracker.openbittorrent.com:80
    encoded · livelossless
  4. 04

    Copy as JSON

    One click to grab the parse as a JSON object.

    Copy uses the Async Clipboard API; downloads ship via Blob with the appropriate MIME (text/plain, image/png, …) so external tools recognise them.

    exportclipboardblobMIME-correctclient-side
    ok · copiedready · done
    Copied
    shipped · ready to shipsuccess
Pro tips

Encoding without surprises

Always UTF-8 first

Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.

URL-safe vs standard Base64

Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.

Hashes aren’t passwords

SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.

Watch padding rules

Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.

Use Web Crypto for keys

Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.

JWT decode ≠ verify

Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.

Related toolsURL DecoderURL EncoderData URI ParserBase32SHA-1Hex to Decimal
Use Cases

When to inspect magnet links

Security review, archival, link debugging, audit.

Security review

See exactly which trackers a link contacts. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.

RFC-compliant

Archival

Record the info hash and display name for catalogues. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.

OpenSSL-matched

Debugging

Spot malformed or duplicated tracker entries. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.

lossless

Migration

Move metadata between BitTorrent clients programmatically. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.

byte-identical

Audit

Inventory all magnet links in a document or wiki. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.

spec-grade

Education

Show the structure of a magnet URI to a teammate. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.

production-ready
FAQ

Frequently asked questions

The BitTorrent info hash (SHA-1 of the torrent's info dictionary). It uniquely identifies the content without needing the .torrent file.
Because they live inside a URL query string, the URI scheme requires encoding of reserved characters. The parser decodes them for display.
v2 uses urn:btmh: with multihash. This parser displays whatever xt value is present, even for v2 magnet links.
No — it only parses the URI. No network traffic is generated.
No. Parsing runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!