Data & Formats

JSON ⇄ TOON Converter

Turn JSON into TOON, a compact, readable format for structured data in LLM prompts, or turn TOON back into JSON. It follows the current TOON specification exactly, keeps every number exact and tells you precisely where invalid input goes wrong. Nothing leaves your browser.

Your data never leaves this page. Everything is converted in your browser, large inputs in a background worker. Nothing is uploaded, sent to a server, put in the URL or stored.
JSON to TOON options

Drag and drop a .json or .toon file here, or choose one. Files up to 200 MB are converted in the background.

Ready. Paste JSON to convert it to TOON. Nothing is uploaded.

What TOON is

TOON (Token-Oriented Object Notation) writes the same data as JSON in fewer lines of syntax: indentation instead of braces, array lengths and column names declared once, and quotes only where they are needed. It is meant for sending structured data to language models. This converter follows version 4.4 (8 October 2026) of the specification at github.com/toon-format/spec and passes the specification's own test fixtures.

users[2]{id,name,role}:
  1,Ada,admin
  2,Bob,user

What it does

  • JSON to TOON and back. Uniform arrays of objects become tables, including tables with nested columns and objects of uniform objects. Other data uses list form.
  • Exact numbers. Numbers are written in the canonical form the specification requires (no exponent in the normal range, no trailing zeros, -0 becomes 0). A number a standard double cannot hold exactly, such as 12345678901234567890, is never silently rounded: by default it is written as a quoted string so every digit survives, and you are told. You can choose the nearest number instead; then you are told digits were lost.
  • Nothing is guessed. Duplicate keys in JSON, numbers beyond the double range, and lenient-mode recoveries are listed as notes. An unpaired surrogate in a string is refused, because TOON cannot represent it.
  • Precise errors. Invalid JSON is reported with line and column, using the same diagnostics as the other JSON tools. Invalid TOON is reported with the line and the rule that was broken, and strict mode (the default) checks array counts, row widths, indentation, blank lines and duplicate keys.
  • Round-trip check. After converting JSON to TOON the tool reads the TOON back and compares it with your JSON. Inside tables the specification lets keys follow the table header order, so that is the one reordering you may see.
  • Large files. Big inputs and files are converted in a background worker, with a Cancel button. The page does not freeze.
  • Delimiters. Comma, tab or pipe, and 2 or 4 spaces of indentation. The choice is declared in every header, as the specification requires.

Moving data between tools

Use the “Send to” menu of the JSON Formatter, JSON Repair, NDJSON, JSON Validator and JSON Tree Viewer to open their JSON here. After converting TOON to JSON, “Send JSON to” opens the result in the other JSON tools. Data is held in your browser for under a minute for the next tool, then deleted.

Limits and honest notes

  • TOON is a Working Draft. If the specification changes, this tool should be updated; the version it implements is shown in the summary.
  • Fewer characters is not the same as fewer tokens. Token counts depend on the model's tokenizer, and TOON can be larger than JSON for deeply nested or irregular data. This tool shows characters, not tokens.
  • Nesting deeper than 2,000 levels is refused with a clear message.
  • Files up to 200 MB are read whole into memory. Very large results are shown in part (the first 500,000 characters); Copy and Download always use everything, and Copy stops at 25 million characters.
  • In TOON to JSON, a number the decoder cannot hold as a double keeps its exact digits in the JSON text. A string such as "123" stays a string.
  • The decoder ignores full-line comments (#), as the specification says; they are not kept when converting to JSON.

Share this tool

Your data is not included in this link.