What are YAML indentation rules?

YAML uses indentation for nesting; spaces are standard (two spaces per level in most style guides). Tabs are discouraged because parsers and editors disagree on tab width. Sibling map keys must align; drifting one space breaks the document. Always use a converter after hand-edits to confirm the parse matches intent.

What are YAML anchors and aliases?

Anchors (`&id`) mark a node; aliases (`*id`) reference it for deduplication. They are powerful for DRY configs but confuse JSON, which has no equivalent—conversion usually expands aliases into duplicated JSON structures or rejects ambiguous graphs. Expect lossy or expanded output when round-tripping through JSON.

YAML vs JSON for configuration files—which wins?

YAML reads well for multi-line strings and shallow hierarchies—Kubernetes, Helm, GitHub Actions. JSON is safer for machine-generated data, strict schemas, and contexts where comments must not exist. Many teams store canonical JSON in APIs and author YAML only at the deployment edge.

Can YAML contain comments and will they survive JSON conversion?

YAML allows `#` line comments and block comments in some processors. JSON has no comments—converting YAML→JSON drops them. Keep commentary in separate docs or use tools that strip comments before emitting JSON for strict consumers.

Why did my YAML parse as a string instead of a map?

Ambiguous scalars, tabs mixed with spaces, or unquoted colons in plain scalars can change typing. Quotes and explicit tags (`!!str`, `!!int`) disambiguate. Validating with a linter and comparing JSON output from this tool surfaces implicit coercion early.

JSON to YAML Converter

v1.0.0

Convert JSON ↔ YAML with file upload, pretty printing, clipboard tools, format swapping, and character count display.

JSON Input

YAML Output

Output will appear here

JSON Input

Move between JSON and YAML with a clear view of structure—ideal for configs, CI files, and API fixtures without retyping by hand.

Read the full guide →

Frequently Asked Questions

What are YAML indentation rules?: YAML uses indentation for nesting; spaces are standard (two spaces per level in most style guides). Tabs are discouraged because parsers and editors disagree on tab width. Sibling map keys must align; drifting one space breaks the document. Always use a converter after hand-edits to confirm the parse matches intent.
What are YAML anchors and aliases?: Anchors (`&id`) mark a node; aliases (`*id`) reference it for deduplication. They are powerful for DRY configs but confuse JSON, which has no equivalent—conversion usually expands aliases into duplicated JSON structures or rejects ambiguous graphs. Expect lossy or expanded output when round-tripping through JSON.
YAML vs JSON for configuration files—which wins?: YAML reads well for multi-line strings and shallow hierarchies—Kubernetes, Helm, GitHub Actions. JSON is safer for machine-generated data, strict schemas, and contexts where comments must not exist. Many teams store canonical JSON in APIs and author YAML only at the deployment edge.
Can YAML contain comments and will they survive JSON conversion?: YAML allows `#` line comments and block comments in some processors. JSON has no comments—converting YAML→JSON drops them. Keep commentary in separate docs or use tools that strip comments before emitting JSON for strict consumers.
Why did my YAML parse as a string instead of a map?: Ambiguous scalars, tabs mixed with spaces, or unquoted colons in plain scalars can change typing. Quotes and explicit tags (`!!str`, `!!int`) disambiguate. Validating with a linter and comparing JSON output from this tool surfaces implicit coercion early.