YAML to JSON
Paste YAML — a config file, a Kubernetes manifest, a CI pipeline, a Docker Compose file — and get equivalent JSON. Block-style maps, sequences and scalars are all supported. Runs entirely in your browser.
Convert YAML to JSON in the browser
YAML is the format of choice for human-edited configuration — Kubernetes manifests, GitHub Actions and GitLab CI pipelines, Docker Compose files, Ansible playbooks, and countless app config files. JSON is the format machines prefer. This converter turns one into the other so you can take a config you already have and hand it to a tool, API or library that only understands JSON, without rewriting it by hand.
How the conversion works
The parser reads block-style YAML: indentation defines structure, - introduces sequence items, and key: value pairs build maps. Scalar values are type-inferred the way YAML expects, so replicas: 3 becomes a number and enabled: true becomes a boolean, while quoted strings keep their literal text. The result is pretty-printed JSON with the same nesting as your source, ready to copy or download.
When you would use it
Validating a manifest that a JSON-only linter rejects, converting a config into a request body, diffing two pipeline files as JSON, or simply reading a deeply nested YAML file in a structured tree view. Once you have JSON, the rest of the workspace opens up: format and validate it, query it with JSONPath or jq, compare two versions with the diff tool, or convert it onward to CSV. Flip the direction dropdown to go the other way when you need to hand a JSON config back to a YAML-based tool.
Privacy
The converter runs client-side and works offline after the page loads. Config files often contain hostnames, resource limits, environment names and other details you would rather not paste into an upload-based site — here nothing is transmitted, logged or stored.
Frequently asked questions
Which YAML features are supported?
The common subset that covers almost every config file: block mappings, block sequences, nested structures and scalars with type inference (numbers, booleans and null). Anchors, aliases, tags and complex flow syntax are not supported.
Why convert YAML to JSON at all?
Many tools, APIs and libraries accept JSON but not YAML. Converting lets you paste a manifest into a JSON-only validator, feed a config into a program that expects JSON, or inspect a pipeline file in the JSON tree view.
How are indentation and types handled?
Two-space indentation defines nesting. Unquoted scalars are inferred: true/false become booleans, numeric values become numbers, null/~ become null, and quoted strings keep their exact text.
Is my config uploaded?
No. Conversion happens entirely in your browser — nothing is sent to a server or stored.