Bencode to JSON

A .torrent file, a tracker announce, a DHT message — on the wire they are all bencode: compact strings with length prefixes, integers wrapped in i...e, and deeply nested lists and dictionaries. Reading that by eye is painful, and debugging a peer against a malformed metainfo file is worse.

Convert Bencode to JSON parses bencode into a clean, pretty-printed JSON document. Dictionaries become objects, lists become arrays, integers and strings map onto their JSON counterparts, and UTF-8 strings are decoded for you.

• Full grammar: Integers, strings, lists, dictionaries and arbitrary nesting.
• UTF-8 strings: Byte strings are decoded to readable text when valid UTF-8.
• Torrent files: Upload a .torrent or .bencode file, or paste text.
• Null support: The common n marker becomes JSON null.
• Strict validation: Truncated and malformed bencode is reported with a position.
• Duplicate detection: Dictionary keys that would overwrite are flagged.
• Pretty output: The result is indented, readable JSON.
• Private: All parsing happens in your browser.

1. Paste bencode or upload a .torrent file.
2. Read the JSON — dictionaries, lists and values are decoded instantly.
3. Check the info section of a metainfo file for files and piece lengths.
4. Copy or download the JSON document.

Example 1 — Torrent inspection. A user uploads a .torrent to see the announce URL, file list and piece length in readable JSON instead of decoding hex by hand.

Example 2 — Tracker debugging. A tracker operator pastes a failed announce request and reads the error key that the protocol hides in bencode.

Example 3 — Data migration. A team imports legacy torrent metadata into a JSON database, converting each metainfo file and reviewing the output before ingest.

Example 4 — Testing. A developer generates bencode fixtures for a peer implementation, converts them here, and uses the JSON as expected-output test data.

• Instant readability: Compact bencode becomes indented JSON.
• Standards-safe: Strict parsing catches truncation and duplicates.
• No install: Runs in the browser, nothing to download.
• Round-trip friendly: Pairs with our JSON to Bencode tool.
• Zero upload: Files are parsed locally, never sent anywhere.