Developer Tools
Convert JSON to YAML
Convert JSON config text to YAML locally in your browser.
Direct Answer
Use the JSON To YAML Converter when a configuration or documentation workflow expects YAML instead of JSON.
What Changes When JSON Becomes YAML
YAML and JSON can represent the same data, but YAML uses indentation and line breaks to show structure instead of braces and brackets, so the converted output looks very different even though the underlying values are identical.
- Curly braces and square brackets become indented block-style lists and mappings
- Double-quoted JSON strings are only quoted in YAML output when necessary to avoid ambiguity
- JSON's true, false, and null map to YAML's true, false, and null or a tilde shorthand
- Deeply nested JSON produces deeply indented YAML, where indentation itself carries meaning
Values That Need Extra Care in the Output
A handful of JSON string values become ambiguous once written in YAML's more permissive syntax, so a good converter quotes them explicitly to avoid changing their meaning.
- A string value like "yes", "no", "true", or "off" must stay quoted or YAML reads it as a boolean
- A string that looks like a number, such as a version "1.0", must stay quoted to remain a string
- A string starting with a special character like * or & needs quoting since those are reserved in YAML
- Long strings with embedded newlines may be converted into YAML's literal block scalar style
How to Use JSON To YAML
- Paste or type your content into the input box.
- The transformed result appears instantly in the result panel below.
- Click Copy result to copy the output to your clipboard.
- Download .txt saves the transformed text as a file.
- Reset clears everything and lets you start over.
Reference
| Feature | Details |
|---|---|
| Purpose | Transform pasted text into a cleaner or different format. |
| Input | Text, lines, lists, or copied content. |
| Result | Transformed text ready to copy or download. |
| Best for | Cleanup, formatting, list preparation, and copy-paste workflows. |
| Category | Developer Tools |
| Works on | Desktop, tablet, and mobile browsers |
Useful Related Tools
Frequently Asked Questions
Why does my converted YAML quote some strings but not others?
The converter only adds quotes when leaving a value unquoted would change its meaning in YAML, such as a string that looks like a boolean, a number, or null. Plain strings without special characters are left unquoted because YAML does not require quotes the way JSON does.
Does converting JSON to YAML lose any data?
No, a correct conversion preserves every key, value, and structural relationship; only the syntax changes, from braces and brackets to indentation. JSON never had comments to begin with, so there is nothing extra for YAML to lose there either.
Why does my YAML output look so different in structure from the original JSON?
YAML expresses nesting through indentation levels instead of explicit braces, so a JSON object with several nested objects becomes a YAML document where each level is indented further than its parent, with no closing symbol to mark where a section ends. This is a purely visual difference; the data hierarchy is the same.
Can I convert JSON with null values to YAML?
Yes, JSON's null typically converts to YAML's null keyword or the tilde shorthand, both of which are equivalent in YAML. Some converters let you choose which representation to use in the output.
Why do my JSON arrays turn into dashes in YAML?
YAML represents a list using a dash and a space for each element, indented under its parent key, which is YAML's block-style equivalent of a JSON array's square brackets. This is standard YAML array syntax, not an error, though YAML also supports an inline flow style if you need a more compact look.
Should I use YAML's block style or flow style when converting from JSON?
Block style, with dashes and indentation, is the YAML convention and is what most converters produce by default, since it is easier to read and diff. Flow style, using JSON-like brackets and braces inline, is valid YAML too and useful for short arrays or objects you want to keep compact, but it is less common for full documents.
Why does my converted YAML fail when I paste it into a Kubernetes manifest?
Kubernetes YAML is sensitive to exact indentation and expects specific top-level keys like apiVersion, kind, and metadata; if the source JSON did not already match that structure, converting it to YAML syntax will not add the required Kubernetes fields. The conversion changes format only, not the schema a specific tool expects.
Does JSON to YAML conversion handle numbers with many decimal places correctly?
Yes, numeric values are carried over as-is since both formats support the same basic number syntax, but if the JSON was generated by a language with floating-point rounding, that same rounding will appear unchanged in the YAML output. The conversion does not introduce new precision issues, but it does not fix existing ones either.