Convert TOML documents into JSON with configurable indentation and compact-mode output.
Convert TOML documents into JSON with configurable indentation and compact-mode output. Convert TOML documents into JSON with configurable indentation and compact-mode output.
JSON is the lingua franca of the web: every API speaks it, every editor can highlight it, and every language has a parser in its standard library. TOML excels at human-edited configuration but is less universally supported as a runtime data exchange format. When you need to feed a TOML config into a tool that only consumes JSON (web playgrounds, schema validators, code generators, etc.), a reliable TOML-to-JSON converter saves the day.
The conversion is mostly lossless because both formats are
expressive enough to represent the same primitives. The few
TOML-specific types (multi-line strings, dates) translate to
plain strings; the few JSON-specific values (null) translate
to the JSON literal null, which TOML has no native equivalent
of.
The converter offers a pretty-print toggle (with 2/4-space
indentation) and a compact mode (single line). For very large
config files, the compact output is much easier to paste into
a curl request body. The swap button moves the JSON output
back into the input box so you can re-edit and re-export as
TOML again.
After conversion, validate the JSON with a schema validator
(ajv, jsonschema) before pushing it to a downstream tool.
The TOML parser is strict: it will reject unquoted scalars that
start with digits, inline tables with comments, and other common
mistakes. Use the error messages to fix the source document,
not the JSON.
Suppose you maintain a pyproject.toml snippet that lists your tool's runtime configuration under [tool.beetools]. To feed the same configuration into a JavaScript build pipeline that only accepts JSON, run the snippet through this converter. The output preserves the table hierarchy, so a nested block like [tool.beetools.cache] becomes { "tool": { "beetools": { "cache": { ... } } } }. Dotted keys collapse into nested objects on the way out, mirroring how the TOML parser initially built them. Once you have the JSON, validate it with ajv or jsonschema before passing it downstream -- the converter only translates syntax.