Question 1

Does this support multi-document YAML files?

Accepted Answer

Yes — YAML files with multiple documents separated by "---" (common in Kubernetes manifests) convert to a JSON array, one entry per document. A single document converts to a single JSON value.

Question 2

What happens to YAML anchors and aliases?

Accepted Answer

Anchors (&name) and aliases (*name) are resolved to their actual value during conversion, so the resulting JSON always contains fully expanded data with no YAML-specific references.

Question 3

Are duplicate keys or tab-indented YAML rejected?

Accepted Answer

Yes. Per the YAML spec, mapping keys must be unique and indentation must use spaces, not tabs. Both are flagged as errors with the exact line so you can fix the source file instead of getting a silently wrong result.

Question 4

Can I control the indentation width for JSON → YAML?

Accepted Answer

Yes — choose 2, 4, or any width between 2 and 8 spaces before converting, so the output matches your project's existing YAML style.

Question 5

How are null values represented?

Accepted Answer

YAML's three ways of writing null — the word "null", "~", and an empty value — all convert to JSON null. Converting back from JSON, null is written as the word "null".

Question 6

Is my file uploaded to a server?

Accepted Answer

No. Both directions run entirely in your browser using a client-side YAML library — your config or data never leaves your device.

JSON to YAML Converter

Result

Frequently Asked Questions

Does this support multi-document YAML files?

What happens to YAML anchors and aliases?

Are duplicate keys or tab-indented YAML rejected?

Can I control the indentation width for JSON → YAML?

How are null values represented?

Is my file uploaded to a server?

Related Tools

CSV to JSON Converter

XLSX to CSV Converter