Does converting YAML to JSON remove comments?

Yes. JSON has no comment syntax, so any line starting with `#` in your YAML is dropped during conversion. If you need to keep the documentation, hold on to the original YAML file alongside the generated JSON.

What happens to YAML anchors and aliases when converting to JSON?

They're fully resolved: the value an alias points to gets expanded inline at every place it's referenced. The resulting JSON has no YAML-specific constructs left — just plain values and structures.

Is converting JSON to YAML lossless?

Yes. Because YAML 1.2 is a superset of JSON, this direction always converts without loss — every type, nested structure, and value is preserved exactly as it was.

Is it safe to paste config files with secrets into this tool?

Yes. The entire conversion runs in your browser via JavaScript — nothing is uploaded to a server, stored, or logged anywhere.

Can I convert a Kubernetes manifest from YAML to JSON?

Yes, this tool handles Kubernetes manifests, Helm values, Docker Compose files, and Ansible playbooks without any special setup — just paste the YAML in and the converter parses standard YAML 1.2 syntax including multi-document structures and nested lists.

YAML ↔ JSON Converter

Convert YAML to JSON or JSON to YAML instantly in your browser. Paste your config or data, choose the direction, and copy the result. Free, no sign-up required.

Updated April 2026

Shift + Enter to Copy

INPUT YAML Valid YAML

OUTPUT JSON JSON

{
  "apiVersion": "apps/v1",
  "kind": "Deployment",
  "metadata": {
    "name": "my-app",
    "labels": {
      "app": "my-app"
    }
  },
  "spec": {
    "replicas": 3,
    "selector": {
      "matchLabels": {
        "app": "my-app"
      }
    },
    "template": {
      "spec": {
        "containers": [
          {
            "name": "my-app",
            "image": "nginx:latest",
            "ports": [
              {
                "containerPort": 80
              }
            ]
          }
        ]
      }
    }
  }
}

33 lines · 534 chars

How to use the YAML to JSON converter

Pick a direction, paste, get validated output instantly

1. Pick a direction

Toggle "YAML → JSON" or "JSON → YAML" at the top of the tool.

2. Paste your input

Drop it in the left panel, or click "Paste" to grab it straight from your clipboard.

3. Copy or download the result

The output renders instantly on the right — a "Valid" badge confirms the structure parsed correctly.

What this YAML to JSON converter does

Accurate conversion in both directions

Real-time validation

A green "Valid" badge confirms your input is well-formed before you copy anything out.

Resolves anchors and aliases

YAML's & anchors and * aliases are fully expanded in the resulting JSON — no dangling references.

Lossless JSON to YAML

Since YAML 1.2 is a superset of JSON, this direction always converts cleanly, preserving every type and nesting level.

Runs entirely in your browser

No sensitive config — API keys, secrets, connection strings — ever leaves your device.

Examples

What changes and what doesn't

Situation

Result

`#` comment in the YAML

Stripped out — JSON has no comment syntax

`&ref` anchor and `*ref` alias

Fully expanded in the output JSON

JSON → YAML

Always lossless — every valid JSON document is already valid YAML

When you'll reach for this tool

The scenarios that come up most often

Kubernetes and Helm

Feed YAML manifests into CI/CD pipelines that only accept JSON, or convert Helm values back for readability.

OpenAPI and Swagger specs

Convert a YAML API spec to JSON when your toolchain requires it, or flip it back for human review.

Docker Compose and Ansible

Move service configs or playbooks between formats depending on which tool downstream is consuming them.

GitHub Actions workflows

Debug or adapt YAML workflow files by converting them to JSON for schema validation.

Common mistakes

Expecting comments to survive the conversion

JSON has no comment syntax — keep the original YAML alongside the generated JSON if you need the documentation.

Not realizing aliases get expanded

The resulting JSON contains no YAML-specific constructs — every anchor and alias is fully resolved into its actual value.

Inconsistent indentation in the source YAML

YAML is indentation-sensitive — mixing tabs and spaces is the single most common cause of parsing errors.

Why use this converter

It handles the edge cases that trip up simpler converters — anchors, aliases, comments — correctly instead of silently dropping or mangling them.

Everything runs client-side in your browser, so it's safe to convert sensitive config files, templates with embedded API keys, and infrastructure definitions without them ever touching a server.

YAML vs. JSON

Same data, different audiences

YAML

JSON

Syntax

indentation, minimal punctuation

curly braces and brackets

Supports comments

yes (`#`)

Used by

Kubernetes, Docker Compose, Ansible

REST APIs, data interchange

Every valid JSON file is...

valid YAML (YAML 1.2 is a superset)

—

Frequently asked questions

YAML uses indentation and minimal punctuation, which makes it easier for humans to hand-edit — that's why Kubernetes, Docker Compose, and Ansible all use it for config. JSON uses braces and brackets with stricter syntax, and it's the standard for REST APIs and data interchange. Because YAML 1.2 is a superset of JSON, any JSON document is already valid YAML.

References

YAML 1.2 Specification

The official spec defining how YAML is a superset of JSON.

JSON.org

The canonical reference for the JSON data format.

Kubernetes: YAML vs JSON

Official guidance on when Kubernetes accepts YAML or JSON.