82 characters · 17 words · 82 bytes (UTF-8)
Output will appear here
Click in the output to select all text
82 characters · 17 words · 82 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Convert INI configuration files and sections to JSON and back.
Bidirectional converter between YAML configuration and JSON data.
Convert JSON data to clean YAML syntax with configurable indentation.
Format, indent, validate, and beautify JSON with custom spacing.
Beautify and format YAML documents with standardized indentation.
Validate YAML syntax and identify structural or indentation errors.
TOML has become the config format of choice for tools like Cargo, Poetry, and various static site generators, thanks to its clear, minimal syntax, but plenty of scripts and APIs still need that same configuration as JSON. This converter transforms TOML into JSON or JSON back into TOML in either direction, correctly handling TOML's tables, arrays of tables, and typed values like dates and integers. It's useful for developers working across Rust, Python, or other TOML-heavy ecosystems who need to bridge config data into JSON-based tooling, or vice versa. The conversion preserves data types faithfully so numbers, strings, and dates aren't accidentally reinterpreted. Since everything runs client-side in your browser, your config is never uploaded to a server, and there's no signup required. Paste your TOML or JSON below to convert it instantly.
TOML is a minimal, readable configuration file format used widely in tools like Rust's Cargo, Python's Poetry, and many static site generators.
Yes, it works bidirectionally - paste either format and the tool detects and converts it to the other.
TOML's native date and datetime types are converted into ISO 8601 date strings in the resulting JSON.
Yes, TOML's array-of-tables syntax ([[section]]) is converted into a corresponding JSON array of objects.
No, the entire conversion runs locally in your browser using client-side JavaScript - nothing is sent to a server.
Yes, standard TOML configuration files from Rust, Python, or other ecosystems convert cleanly since they follow the standard TOML specification.
Yes, invalid TOML is flagged with an error before conversion, so you know the output reflects valid source data.