Skip to content

TOML to JSON converter

Read any TOML file as JSON — parsed on your device.

Runs in your browser — files never leave your device
TOML
JSON

Convert TOML to JSON in your browser

TOML is pleasant to edit and awkward to process: most scripts, APIs and tools like jq want JSON. Converting a Cargo.toml, pyproject.toml or app config to JSON makes it easy to inspect, diff or feed into something else. The parser follows TOML 1.0 strictly, so duplicate keys and redefined tables are reported as errors with the line they occur on.

Types that don't exist in JSON

TOML has a richer set of types than JSON, so a few values change form on the way across:

  • Dates and times become ISO 8601 strings. An offset date-time such as 2026-10-30T08:00:00Z is written in UTC; a local date such as 1979-05-27 stays as written.
  • Very large integers — TOML allows full 64-bit integers, while JSON numbers in JavaScript are exact only up to 253.
  • Comments are dropped.

Tables and arrays of tables become nested objects and arrays, exactly as you would expect.

Other conversions with this tool

How to convert TOML to JSON

  1. 1

    Paste your TOML into the left pane.

  2. 2

    The equivalent JSON appears live on the right.

  3. 3

    Copy it for scripts, APIs or jq.

TOML to JSON — frequently asked questions

Is my TOML uploaded anywhere?

No. The conversion runs in your browser, and this site has no server that could receive your TOML. A Content-Security-Policy blocks requests to other domains; you can confirm in DevTools → Network or by going offline.

How are TOML dates converted?

JSON has no date type, so TOML dates and times become ISO 8601 strings, such as "2026-10-30T08:00:00.000Z".

Is the TOML parser strict?

Yes. It follows TOML 1.0, so duplicate keys, redefined tables and mixed-up types are reported as errors instead of being guessed at.