JSON ⇄ YAML

How to use it

1. Paste JSON or YAML into the left panel - a config file, an API response, a workflow definition.
2. Pick the direction: JSON -> YAML for readable indentation, YAML -> JSON to feed a parser or an API.
3. The result appears on the right as you type; click Convert to force a re-run.
4. Use Copy to grab the result or Download to save it as a .yaml or .json file.
5. Press Sample to load a small object and see how both directions behave.

Common use cases

• Reading dense JSON configs - turn a wall of braces into indented YAML that reviewers can scan quickly.
• Feeding YAML tooling - normalize a manifest to JSON before passing it to a script, linter or API.
• Keeping formats in sync - maintain the same data as YAML for humans and JSON for machines without retyping.
• Debugging quoting issues - round-trip a snippet to see how strings, nulls and nested maps are interpreted.

Why it stays private

Parsing and serialization run in your browser's memory using the bundled js-yaml library. Config files often contain hostnames, tokens or internal paths, and none of that leaves your device.

FAQ

Q: Are YAML anchors and aliases supported? A: Yes. Anchors and aliases are resolved during parsing, so the JSON output contains the fully expanded data.

Q: What happens to comments in my YAML? A: Comments are dropped when converting to JSON, because JSON has no comment syntax. Keep the original file if you need them.

Q: Does it handle multi-document YAML streams? A: No. Files that separate documents with --- are not supported - paste one document at a time.