JSON to YAML
Input
{"name":"Ada","enabled":true}Example output
name: Ada
enabled: trueConvert JSON to YAML or YAML back to JSON on one page, entirely in your browser, with 2- or 4-space indentation and optional recursive key sorting. YAML comments do not survive conversion, and some YAML values have no exact JSON equivalent.
| Conversion directions | Two operations: JSON to YAML (default) and YAML to JSON |
|---|---|
| Formatting options | Indentation of 2 or 4 spaces, with optional recursive key sorting |
| Max input size | 5 MB |
| Execution deadline | 3 s |
| Processing location | Browser-only: pasted input is not uploaded |
Input
{"name":"Ada","enabled":true}Example output
name: Ada
enabled: trueInput
name: Ada
enabled: trueExample output
{
"name": "Ada",
"enabled": true
}YAML comments are discarded when converting to JSON, which has no comment syntax. Comments are also not preserved through a YAML to JSON to YAML round trip.
Anchors and aliases are expanded during parsing with a cap of 100 alias resolutions; excessively aliased input is rejected to prevent exponential expansion.
YAML merge keys using '<<' are not specially merged; they arrive as an ordinary '<<' property in JSON. Expand merges before converting if you need merged mappings.
Duplicate keys in YAML input are rejected with an error instead of silently keeping one value.
Multi-document YAML input is rejected; convert one document at a time.
Integers beyond 2^53 and non-finite values such as .nan and .inf have no exact JSON representation and may convert lossily or to null.
JSON Formatter
Prettify, indent, and format JSON strings with customizable indentation and key sorting.
JSON Validator
Validate JSON syntax, inspect structure, and diagnose syntax errors with line and column diagnostics.
JSON ↔ CSV Converter
Convert bi-directionally between JSON arrays of objects and tabular CSV/TSV data with delimiter options, header validation, and spreadsheet formula injection protection.
Base64 Encoder / Decoder
Encode UTF-8 text to standard or URL-safe Base64 and decode Base64 back to text.
YAML comments are always dropped, anchors and aliases are expanded rather than preserved, and integers beyond 2^53 or non-finite values may convert lossily. Duplicate keys and multi-document input are rejected outright.
No. JSON has no comment syntax, so comments are necessarily dropped during YAML to JSON conversion.
Anchors and aliases are expanded during parsing, with at most 100 alias resolutions. Input exceeding that cap is rejected to prevent denial-of-service through exponential expansion.
Objects, arrays, strings, numbers, booleans, and null convert in both directions. Anything outside that set, such as YAML timestamps or binary tags, arrives in JSON as the parser's best representation, not the original tag.
Unquoted YAML scalars are typed by the parser, so a value that looks numeric or boolean in YAML may arrive as a different JSON type than you expect. Quote a scalar to keep it a string.
No. Conversion runs inside an isolated Web Worker in your browser, and pasted input is not uploaded for processing. The browser still requests site assets from the host; clipboard, downloads, and analytics are separate boundaries.