How to use it
- 1
Choose TOML → JSON or JSON → TOML.
- 2
Paste the configuration document.
- 3
Run conversion and review warnings and output.
What the tool can do
- Basic and literal strings, booleans, safe integers, finite floats, and arrays.
- Tables, dotted keys, array tables, and inline tables.
- Hexadecimal, octal, and binary integers checked against the JSON safe-integer range.
- TOML date/time values are preserved as strings with an explicit warning.
Common use cases
- Converting application configuration for an API or tests.
- Finding duplicate keys and type conflicts.
- Preparing readable TOML from a JSON-compatible object.
How it works inside
Input is limited to 500,000 characters, 5,000 nodes, and depth 32.
JSON → TOML accepts a root object; arrays of objects are emitted as array tables.
Questions and answers
Why do dates become strings?
JSON has no dedicated date/time type. The tool preserves the lexical TOML value as a string and reports a warning.
Is null supported?
Not for JSON → TOML: TOML 1.0 does not define a null literal.