What is the difference between YAML and JSON?

They represent the same data structures — objects, arrays, strings, numbers. YAML is indentation-based, allows comments, and is friendlier to write by hand (used by Kubernetes, Docker Compose, CI configs). JSON is stricter and universal for APIs. Any JSON document is also valid YAML.

Do comments survive YAML to JSON conversion?

No — JSON has no comment syntax, so comments are dropped during conversion. Converting back to YAML will not restore them, so keep the original file if the comments matter.

Why did my unquoted YAML value convert strangely?

YAML guesses types for unquoted scalars: no becomes false, 3.10 becomes the number 3.1, and country codes like NO can turn into booleans. When a value must stay a string, quote it in the YAML source.

Is it safe to convert configs containing secrets?

Yes. Conversion runs entirely in your browser — your data never leaves your device and nothing is stored on any server.

YAML ↔ JSON Converter

Convert between YAML and JSON formats instantly

100% Private — your data never leaves your device

Your YAML and JSON are converted entirely in your browser — they never leave your device.

Parse Error

Input: Output: Keys:

YAML vs JSON — Key Differences:

YAML uses indentation for structure — easier to read and write by hand (used in Docker, Kubernetes, GitHub Actions)
JSON uses braces {} and brackets [] — universal data exchange format for APIs
YAML supports comments with # — JSON does not
YAML strings often don't need quotes — JSON strings always require double quotes