TOML ⇄ JSON Converter
Cargo.toml, pyproject.toml or any TOML file in — clean JSON out. Or convert JSON config back to TOML.
Why convert TOML at all?
TOML is the config language of the modern toolchain — Cargo.toml for Rust,
pyproject.toml for Python, Hugo sites, Netlify and dozens of CLI tools. It is
designed for humans to write by hand: unquoted keys, comments, sections. But almost no JSON
API, database or script wants to consume it, so the moment a config value needs to be read
programmatically, you convert it to JSON.
The reverse direction matters too: generating config files from templates, or handing an infrastructure JSON blob to a tool that only reads TOML. This converter handles both, with tables, nested tables, arrays, arrays of tables, inline tables, booleans, integers, floats and dates mapped to their natural JSON equivalents and back.
FAQ
What happens to comments?
Comments are a TOML-only feature — JSON cannot represent them, so they are dropped when converting to JSON. The JSON → TOML direction emits no comments either.
How are dates handled?
TOML datetime values become JSON strings in ISO form (for example 1987-07-05T17:45:00Z), which is the standard lossless representation.
Is anything uploaded?
No — parsing and generation happen entirely in your browser.