YAML to JSON

YAML comments do not exist in JSON and are silently dropped. If your config carries documentation in comments, this conversion loses it.

Runs in your browser // nothing is uploaded

Loading converter

What survives the conversion

Derived from what each format is able to store, not from what the conversion promises.

Kept

Nested structure
Data types

Lost

Comments
Anchors and references

Settings used

Parsed with js-yaml, re-serialised as JSON with two-space indentation.

When not to convert

Not for a config file people edit by hand. Comments are usually why it is YAML.

About these formats

Data

What is a YAML file?

YAML is an indentation-based data format designed to be easier for humans to write than JSON, and it is a superset of it. It supports comments and reusable anchors, which is why it dominates CI pipelines and infrastructure configuration. Indentation errors are its classic failure mode.

Read the format guide

Data

What is a JSON file?

JSON is a lightweight text format for structured data, standardised as ECMA-404. It supports objects, arrays, strings, numbers, booleans and null, and nothing else. That deliberate minimalism is why it replaced XML as the default format for web APIs and configuration.

Read the format guide

Common questions

Does converting YAML to JSON lose anything?

Yes. Comments, Anchors and references cannot be carried into JSON and are dropped. YAML comments do not exist in JSON and are silently dropped. If your config carries documentation in comments, this conversion loses it.

Are my files uploaded when I convert YAML to JSON?

No. The conversion runs in your browser tab, so the file is never transmitted and the page works offline once loaded.

What settings does Filoven use for YAML to JSON?

Parsed with js-yaml, re-serialised as JSON with two-space indentation.

When should I not convert YAML to JSON?

Not for a config file people edit by hand. Comments are usually why it is YAML.