MLToolslabel · build · tune · ship

Developer

YAML, JSON & TOML Converter

Configs for training, deployment and CI come in three syntaxes. Paste one, get the other two, with parse errors located precisely. Anchors and multi-document YAML are handled; TOML tables and arrays of tables round-trip; JSON output keeps key order.

Loading the tool…

How it works

01

Paste

The input format is detected; override it if needed.

02

Read errors

Indentation mistakes, tab characters, unquoted colons and duplicate keys are reported with line numbers.

03

Copy the output

Any of the three, with indent and quoting options for YAML.

Formats, limits and the numbers that matter

YAML gotchas

yes, no, on, off become booleans in YAML 1.1 parsers; version strings like 1.10 become numbers. The converter quotes such values on output and warns on input.

TOML

Dates and times are native types in TOML; they are written as ISO strings in JSON and YAML.

Multi-document

YAML files with --- separators convert to a JSON array; the reverse writes separators.

Common questions

Which YAML version?

YAML 1.2 by default, which is what modern tools use; the 1.1 boolean quirk is only flagged, not applied.

Can it validate against a schema?

Convert to JSON and use the JSON Schema tool.

Docker compose and Kubernetes files?

Yes; they are plain YAML.

Next in the workflow

JSON Formatter, Validator & Tree ViewerFormat, validate, minify and explore JSON as a collapsible tree, with a path query and error positions.JSON Schema Generator & ValidatorGenerate a JSON Schema from sample data and validate documents against a schema with precise error paths..env, JSON & Compose Environment ConverterConvert between .env files, JSON objects, docker-compose environment lists, Kubernetes ConfigMaps and shell exports.