TOML to JSON

How to use this developer tool

1. Paste or upload the toml source you want to inspect.
2. Run Convert to JSON, or press Ctrl/Cmd + Enter.
3. Read the summary, diagnostics, and reported counts before using the output.
4. Copy the result or download it in the shown format.

What this developer tool does

The converter builds a nested object from TOML table paths and assignments, then serializes it with two-space JSON indentation. Array tables append one object for each repeated header.

TOML dates remain strings and TOML-specific type distinctions may not survive JSON. Review consumers that depend on exact date, integer, or float semantics.

Example

The Sample button loads a representative toml source. Running it produces the same kind of json document shown in the result panel, including counts that are calculated from the supplied text rather than fixed examples.

title = "Example"
[owner]
name = "Ada"
active = true
[database]
ports = [8000, 8001]
created = 2026-07-17

Use cases

• Review configuration changes before committing them.
• Diagnose format-specific problems in CI or deployment inputs.
• Create a copy-ready result for documentation or another developer tool.
• Check generated files without exposing project data to a remote service.

Tips for reliable output

• Start with the smallest input that reproduces a problem.
• Keep a copy of the original before replacing configuration files.
• Read warnings and limitations, even when the main result succeeds.
• Validate the output again with the parser used by your application.
• Use UTF-8 when saving downloaded text.

Processing details

Duplicate assignments and table/value conflicts stop conversion. The byte count is measured from UTF-8 encoded JSON output.

The supported parser does not cover multiline strings, all dotted-key quoting rules, special floats, or non-decimal integers. Use a full TOML parser when those appear.