How to use JSON ↔ YAML
- Choose the direction that matches your source.
- Paste JSON-compatible data or open a UTF-8 file. Load an example to inspect types.
- Run conversion, then check booleans, quoted identifiers, nulls and empty strings.
Check YAML values and their JSON types
yes stays a string, true becomes a boolean, and null remains distinct from empty text.
Load this exact example ↗What changes—and what stays
YAML uses the 1.2 core schema. Aliases, explicit tags, non-string keys, multiple documents and non-finite numbers are rejected. Comments, original quote style and formatting are not retained.
Practical limits
Up to 1 MiB per input, 80 nested levels and 50,000 structured values. CSV supports 10,000 data rows and 200 columns. JSON comparison returns at most 5,000 differences. UTF-8 files only; large jobs stop after six seconds.
Common questions
Will comments survive conversion?
No. JSON does not represent YAML comments. Keep the original file when comments or editorial formatting matter.
Why is yes a string?
This tool uses YAML 1.2 core rules. Other schemas can differ, so verify the parser used by your receiving application.