TOML tables and dotted keys
A table such as [server] becomes a nested server object. Repeated [[users]] declarations become an array of objects. Dotted keys expand into nested properties, while quoted keys can contain literal punctuation. TOML comments describe the source document and are not included as JSON fields.
Dates, integer precision and JSON values
TOML date-time values become strings because JSON has no date-time scalar. Integers within the JavaScript safe range stay numbers; larger TOML integers are emitted as decimal strings to keep their digits. Infinity and NaN are rejected rather than changed to null. Review the target schema if it expects a numeric value instead of a large-integer string.
TOML syntax errors
Duplicate keys, invalid table declarations and malformed strings produce parse errors. A JSON object permits null, but TOML has no null literal; a plain null in TOML is not a shortcut for an empty value. The result editor lets you adjust the JSON after a successful parse without changing the original TOML file.
Format references
File content is read and converted in the browser. Conversion does not upload the source to a server.