Developer troubleshooting
YAML ⇄ JSON Converter
Basic nested mappings and arrays
🔒 See this tool’s privacy notes for local processing and external service details. Site analytics are described in our privacy policy.
Quick guide
What can YAML ⇄ JSON help you do?
Free YAML / JSON converter for basic nested mappings, arrays, quoted strings, booleans, and numbers. Block scalars, anchors, aliases, tags, and flow collections are not supported.
Best for
Convert a small, straightforward configuration with nested mappings, lists, strings, booleans, and decimal numbers into JSON for inspection. This is a basic YAML subset converter, useful for simple examples but not a replacement for a full configuration parser.
How to use it
Paste YAML on the left and choose YAML to JSON, or paste valid JSON on the right and choose JSON to YAML. Use spaces for indentation. Sample supplies a nested example and converts it; Clear removes both inputs and the status message.
How to read the result
JSON output uses two-space indentation. Recognized plain numbers, booleans, and null become typed JSON values, while quoted strings remain strings. Comments are discarded. Editing the source clears untouched generated output; a failed conversion clears its destination and reports an error.
Privacy and limits
The widget runs its own local subset parser and serializer, without requesting a YAML library from a CDN or submitting configuration text. Replace credentials and private endpoints with placeholders before sharing output; converting a configuration does not remove its secrets.
Block scalars, anchors, aliases, tags, flow collections, and tab indentation are unsupported. Empty collections and complex nested lists may not round-trip faithfully. Quote values containing #, which the parser otherwise treats as a comment, and validate results with the application that will consume them.
Frequently Asked Questions
YAML or JSON?
YAML is more readable (indents, comments) — used for configs. JSON parses faster — used for APIs.