CONVERT · ENTIRELY IN YOUR BROWSER
YAML to JSON
Translate a YAML configuration into strict, readable JSON. Catch indentation and mapping errors before moving configuration between systems.
YAML to JSON workspace
LOCAL WORKSPACEYour converted data will appear here.
Table preview · up to 5 rows and 20 columns
A PRACTICAL EXAMPLE
See the transformation.
Input
app: TidyFormats
private: true
formats:
- JSON
- CSVOutput
{
"app": "TidyFormats",
"private": true,
"formats": ["JSON", "CSV"]
}How to use YAML to JSON
- Paste one YAML document or open a YAML file.
- Choose the JSON indentation.
- Convert and review the JSON before downloading.
Understand YAML values before converting
YAML 1.2 distinguishes true from the string yes. Quote identifiers such as postal codes when their exact characters matter. Comments are omitted because JSON has no comment syntax. The output below uses two-space indentation.
Input
enabled: true
answer: yes
code: "00123" # keep as textOutput
{
"enabled": true,
"answer": "yes",
"code": "00123"
}Common problems and how to fix them
An indentation error appears
Use spaces, not tabs, for YAML indentation, and align sibling keys at the same level. Check the lines just before the reported error as well as the marked line.
My configuration uses multiple documents or custom tags
Convert one document at a time and resolve application-specific tags in the originating application. This tool does not interpret custom tags or YAML merge keys.
An alias or numeric value is rejected
Circular references and excessive alias expansion cannot be converted safely. JSON also cannot represent .inf or .nan; replace these with a meaningful supported value in your source.
Limitations and supported input
Uses YAML 1.2 core schema. Custom tags, merge keys, complex mapping keys, non-finite numbers, and multiple documents are not supported. Alias expansion is limited. Comments and YAML styling are not preserved.
Files must be UTF-8 text and no larger than 10 MiB. Very deep or complex documents may exceed the 15-second processing limit. JSON numbers use JavaScript precision; keep long identifiers as strings.
Your data stays on your device
All parsing and conversion happens in a local browser worker. Your input is not sent to a server or saved in browser storage. Closing or reloading the page clears this workspace. Read our privacy explanation.
GOOD TO KNOW
A little clarity.
Simple tools. Straight answers.
Are YAML comments kept?
No. JSON has no comment syntax, so only the data is retained.
Does “yes” become true?
Under YAML 1.2 core schema, yes is a string. Use true or false for booleans.
KEEP THINGS MOVING