Convert JSON to YAML Online for Free

JSON to YAML: Making Structured Data Readable as a Config File

JSON is easy for a program to generate and parse, but a JSON document more than a few levels deep — full of braces, quotation marks around every key, and no visual indentation to speak of — is genuinely hard for a person to scan. A JSON-to-YAML converter takes that same data and renders it the way a human-authored config file would be written: nested mappings shown through indentation instead of braces, lists as dashed items instead of bracketed arrays, and quotes only where a string actually needs them. This tool performs that rendering directly in your browser — paste in JSON, and a properly formatted YAML document appears immediately, generated by JavaScript running on your own device rather than a server elsewhere.

This direction of conversion comes up constantly in infrastructure and DevOps work specifically, because tools like Kubernetes, Docker Compose, and most CI/CD platforms expect their configuration written as YAML even when the data describing that configuration originates somewhere else — a database, an internal tool, or a script that only knows how to emit JSON. Rather than hand-writing an equivalent YAML file and keeping it in sync by hand, generating it directly from the JSON that already exists removes an entire category of copy-paste mistakes.

How to Convert JSON Into YAML With This Tool

1. Paste a JSON value into the left panel, or click File to load a .json file from your device — its contents are read locally and placed into the same box, with conversion running once the underlying YAML library has finished loading in the background.
2. Glance at the small status indicator under the input box: green tells you the text parsed as valid JSON, while red spells out the specific problem, such as a missing closing brace or a trailing comma the parser refuses to accept.
3. Pick an indent width of two or four spaces for the generated YAML, matching whatever convention the rest of your project already uses.
4. Toggle Sort keys if you'd rather see the YAML's mapping keys alphabetized rather than left in the order your original JSON defined them.
5. Use the swap control to flip direction and check how the generated YAML would parse back into JSON, without leaving the page or losing your original input.
6. Copy the finished YAML to your clipboard, or download it as a .yaml file ready to drop into a project.

As with the reverse direction, none of this depends on a network request — a JSON document, however deeply nested, is rendered by the browser's own JavaScript in well under a second.

Why Convert JSON to YAML in the First Place

• Generating a Kubernetes manifest or Helm values file from application data. A deployment script that already builds its configuration as a JSON object in memory often needs to hand that same configuration to a tool that only reads YAML.
• Writing a Docker Compose file programmatically. Building service definitions as JSON inside a script, then rendering the result as YAML, is often simpler than string-templating YAML's whitespace-sensitive syntax directly.
• Producing a CI/CD pipeline definition from a template engine. Some pipeline generators assemble configuration as JSON internally and need a final YAML rendering step before the file can actually be committed and used by GitHub Actions, GitLab CI, or a similar platform.
• Making an API response or exported settings file easier for a person to review. A configuration object that's about to be reviewed, edited, or approved by a human being is usually easier to work with as indented YAML than as a wall of braces and quoted keys.
• Migrating a JSON-based config format to a YAML-based one. Some tools change their supported config format over a major version, and converting existing JSON settings into the new expected YAML shape is often the fastest way to carry old configuration forward.
• Documenting an API's response shape as a readable example. Pasting a real JSON response into this tool and sharing the YAML version in a wiki page or a pull request description is sometimes simply easier to read at a glance than the same data wrapped in braces and quotes.

How the Renderer Decides What the Output Looks Like

Turning JSON into YAML sounds like it should be a purely mechanical, one-way mapping, but the underlying library — js-yaml's dump() function — actually makes a handful of formatting decisions that are worth understanding rather than taking for granted. A JSON object becomes an indented YAML mapping, with each key written plainly and unquoted whenever the key is a simple identifier-like string; a string value gets quoted only when it needs to be, such as when it starts with a character that would otherwise be misread as YAML syntax, contains a colon-and-space sequence, or looks like it could be mistaken for a number or a boolean if left bare. Arrays become YAML's dash-prefixed block sequences by default rather than bracketed inline lists, which keeps the output consistent with how most hand-written YAML in the wild is actually formatted.

It's worth being precise about where each option lives, since the browser tool on this page and the plain function call behind the API aren't identical in what they expose. The metered API's json-to-yaml endpoint calls dump() with no extra options at all — meaning it always uses the library's own defaults for indentation and key ordering, with no parameter to request four-space indents or alphabetized keys instead. The Indent and Sort keys controls you see on this page are conveniences layered on top of that same underlying function specifically for the browser tool, passed to dump() as explicit options before rendering; if you need that same level of control from a script or a server calling the API directly, you'd currently need to reformat the returned YAML yourself after the fact, since the endpoint's only input is the json string itself.

How JSON Values Render as YAML

JSON value	Resulting YAML
An object, e.g. {"name": "Alice"}	An indented mapping: name: Alice
An array, e.g. ["one", "two"]	A dashed block sequence, one item per line
true, false, or null	The bare word, unquoted
A plain string like "hello"	Written unquoted, as hello
A string that looks like a number, e.g. "007"	Quoted in the output, so it isn't misread as a number on reload
An empty object {} or empty array []	Rendered inline as {} or [] rather than an indented block

Manual Formatting vs. Using This Converter

• Hand-writing the YAML directly instead of converting. Reasonable for a short, one-time config file, but it means re-typing every key and value from the JSON source, with every future update needing to happen in two places at once.
• String-templating YAML from inside a script. Works until a value contains a character that needs escaping or quoting in YAML — a colon, a leading dash, a value that looks numeric — at which point a plain string template quietly produces invalid or misleading output.
• A general-purpose data-serialization library. Many programming languages have one capable of emitting YAML from an in-memory structure, and reaching for it makes sense when this conversion is one step inside a larger automated build or deployment process.
• This tool's metered API. The same underlying dump() rendering is available as a REST endpoint accepting a json string and returning YAML text, suited to a server or script that needs the conversion directly rather than a person pasting into a page.

How This Tool Handles Your Data

As with the reverse tool, the rendering from JSON to YAML shown above runs locally: your JSON is handed to the YAML library loaded into the page, and the resulting document is generated without any round trip to a server. The same underlying rendering is also offered as a metered API call for use outside a browser tab — inside a build pipeline, say, or a command-line wrapper script — and going that route means the JSON payload is included in a request that does reach our server, in contrast to using the page directly, which never sends the data anywhere to produce a result.

Why does the YAML output leave some of my strings unquoted but wrap others in quotes?

A string is only quoted when leaving it bare would create ambiguity or invalid YAML — for instance, if it starts with a character YAML treats as syntax, contains a colon followed by a space, or reads exactly like a number or a boolean word. Ordinary text is rendered unquoted, matching how most hand-written YAML files are actually styled.

Can I control the indent width or key ordering through the API, not just on this page?

Not currently. The metered API's endpoint accepts only the json string itself and always renders with the underlying library's default indentation and key order; the Indent and Sort keys controls are options exposed by this page's own JavaScript, layered on top of that same rendering function specifically for the browser tool.

What happens to a deeply nested JSON object when it's rendered as YAML?

Each level of nesting becomes an additional level of indentation in the output, following whichever indent width you've selected, with mapping keys and list items lining up underneath their parent exactly the way a person would write the same structure by hand.

Will converting to YAML and back to JSON give me the exact same document I started with?

For the data itself, yes — the values and structure round-trip faithfully. What isn't preserved is anything YAML doesn't represent from the original, such as object key order if you had Sort keys enabled during the JSON-to-YAML step, or any comments you added to the YAML afterward, since JSON has no concept of comments to carry them back.

Does this tool add any comments or extra formatting to explain the generated YAML?

No. The output is the plain rendering of your JSON's structure and values, with no inserted comments, header banners, or annotations — exactly the document the underlying library produces, ready to be used or edited as-is.

My original JSON had numbers formatted as strings, like a version number. Will they still look like strings in the YAML?

Yes. A JSON value that arrived as the string "1.10" rather than the number 1.10 is rendered in quotes in the YAML output specifically so it isn't misread as a number when the file is loaded again later — this matters for values like version numbers or zip codes, where losing a leading zero or a trailing digit on reload would silently change the value's meaning.

Related Tools

Working the other direction, YAML to JSON parses a YAML document back into ordinary JSON using the same safe-schema library described above. If your underlying data is closer to a spreadsheet than a config file, JSON to CSV flattens the same kind of JSON into tabular rows instead of a YAML document. And when your data started out as tag-based markup rather than JSON, XML to JSON is the tool worth running first, before feeding its output into this converter.