TOML to JSON
Convert a TOML config to JSON, with tables and arrays of tables resolved.
Convert YAML config into JSON and see exactly how each value was typed.
The YAML to JSON converter makes a config file's real structure and types explicit. It reads nesting, sequences, flow collections, block scalars, multiple documents and the YAML 1.1 booleans that catch people out.
Converting YAML to JSON is the fastest way to see what a config file really says. The nesting becomes explicit, the types become visible, and a key that is one indent level off its siblings stops being invisible.
The parser handles what configuration files actually contain: mappings, sequences, nesting by indentation, inline flow collections such as [a, b] and {x: 1}, literal and folded block scalars, comments, multiple documents separated by ---, and the full set of scalar types including the YAML 1.1 booleans that trip people up. When parsing fails you get the line rather than a stack trace.
A value that YAML quietly read as a boolean or a number is unmistakable once it is JSON, which is the point of converting.
Both the literal | and folded > forms are read, including their chomping indicators, so embedded scripts survive.
Inline forms such as [a, b] and {x: 1}, which real config files mix freely with block style, are handled.
Documents separated by --- become a JSON array, so a manifest bundle converts in one pass.
A file that will not parse reports the line rather than a stack trace from a parser you did not write.
A Compose file, a CI pipeline, a Helm values file or anything else.
Set how the resulting JSON should be formatted, or minify it.
The types become explicit, which is where most config surprises show up.
Take the JSON to your clipboard or save it as a .json file.
YAML 1.1 treats unquoted yes, no, on and off as booleans. That is the language behaving as specified — quote the value if you meant the word.
They are dropped, because JSON has no syntax for them. That is a genuine loss of information, so keep the YAML as the source of truth.
No. The & and * reference syntax is not resolved. Expand them by hand first, or use a full YAML processor when a file relies on them.
Documents separated by --- are all read, and the result becomes a JSON array with one entry per document.
What people who use the YAML to JSON think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the YAML to JSON. It takes half a minute and no account.
Write the first reviewConvert a TOML config to JSON, with tables and arrays of tables resolved.
Find what runs on a port, with a note on whether it should be exposed.
Re-indent a SQL query into readable clauses, joins and conditions.
Build a valid package.json with scripts, exports and metadata.
Build and edit URL query strings without breaking the encoding.
Build soft extruded UI with paired light and dark shadows.
Score a selector and find out which of two rules actually wins.
Reformat a MAC address between every notation, and decode what it means.