Why is my tab-indented file rejected?

The YAML spec forbids tabs for indentation. Most editors show them as identical to spaces, which makes this a genuinely hard bug to spot by eye — converting is a quick way to find it.

Are anchors and aliases supported?

No. Anchors (&name), aliases (*name), and multi-document streams separated by --- are out of scope. Everything else in ordinary data YAML works.

JSON1 / YAML to JSON

YAML to JSON

Convert YAML to formatted JSON. Handles nested mappings, block and inline sequences, quoted scalars, and comments.

Upload

Processed locally·Your data never leaves your device

InputYAML

Ready

OutputJSON

Converted output appears here as you type.

Good to know

Anchors, aliases, and multi-document streams are not supported. Everything else in common data YAML is.

About this tool

Converting YAML back to JSON is the usual first step when a config file has to be consumed by something that only speaks JSON, or when you want to check what a YAML file actually parses to rather than what it looks like it says.

Nested mappings, block sequences, inline flow collections, quoted scalars, and comments are all handled. Indentation is what defines structure, so a stray tab or a misaligned key is a parse error rather than a silent change in meaning.

Why is my tab-indented file rejected?: The YAML spec forbids tabs for indentation. Most editors show them as identical to spaces, which makes this a genuinely hard bug to spot by eye — converting is a quick way to find it.
Are anchors and aliases supported?: No. Anchors (&name), aliases (*name), and multi-document streams separated by --- are out of scope. Everything else in ordinary data YAML works.