Question 1

How do I convert YAML to JSON online?

Accepted Answer

Paste your YAML into the input editor and the converter instantly emits JSON in the right pane. The output preserves types correctly (numbers stay numbers, true/false stay booleans, null stays null) and strips comments. Click Copy to send to clipboard or Download to save as a `.json` file. Conversion runs entirely in your browser — no upload, no server.

Question 2

What is the difference between YAML and JSON?

Accepted Answer

YAML uses indentation for nesting, supports comments (`#`), allows unquoted strings, and provides anchors/aliases for re-use. JSON uses braces and brackets, requires double-quoted keys, has no comments, and no reference syntax. Both represent the same data model (maps, sequences, scalars), so converting between them is mostly mechanical — except YAML's comments and anchors are lost in the JSON form.

Question 3

Is YAML a superset of JSON?

Accepted Answer

Yes — since YAML 1.2, every valid JSON document is also valid YAML. This means a YAML parser can read JSON files directly, and you can mix JSON-style flow syntax (`{}`, `[]`) inside a YAML document. The reverse is not true: most YAML cannot be parsed as JSON because of indentation, comments, anchors, and unquoted strings.

Question 4

How does YAML to JSON conversion handle types?

Accepted Answer

Type inference follows YAML 1.2 core schema. Booleans: `true`/`false` (case-insensitive) become JSON booleans; everything else stays a string. Null: `null`, `~`, or empty value becomes JSON null. Numbers: digits matching integer or float patterns become JSON numbers. Strings: quoted values always stay strings; unquoted values are tested against bool/null/number patterns first, falling back to string.

Question 5

Why are `yes` and `no` strings instead of booleans?

Accepted Answer

YAML 1.2 narrowed booleans to only `true` and `false` (case-insensitive). YAML 1.1 (the older spec, still used by some Ruby tooling) treated `yes`/`no`/`on`/`off` as booleans, which silently broke configs — most notably Norway's country code `NO` becoming `false`. Modern parsers like js-yaml, PyYAML 6+, and Snakeyaml default to 1.2 behavior. Our converter is YAML 1.2 strict.

Question 6

Can I convert nested YAML to JSON?

Accepted Answer

Yes — the converter handles arbitrarily deep nesting. Each indentation level adds one level of nesting in the output JSON. Sequences inside maps, maps inside sequences, and recursive combinations all convert correctly. The maximum depth is limited only by your browser's call stack (typically thousands of levels — far beyond any realistic config).

Question 7

How do I convert Kubernetes YAML manifests to JSON?

Accepted Answer

Paste your Kubernetes manifest (Pod, Deployment, Service, ConfigMap, etc.) and the JSON output is ready to POST to the Kubernetes API server, which accepts both formats. Useful when you have a YAML manifest in source control but need to feed it to a tool that only accepts JSON (some Helm post-renderers, custom controllers, or programmatic CI logic). Validate the output with `kubectl apply --dry-run=client -f -` (Kubernetes accepts JSON via stdin too).

Question 8

How do I convert Docker Compose YAML to JSON?

Accepted Answer

Paste your `docker-compose.yaml` and copy the JSON output. Compose itself doesn't accept JSON directly, but several Compose-adjacent tools do (Kompose for K8s migration, container-orchestration platforms with custom Compose interpreters). Useful for programmatic transformations where JSON is easier to manipulate. Validate the YAML side first with `docker compose config` before converting.

Question 9

How do I convert Ansible playbooks (YAML) to JSON?

Accepted Answer

Paste your Ansible playbook YAML and the converter emits JSON. Ansible itself only consumes YAML, but conversion is useful for documentation tooling, GraphQL/REST APIs that accept playbook definitions, and custom CI pipelines. Note: Ansible's Jinja2 template expressions (`{{ var }}`) are stored as plain strings in JSON — they're not evaluated by the converter.

Question 10

How do I convert OpenAPI YAML specs to JSON?

Accepted Answer

Paste your `openapi.yaml` (or `swagger.yaml`) and download the JSON output. Many API tools and code generators accept either format, but some legacy ones (older Swagger UI builds, certain enterprise gateways) require JSON. The converter preserves `$ref` pointers, schema definitions, and example bodies exactly. After conversion, validate with the official OpenAPI validator (Spectral, openapi-cli) to confirm schema compliance.

Question 11

Why is my YAML failing to parse?

Accepted Answer

Most common causes: (1) Tabs in indentation — YAML forbids tabs entirely. (2) Inconsistent indentation — siblings must align exactly. (3) Missing space after `:` — `key:value` is wrong; `key: value` is right. (4) Missing space after `-` in a sequence — `-item` is a string starting with dash. (5) Unquoted special characters at start of value (`@`, `` ` ``, `%`). (6) Anchors/aliases (`&name`/`*name`) — unsupported by this converter (use a full YAML library if you need them). The error message shows line/column where parsing failed.

Question 12

Does YAML support comments after conversion to JSON?

Accepted Answer

No — JSON has no native comment syntax (RFC 8259). Comments in your YAML source are stripped during conversion. If you need to preserve documentation, three options: (1) keep YAML as the source of truth and treat JSON as a derivative; (2) use JSON5 or JSONC (variants with comments) instead of strict JSON downstream; (3) move comments to a sidecar `.md` file alongside the JSON.

Question 13

What about YAML anchors and aliases?

Accepted Answer

Anchors (`&name`) and aliases (`*name`) let YAML reuse a node by reference. JSON has no equivalent — every value is a fresh copy. When converting, this converter expands anchors inline (each alias becomes a full copy of the referenced data). The data is preserved but the JSON is larger and shared-reference structure is lost. If your YAML uses heavy anchor reuse (e.g., shared Compose service templates), the JSON output may be 2-3× larger than the source.

Question 14

Can I convert YAML files with multiple documents (---)?

Accepted Answer

Multi-document YAML streams (separated by `---` on their own line) represent multiple top-level values in one file — common for Kubernetes manifests bundling several resources. JSON has no equivalent (single root value per document). Split the YAML into separate documents first (one resource per file) and convert each individually, or wrap them in a JSON array `[doc1, doc2, doc3]` if your downstream consumer accepts that.

Question 15

Is this YAML to JSON converter safe for sensitive data?

Accepted Answer

Yes — all conversion runs in your browser via JavaScript. No YAML is uploaded to a server, logged, or transmitted anywhere. Verify by opening DevTools → Network: no requests fire when you paste or convert. Safe for Kubernetes secrets (after base64-decode), API keys in YAML configs, JWT payloads, and any sensitive data. The page works offline once loaded.

Question 16

What YAML version does this converter target?

Accepted Answer

YAML 1.2.2 — the latest published spec (October 2021), strict mode. Key implications: (1) only `true`/`false` are booleans (the Norway-bug-fix change from 1.1); (2) integer/float parsing follows JSON-compatible patterns; (3) explicit type tags (`!!str`, `!!int`) are honored when present. Most modern parsers (PyYAML 6+, js-yaml, Snakeyaml, Go yaml.v3) target YAML 1.2.

Question 17

How does this compare to the `yq` command-line tool?

Accepted Answer

Functionally similar for the common case (`yq -o json file.yaml` does YAML to JSON conversion). Differences: this online converter is a browser tool — no install, instant feedback, easy to share a URL with colleagues. `yq` is better for CI pipelines, large files (streaming support), JSONPath-like queries, and complex transformations. Both target YAML 1.2 strict mode and produce equivalent JSON for standard inputs.

Question 18

Can I convert JSON back to YAML?

Accepted Answer

Yes — use the JSON to YAML Converter (sister tool linked below). Round-tripping YAML → JSON → YAML loses YAML-specific features: comments, anchors/aliases (expanded), explicit type tags, and multi-document streams. The data model itself is preserved exactly, so values, types, and structure round-trip perfectly. For configs that include comments, keep YAML as the source of truth.

YAML to JSON Converter

lightbulb Tips

YAML to JSON Converter

YAML to JSON calculator

lightbulb Tips