TOML to JSON

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from TOML to JSON

TOML to JSON converts TOML to JSON. TOML tables and assignments can be represented as nested JSON objects for software expecting JSON configuration or data. TOML comments and date/time types do not have exact ordinary JSON equivalents. Review date representations in the converted output. Check arrays of tables separately from ordinary arrays and verify dotted keys produce the intended nesting. 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 TOML 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 JSON result. Resolve a reported parse error at its source before attempting to reuse the output.
3. Check the example below against your own data. Check arrays of tables separately from ordinary arrays and verify dotted keys produce the intended nesting.
4. Copy or save the resulting JSON 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"}

Assignment names become JSON property names, and the integer and string preserve their distinct types.

Follow the table context

Assignments after a TOML table heading belong inside that table. For example, a name assignment under [app] becomes a name property inside an app object. Arrays of tables become a collection of records rather than a single mapping. Check a nested table and a repeated table entry before converting a larger configuration, and verify that the resulting hierarchy matches the receiving JSON schema.

Date and time values need review

TOML has date and time types that ordinary JSON does not. Their converted representation must fit the consuming application’s expectations, often as text. Check whether an offset is retained and whether a date-only value remains date-only. Comments and table formatting are not JSON data. Preserve them separately if they document operational intent, rather than expecting a data conversion to retain the original TOML source layout.

When this tool is useful

• Prepare JSON configuration from TOML while retaining a separate copy of the source.
• Use a small example to troubleshoot table paths and quotation issues and identify a representation mismatch.
• Create API-friendly configuration snapshots without manually rewriting every field or symbol.

Tips for a better result

• TOML comments and date/time types do not have exact ordinary JSON equivalents. Review date representations in the converted output.
• Check arrays of tables separately from ordinary arrays and verify dotted keys produce the intended nesting.
• After changing formats, compare meaningful values rather than whitespace alone. Read the JSON output with its intended parser when exact types or escaping matter.

Frequently asked questions