TOML to JSON

TOML is the configuration format of Cargo, poetry, pip and a generation of tooling — and JSON is the lingua franca every API and store speaks. When a .toml file has to feed a JSON consumer, you need a real parse: tables to objects, [[headers]] to arrays, values to their native types, not a text patchwork.

Convert TOML to JSON parses standard TOML into a clean JSON document. Tables, arrays of tables, dotted keys, inline arrays and inline tables are all resolved, comments are stripped, and values keep their types.

• Full table support: [table], [nested.table] and dotted-key forms build nested JSON.
• Arrays of tables: Every [[customers]] header appends an element to the array.
• Inline values: Inline arrays and inline tables parse into JSON arrays and objects.
• String forms: Basic ("...") and literal ('...') strings with escapes and Unicode.
• Typed scalars: Integers, floats and booleans become native JSON values.
• Comment stripping: Full-line and inline # comments are ignored.
• Pretty output: The result is formatted, readable JSON.
• Private: All processing happens in your browser; nothing is uploaded.

1. Paste your TOML file into the input pane.
2. Review the live JSON — tables and arrays are resolved automatically.
3. Check numbers and booleans are typed as expected.
4. Copy or download the JSON document.

Example 1 — Cargo tooling. A developer converts a Cargo.toml into JSON to drive a custom build pipeline, with dependencies and features mapping cleanly onto arrays and tables.

Example 2 — Config store. A platform team migrates .toml configs into a JSON-backed store, parsing each file and committing the result after review.

Example 3 — Audit. An engineer converts pyproject.toml to JSON to inspect the effective configuration as a tree, catching a mistyped table path that was invisible in the flat file.

Example 4 — Round-trip editing. A developer converts TOML to JSON, edits it, and converts back with the companion tool.

• Real parsing: Tables, arrays and types come out as actual JSON structures.
• Standards-faithful: Handles the common TOML 1.0 surface correctly.
• Clean output: Comments vanish and values keep their types.
• Zero data movement: The file is parsed locally and never uploaded.
• Instant results: Live output updates with every keystroke.