YAML input
Choose a .yaml or .yml file, or paste YAML directly.
Drop a YAML file here, or click to choose one
Supported: .yaml and .yml
JSON output
Convert YAML to see JSON here.
Conversion notes
- YAML comments are lost during conversion because JSON has no comment syntax.
- YAML timestamps are converted to ISO 8601 strings so the JSON remains portable.
- This converter uses YAML 1.2 behavior: unquoted yes, no, on and off stay strings; only true and false become booleans.
YAML to JSON, locally
Paste YAML or open a .yaml or .yml file to convert it into JSON. Choose readable, pretty-printed output or compact minified JSON, then copy or download the result.
The converter resolves YAML anchors and aliases before producing JSON. For inputs separated by ---, you can output one JSON array or a separate JSON result for each document.
Your YAML stays on your device
Conversion happens in the browser, not on a server.
- YAML is read and parsed locally in your browser.
- There is no upload endpoint for your input.
- The source is open for inspection (MIT).
- After the first visit, the app can work offline.
You can verify this in your browser’s Network panel while converting: no request contains your YAML. Read the source.
How to use it
-
Add YAML
Choose a .yaml or .yml file, drop one on the page, or paste YAML into the text field.
-
Choose output options
Select pretty or minified JSON. If the YAML has multiple documents, choose an array or separate outputs.
-
Copy or download
Review the parsed JSON, then copy it or download a .json file.
FAQ
Are my YAML files uploaded?
No. Parsing and conversion run in your browser. The tool has no upload step or server-side converter.
What happens to YAML anchors and aliases?
They are resolved and expanded in the JSON output. Recursive aliases are reported as an error because JSON cannot represent circular references.
How are multiple YAML documents handled?
For YAML separated with ---, you can choose a single JSON array or one JSON output for each document. A single YAML document remains a single JSON value.
Are comments and timestamps preserved?
JSON has no comments, so comments are lost. YAML timestamps are converted to ISO 8601 strings so the output stays ordinary, portable JSON.
Will no or yes become booleans?
No. The parser uses YAML 1.2 behavior: unquoted yes, no, on and off stay strings. Only true and false become booleans.
What if the YAML is invalid?
The converter shows a parse error with a line and column when the parser can identify them. It does not act as a standalone YAML validator.