JSON to YAML Converter

Paste JSON, get YAML. Two-space block style, keys in the order you wrote them, and no line wrapping. The kind of YAML humans actually want to read.

Here's a ConfigMap that starts life as JSON:

{
  "kind": "ConfigMap",
  "metadata": {
    "name": "app"
  },
  "data": {
    "COUNTRY": "NO",
    "DEBUG": "on",
    "MODE": "0755",
    "PORT": "8080",
    "TIMEOUT": 30,
    "RETRY": true,
    "TAGS": []
  }
}

And the YAML you get:

kind: ConfigMap
metadata:
  name: app
data:
  COUNTRY: 'NO'
  DEBUG: 'on'
  MODE: '0755'
  PORT: '8080'
  TIMEOUT: 30
  RETRY: true
  TAGS: []

Every string a YAML reader could mistake for something else got single quotes. To a YAML 1.1 parser, NO and on are booleans and 0755 is an octal number. 8080 would be an integer anywhere. The real number and the real boolean stay bare, because that's what they are.

Common use cases

Turning kubectl get -o json output or an API response into a manifest you can edit and commit.

Writing CI and deploy configs. GitHub Actions, GitLab CI and Docker Compose all want YAML, and sometimes the data starts out as JSON from a script.

Making a config people can maintain. Less punctuation, room for comments, and nobody hunting for a missing closing brace.

Things to know

YAML 1.2 is a superset of JSON, so technically your JSON was already valid YAML. But nobody writes YAML that looks like JSON. This tool produces the clean indented style people expect.

Strings with line breaks become block scalars: usually | or |-, depending on whether the string ends with a newline. Strings containing a tab, a byte order mark or a Unicode line separator get double quotes with escapes instead. PyYAML rejects raw tabs in plain values, and 1.1 readers treat those separators as line breaks.

Numbers go through JavaScript first, so 1.0 comes out as 1. Numbers that JavaScript prints with an exponent, like 1e21, get written as 1.e+21, which still reads as a float under YAML 1.1 rules.

The quoting only protects what the tool writes. Edit the file later, type country: NO without quotes, and a YAML 1.1 reader is back to reading false.

Privacy

Conversion runs entirely in your browser. Your configs, secrets and all, stay local.