Loading…
Loading…
Convert YAML ↔ JSON bidirectionally with live validation
Run your projects on Claude Code?
We packaged the .claude config that runs this site — 26 specialist agents, 14 workflow skills, and 6 rule files from 31 real production incidents. From $9.
Get the Claude Code Production Pack — $29YAML is the standard format for Kubernetes manifests, GitHub Actions workflows, Docker Compose files, and most CI/CD configuration. JSON is the universal data interchange format for APIs and tooling. Converting between them is a constant need during DevOps work, configuration debugging, and API testing. This tool uses js-yaml — the same library powering most Node.js YAML tooling — for accurate spec-compliant conversion.
YAML parsing uses js-yaml in DEFAULT_SCHEMA mode, which supports all standard YAML 1.2 types including timestamps, null, booleans, integers, and floats. The parsed JavaScript object is then serialised to JSON with a 2-space indent via JSON.stringify.
JSON-to-YAML takes the parsed JSON object and passes it through js-yaml.dump() with a line width of 120, block style for objects and arrays, and no flow-style — producing clean, readable YAML. Syntax errors are caught and displayed with the parser's line/column position.
A DevOps engineer converts a JSON export from a configuration portal into YAML before committing it to a Kubernetes ConfigMap.
A developer converting a GitHub Actions workflow received as JSON back to YAML for version control.
A backend engineer quickly validates that a YAML config file parses to the expected JSON structure before deploying to production.
Paste YAML into the left panel — JSON appears on the right instantly
Or paste JSON into the right panel — YAML appears on the left
Check the error bar for syntax problems with exact line numbers
Copy the output or download as .yaml or .json file
About the YAML to JSON Converter
Single-document YAML is fully supported. Multi-document YAML (separated by ---) converts the first document. Use the dedicated YAML array syntax for multiple objects in one file.
Yes. js-yaml resolves anchors (&) and aliases (*) during parsing, so the JSON output contains fully expanded values rather than references.
If your input starts with { or [ it is treated as JSON. Any other text is treated as YAML. You can also override direction manually with the toggle.
No — JSON has no comment syntax, so YAML comments are dropped during conversion. They are preserved if you only reformat YAML without converting.
Builder/critic agent prompts with brakes built in
Open →DeveloperFormat, validate & diff JSON — runs entirely in browser
Open →DeveloperTest regex live — railroad diagrams + plain English explained
Open →DeveloperOne color in, full design system out
Open →