JSON to YAML Converter

Paste JSON and get readable YAML — ideal for config, CI, and manifests.

Quick presets

Indent

Add --- document marker Sort keys

JSON

YAML

Strings that YAML would misread — yes, no, on, 1.0, values starting with @ or containing : — are quoted automatically (the classic “Norway problem”).

Runs in your browser — nothing you enter is uploaded or stored.

ToolFeather · Clean indent

Scratchpad auto-saved

Stored in this browser (localStorage)

About the JSON to YAML Converter

YAML and JSON describe the same kinds of data, but YAML's indentation-based style is easier for humans to read and edit, which is why config files, CI pipelines, and Kubernetes manifests favour it. When you have JSON from an API or a tool and need it as YAML, this converter does the translation.

It parses your JSON, then serialises it as YAML with two-space indentation: objects become key-value maps, arrays become dash-prefixed lists, and scalars are quoted only when necessary (for example, strings that look like numbers, booleans, or contain special characters). Empty objects and arrays are rendered as {} and [].

Conversion happens entirely in your browser. For very exotic structures you may want to review the output, but for typical config data the result is clean and paste-ready.

Examples

{"a":1} → a: 1

{"ports":[80,443]} → a ports: list with two dash items.

Nested objects → indented sub-maps, ready for a config file.

Frequently asked questions

4 answers

Why convert JSON to YAML at all?

YAML is often the required format for configuration — Docker Compose, GitHub Actions, Kubernetes — and it's easier to read and hand-edit than JSON.

Are strings always quoted?

No. Strings are quoted only when needed — for example if they'd otherwise be read as a number, boolean, or contain YAML-significant characters.

Does it support comments?

JSON has no comments, so none are produced. You can add YAML comments manually afterwards.

Is anything sent to a server?

No — the conversion is fully client-side.