TOML to JSON Converter
Paste TOML to get JSON, covering the TOML 1.0 core. Nothing is uploaded — the parser runs on your device.
Why convert TOML to JSON?
TOML is a common configuration format — Cargo, pyproject and many other tools use it — while JSON is the interchange format most programs read. Converting lets you inspect a config file as plain data, feed it to a JSON tool, or check a structure by hand. The grammar is small and closed, so the parser on this page covers the TOML 1.0 core: key/value pairs, tables, arrays of tables, inline tables, arrays and the native scalar types. Dates and times are kept as strings because JSON has no date type. For JSON itself use the JSON formatter, and for a different conversion see the XML to JSON converter (on the tools hub).
Frequently asked questions
Which TOML features are supported?
The core of TOML 1.0: key/value pairs, tables [a], arrays of tables [[a]], inline tables, arrays, integers, floats, booleans, basic and literal strings (including multiline), and dates/times kept as strings.
What is not supported?
Non-standard extensions and exotic dotted-key edge cases are out of scope. The parser targets the TOML 1.0 core so its behaviour stays predictable.
How are dates and times handled?
TOML dates and times are returned as their original strings, because JSON has no native date type. Convert them downstream if you need a different representation.
Is my TOML uploaded anywhere?
No. Parsing happens in your browser with a self-written parser. Your data never leaves your device and nothing is stored.
What happens if my TOML is invalid?
The output box shows a line-level error so you can locate the problem in the source.
How is this different from a YAML converter?
Both turn a configuration format into JSON, but TOML has a much smaller grammar than YAML: no anchors, aliases or tag system, so the parser covers the specification more completely.