Developer Data

YAML to JSON

Input

name: my-app
port: 8080
debug: false
tags:
  - web
  - api
server:
  host: localhost
  timeout: 30

What to do

Output

{
  "name": "my-app",
  "port": 8080,
  "debug": false,
  "tags": [
    "web",
    "api"
  ],
  "server": {
    "host": "localhost",
    "timeout": 30
  }
}

Processed in your browser · nothing is uploaded

Local · config subset, anchors refused not guessed

Converts YAML to JSON, handling maps, sequences, scalars, comments and block scalars — the subset configuration files are actually written in.

How to use the yaml to json

1 Paste your input. The result appears immediately.

2 Pick the operation you want.

3 Copy the result, or save it as a file.

It is worth being straight about what is not supported: anchors, aliases, tags and multi-document streams are refused with a message rather than misparsed, because getting those subtly wrong is worse than declining them. The type resolution follows YAML 1.1, which is where the famous surprises live — `yes`, `no`, `on` and `off` are booleans, not strings, which is why the Norway country code `NO` becomes `false` in a YAML file unless quoted. That is not a bug in the parser, it is the specification, and it has broken real deployments. Quote anything that could be read as another type.

Questions

Why did NO become false? −

YAML 1.1 treats yes, no, on and off as booleans. The Norway country code has to be quoted. This is specified behaviour, not a bug.

Are anchors and aliases supported? +

Is YAML a superset of JSON? +

Why does my indentation break it? +

Is my data sent anywhere? +

Sources

YAML 1.2 specification

Was this tool any good?

INTERNAL SIGNAL ONLY · WE USE IT TO FIND TOOLS WORTH REBUILDING