IEEE 754 Converter
See a float’s sign, exponent, mantissa and its exact decimal value.
Convert a TOML config to JSON, with tables and arrays of tables resolved.
The TOML to JSON converter resolves dotted table headers into real nesting and arrays of tables into arrays of objects, which makes TOML's scoping — the thing people get wrong — immediately visible.
Converting a TOML file to JSON shows you the structure it actually describes rather than the one the headers suggest. Dotted table headers become real nesting, arrays of tables become arrays of objects, and every key ends up where TOML says it belongs.
That is more useful than it sounds, because TOML's scoping is the thing people get wrong. A key written below a [table] header belongs to that table even if the author meant it as a top-level setting, and the JSON makes that immediately visible. The parser handles basic and literal strings, multi-line strings, integers in decimal, hex, octal and binary, floats, booleans, dates, arrays and inline tables.
A setting that ended up inside a table rather than at the root is plain to see once the headers become nesting.
Decimal, hex, octal and binary literals all convert, and underscore separators such as 1_000_000 are handled.
The { x = 1 } and [1, 2] forms are read, including across the line breaks a long array is wrapped over.
JSON has no date type, so a TOML date is kept as its original string rather than being reinterpreted into a timestamp.
A file that will not parse names the line, which for a Cargo.toml is usually a missing quote.
Cargo.toml, pyproject.toml, a Netlify or Hugo config, or your own.
Table headers become nesting, so you can see what belongs to what.
A setting that ended up inside a table rather than at the root is obvious here.
Take the JSON to your clipboard or save it as a .json file.
TOML has real date, time and datetime types and JSON has none, so they are kept as strings in their original form rather than being reinterpreted into a timestamp.
A JSON array of objects. Each [[header]] block adds one element, which is exactly the mapping you would expect.
Yes. TOML allows 1_000_000 as a readability aid; the separators are removed and the value becomes the number 1000000.
TOML supports 0x, 0o and 0b prefixes and they are converted to their decimal value, since JSON only has decimal numbers.
What people who use the TOML to JSON think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the TOML to JSON. It takes half a minute and no account.
Write the first reviewSee a float’s sign, exponent, mantissa and its exact decimal value.
Build media queries with framework breakpoints and modern features.
Build text shadows, outlines and glows with a live preview.
Generate and decode MongoDB ObjectIds, including their embedded timestamp.
Your browser, engine, platform, languages and what it supports.
Decode a JWT and read its header, claims and expiry in plain English.
Press any key and see event.key, event.code and the modifier state.
Every HTTP status code, searchable, with what it actually means.