JSON to TOML

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from JSON to TOML

JSON to TOML converts JSON to TOML. TOML uses key-value assignments and tables to make configuration data readable, while JSON uses objects and arrays. JSON null has no direct TOML value equivalent. Object nesting and arrays should be reviewed as TOML tables or arrays of tables. Inspect strings containing backslashes and multiline text; quotation rules differ across the two formats. Use the worked example to understand what a successful result looks like, then compare it with a small sample of your own input. Keep the original available until you have checked the output in its destination. Conversion establishes a representation; it does not establish that the underlying information is correct or that the receiving application accepts every supported feature.

Guide updated October 13, 2026

How to use this tool

1. Enter or load JSON using the input controls. Begin with the worked example or a small sample for which you know the expected result.
2. Review any available conversion options, then inspect the TOML result. Resolve a reported parse error at its source before attempting to reuse the output.
3. Check the example below against your own data. Inspect strings containing backslashes and multiline text; quotation rules differ across the two formats.
4. Copy or save the resulting TOML content using the controls provided, then validate it in the application or parser that will actually consume it.

SEE IT IN PRACTICE

A worked example

{"port":3000,"name":"demo"}

port = 3000
name = "demo"

A JSON number remains numeric and a string remains quoted in TOML assignment syntax.

Quoted names and literal dots

TOML uses dots to express dotted key paths, but a quoted key can contain a literal dot. A JSON property named app.name is not automatically the same as a JSON object app containing name. Inspect the converted path when punctuation occurs in keys. Strings containing backslashes and newlines also need TOML-appropriate quoting; visual similarity alone does not prove that the parsed value is unchanged.

Objects become tables

A nested JSON object can map to a TOML table, while a list of similarly shaped objects can map to an array of tables. Inspect the table boundaries rather than judging only the values on individual assignment lines. TOML does not have a null scalar, so null-bearing JSON needs a deliberate mapping or cleanup. Do not silently replace null with an empty string unless that matches the application’s meaning.

When this tool is useful

• Prepare configuration migrations while retaining a separate copy of the source.
• Use a small example to troubleshoot table nesting and value typing and identify a representation mismatch.
• Create readable application settings without manually rewriting every field or symbol.

Tips for a better result

• JSON null has no direct TOML value equivalent. Object nesting and arrays should be reviewed as TOML tables or arrays of tables.
• Inspect strings containing backslashes and multiline text; quotation rules differ across the two formats.
• After changing formats, compare meaningful values rather than whitespace alone. Read the TOML output with its intended parser when exact types or escaping matter.

Frequently asked questions