Runs entirely in your browser — nothing leaves this page.
YAML / JSON / TOML
Validate YAML, JSON and TOML with precise error location — convert and pretty-print between all three.
Input format
Validating and converting configuration
Paste YAML, JSON or TOML and the format is detected for you; convert to any of the three, or keep the same format to reformat it. Syntax errors come back with the line and column, which is the part a failing pipeline usually does not tell you.
Conversion goes through a real parse, so what you get out is what a parser sees — not a text transformation.
Why did my value become false?
The YAML 1.1 boolean rule: unquoted no, off and n parse as false, and yes, on and y as true. The country code NO is the classic casualty. Quote any value where the string form matters.
Why does my YAML fail with a tab error?
YAML forbids tabs for indentation entirely — only spaces. An editor set to insert tabs produces a file that looks correctly indented and never parses.
Why does TOML conversion refuse my document?
TOML requires a table — a key-value mapping — at the root. A JSON or YAML document whose top level is an array or a scalar has no valid TOML representation, so it is rejected rather than silently wrapped.
What happens to comments?
They are lost. Comments live outside the data model, so any conversion through a parser drops them. Convert to explore or to generate, not to migrate a hand-maintained file you care about.
Related tools: YAML diff, K8s manifest validator and Base64.