TOML vs JSON
TOML (Tom's Obvious Minimal Language) is designed for configuration by humans: comments, dates, dotted keys, and no braces. JSON is designed for machine interchange: no comments, strict quoting, universal parser support. Converting between them is a daily chore when your Rust/Python project (TOML config) talks to a web API (JSON).
What this converter handles
- Tables
[section]and sub-tables[a.b.c]→ nested JSON objects. - Key-value pairs — strings, integers, floats, booleans, datetimes.
- Arrays and inline tables
key = { a = 1, b = 2 }. - Comments (
#) are stripped; keys are quoted properly. - JSON → TOML preserves nesting with standard
[table]headers.
Limits
Exotic TOML is only partially supported: array-of-tables [[items]] converts as arrays of objects, but multi-line strings and other advanced TOML syntax are not handled. Everything runs locally; nothing is uploaded.
When you'd use this
Porting a pyproject.toml into a CI pipeline that expects JSON env, converting Cargo.toml metadata for a dashboard, or generating a JSON config from a TOML template. Pair it with the JSONL Tools page for the full data-pipeline kit.