TOML to JSON Converter – Free, Online, Private

Coverage

The reader accepts assignments, dotted keys, [tables], [[arrays of tables]], basic and literal strings, multiline basic strings, booleans, integers, floats, arrays and inline tables. Comments start at # outside a string. Integers may contain underscores. A datetime is returned as a string rather than a Date, so the JSON stays portable and you do not lose the original spelling to a timezone conversion. The root of TOML is always a table, so the JSON root is always an object.

What will fail

This is a practical subset, not a certification of the whole 1.0 spec. Quoted keys work. Exotic escapes and dotted keys inside arrays of tables can still trip the scanner; the error text names the value it could not read. Duplicate keys in one table overwrite. A file that uses the older implicit table style is accepted when each [header] appears before its keys. If you need a fully conforming parser for a Cargo.toml with every extension, use a language library in CI. This page is for the config you want to see as JSON right now.

Worked example

The sample sets title, port and enabled at the root, then an [owner] table with a name. The JSON is { title, port: 8080, enabled: true, owner: { name } }. port is a number because the scalar was an integer. enabled is a boolean. Add [[tags]] sections and the JSON gains a tags array of objects. The reverse page, JSON to TOML, prints tables in an order a TOML reader accepts: scalars first, then child tables.

Local configs

TOML files often hold registry tokens and database URLs. Parsing them in the browser means the token is not posted to a formatter. Clear the box when you are done on a shared machine. The page does not write back to disk.

Frequently asked questions