Convert YAML to JSON. Locally, nothing uploaded
YAML is what humans write. CI pipelines, Kubernetes manifests, app configs, and JSON is what many tools and APIs consume. This converter parses YAML in your browser and emits pretty-printed JSON, resolving anchors, aliases, and typed scalars along the way so the output is real, structured JSON rather than a pile of strings. It runs entirely on your device, which is the right default for config files: they routinely contain API keys, connection strings, and other secrets that have no business being pasted into an online converter. Invalid YAML produces a clear error instead of mangled output, so it doubles as a quick syntax check.
How it works
- Drop a .yaml or .yml file below.
- Anchors, aliases, and typed values are resolved as it parses.
- Download pretty-printed JSON, or read the error if the YAML is invalid.
Frequently asked questions
Is it safe to convert a config file with secrets?
Yes, in a way pasting into a typical online converter is not. Parsing happens in your browser and nothing is transmitted, so API keys or connection strings inside the YAML stay on your machine. You can disconnect from the network after the page loads and it still works.
Are YAML anchors and aliases handled?
Yes. Anchors (&name) and aliases (*name) are resolved, so the JSON contains the expanded, fully-realized data structure rather than references. Typed scalars like numbers, booleans, and null are converted to their JSON equivalents.
What about multi-document YAML files?
A YAML file can hold several documents separated by ---. The first document is converted. If you need every document, split them into separate files first. Most single-config YAML files contain just one document anyway.
Why did I get an error?
The input must be valid YAML. The most common culprits are inconsistent indentation and tabs (YAML requires spaces). The error message points at the line, which makes the tool a handy YAML validator as well.