Paste JSON, get clean YAML. Built for Kubernetes manifests, Compose files, and CI workflows. 100% in your browser.
Share this tool
Found it useful? Help a fellow developer discover it.
Going the other way, turning a YAML manifest into JSON for an API call?
Convert YAML to JSON
Almost every tool in the modern deployment stack reads YAML, while almost every API speaks JSON. That mismatch is where this converter earns its place. You pull a resource definition out of the Kubernetes API as JSON and need it as a checked-in manifest. You generate a config object in a script and need it as a values.yaml for a Helm chart. You export a workflow definition and need it back under .github/workflows. Converting by hand means counting indentation levels and hoping you did not turn a string into a boolean. This tool does it in one paste, and because the conversion runs entirely on your device, you can safely paste a manifest that still contains secrets.
Kubernetes and Helm
CI and local dev
.yaml file ready to commit.Paste your JSON into the left panel. This page opens already set to the JSON to YAML direction, so the YAML output appears on the right immediately. Copy it to your clipboard or download it as a .yaml file. Everything runs in your browser, so nothing is uploaded.
Yes. YAML is a superset of JSON, so every JSON type maps cleanly onto a YAML equivalent: objects become mappings, arrays become sequences, and strings, numbers, booleans and null carry over exactly. Nothing is dropped going in this direction. The loss only happens in reverse, because YAML comments and anchors have no JSON equivalent.
The syntax will be valid YAML that any Kubernetes parser accepts. Whether the resource itself is valid depends on your JSON containing the fields Kubernetes requires, such as apiVersion, kind and metadata. The converter does not add or validate schema fields, it faithfully represents whatever structure you paste.
YAML quotes a string when leaving it bare would change its meaning. Values such as yes, no, on, off, true, null, and anything that looks like a number or a date would be parsed as a non-string type if left unquoted. Quoting them preserves the exact value from your JSON. This is correct behavior, not noise.
Yes. Use the indent selector in the tool to switch between 2-space and 4-space output. Two spaces is the convention for Kubernetes manifests, Docker Compose and GitHub Actions, so it is the default.
Use the Swap button to flip the direction in place with the current output as the new input, or open the YAML to JSON converter, which is a separate page written around that direction with its own guidance on parsing and API payloads.
Yes. Nesting depth is not limited and structure is preserved exactly. Very deep structures produce heavily indented YAML, which is a readability tradeoff of the format itself rather than a conversion problem. If the result is hard to read, that is usually a signal the config wants splitting into multiple files.
Yes. The conversion runs entirely in your browser using client-side JavaScript. Your JSON is never sent to a server, never logged, and never leaves your device. That is the reason this tool exists in the form it does.
YAML to JSON Converter
Parse YAML into JSON in your browser. Handles anchors, block scalars, and multi-line strings. Powered by js-yaml.
JSON Formatter & Validator
Format, beautify, validate, and minify JSON. Detects BigInt precision issues, duplicate keys, and JSONC comments.
JSON to TOML Converter
Convert JSON to TOML in your browser. Produces valid Cargo.toml, pyproject.toml, and Hugo config syntax with proper table nesting.
.env to JSON / YAML Converter
Read a .env file as JSON or YAML. Handles comments, quotes, export prefixes, and nested keys. Runs in your browser.