YAML to JSON
Paste your YAML and Happycapy returns well-formed JSON, with the structure, nesting, and data types preserved. Handy for turning config files, CI pipelines, or API specs written in YAML into JSON for tools that need it. Free to start.
Related tools
All tools
How it works
Paste your YAML
Drop in your YAML — a config file, a manifest, or any YAML data.
Set your output preference
Say whether you want pretty-printed (indented) or minified single-line JSON, and how to handle types.
Get valid JSON
The tool parses the YAML and returns well-formed JSON with structure, nesting, and data types preserved.
Copy or download
Copy the JSON straight out, or download it to drop into your project.
Who is this for
Developers and DevOps engineers
Turn YAML configs, CI pipelines, and Kubernetes manifests into JSON for tools and APIs that expect it.
API and integration builders
Convert YAML specs and fixtures into JSON payloads without hand-editing.
Anyone handed a YAML file
Quickly read or reuse YAML data as JSON without learning YAML syntax.
Six prompt-engineering tips that move the needle
Small changes in how you write a prompt make the biggest difference in output.
Check your indentation
YAML needs spaces, not tabs — inconsistent indentation is the most common reason a conversion fails.
Ask for pretty or minified
Request indented JSON for reading, or minified for embedding in code or requests.
Say how to treat types
By default numbers and booleans stay typed — ask for all-strings if that's what you need.
Flag multi-document files
If your YAML has '---' separators, mention it so each document becomes an array element.
Note anchors and aliases
These get expanded into full values in JSON — say if you expect that so the output looks right.
Redact secrets first
Strip API keys or passwords out of config before pasting into any online tool.
What to expect
For valid YAML, the conversion is fast and accurate, preserving structure and data types. Well-formed config files, manifests, and API specs convert cleanly. The main source of errors is invalid YAML — inconsistent indentation or tabs (YAML requires spaces) — so if a conversion looks off, check the source indentation first.
Example: A user pasted a Kubernetes deployment manifest in YAML and asked for pretty-printed JSON. The tool returned valid JSON with the same nested structure — apiVersion, kind, metadata, and spec all preserved, list items as arrays, and replica counts kept as numbers rather than strings.
Good to know
- Invalid YAML (tabs instead of spaces, bad indentation) will fail to convert — the source must be valid first.
- YAML comments are not carried over, since JSON doesn't support them.
- Very large or deeply nested files may need to be split or checked manually for readability.
Frequently asked questions
What does a YAML to JSON converter do?
It reads YAML — a human-friendly data format often used for config files — and outputs the same data as JSON, preserving the keys, nesting, arrays, and value types. YAML and JSON can represent the same data structures, so the conversion is direct.
Are data types preserved?
Yes — numbers stay numbers, true/false stay booleans, and null stays null, rather than becoming quoted strings. If you want everything as strings, say so and the output can reflect that instead.
Can I choose pretty-printed or minified output?
Yes — ask for indented (pretty-printed) JSON for readability, or minified single-line JSON for embedding in code or sending over the wire.
Does it handle multi-document YAML files?
Yes — YAML files with multiple documents separated by '---' can be converted to a JSON array with one object per document. Mention that you have a multi-document file so it's handled correctly.
What about anchors, aliases, and comments?
Anchors and aliases are expanded into their full values in the JSON output, since JSON has no equivalent. Comments are dropped, because JSON doesn't support comments.
Is my data private?
Your YAML is processed to produce the conversion and isn't published anywhere. Still, avoid pasting secrets like API keys or passwords into any online tool — strip or redact sensitive values first.
Is there a size limit?
Small to moderate files convert instantly. Very large YAML files may take longer or need to be split, and extremely deep nesting can be harder to render cleanly — check the output on large inputs.
Ready to create?
Sign up free and put AI agents to work across your tasks, from quick jobs to complete end-to-end workflows, right in your browser, no setup needed.
Get started for free