Why Convert YAML to JSON?

While YAML is great for human-readable configs, JSON is the standard for APIs, data interchange, and programmatic manipulation. Converting YAML to JSON lets you use config data in applications and services.

Example Conversion

YAML:

server:
  host: localhost
  port: 8080
  ssl: true
database:
  connection: postgres://localhost/mydb
  pool_size: 10

JSON:

{
  "server": {
    "host": "localhost",
    "port": 8080,
    "ssl": true
  },
  "database": {
    "connection": "postgres://localhost/mydb",
    "pool_size": 10
  }
}

YAML Features Supported

Common Use Cases

• API integration — Convert YAML configs to JSON for REST API calls
• Kubernetes debugging — Get JSON output for kubectl commands
• Config validation — Validate YAML structure using JSON Schema
• Data processing — Parse YAML files in languages with better JSON support
• Documentation — Generate JSON examples from YAML source files

YAML Gotchas

YAML has some surprising behaviors that affect conversion:

The Norway Problem

# YAML interprets these as booleans!
countries:
  - NO    # false
  - YES   # true

Solution: Quote values that look like booleans: "NO"

Numbers vs Strings

version: 1.0   # Number 1.0
version: "1.0" # String "1.0"
zip: 01234     # Octal number!
zip: "01234"   # String "01234"

Programmatic Conversion

JavaScript (Node.js)

const yaml = require('js-yaml');
const fs = require('fs');

const doc = yaml.load(fs.readFileSync('config.yaml', 'utf8'));
const json = JSON.stringify(doc, null, 2);
console.log(json);

Python

import yaml
import json

with open('config.yaml') as f:
    data = yaml.safe_load(f)
    
json_string = json.dumps(data, indent=2)
print(json_string)

Command Line (with yq)

# Convert YAML file to JSON
yq -o=json config.yaml > config.json

# Or pipe from stdin
cat config.yaml | yq -o=json

Pro Tips

• 💡 Watch indentation — YAML is whitespace-sensitive. Inconsistent indentation causes parse errors.
• 💡 Comments are lost — JSON doesn't support comments, so YAML comments won't transfer.
• 💡 Validate the output — Use the JSON Validator to ensure correct JSON syntax.

Related Tools

• JSON to YAML — Convert JSON to YAML
• JSON Validator — Validate your JSON output
• JSON Schema Validator — Validate structure

Common Mistakes & Pro Tips

• Every valid JSON document is already valid YAML — YAML 1.2 is a strict superset of JSON, so pasting JSON into a YAML parser works and round-trips cleanly. This is why JSON-to-YAML is lossless, while the reverse can lose YAML-only features like comments and anchors.
• Anchors and aliases get expanded, comments get dropped — An anchor (&base) referenced by an alias (*base) is resolved into a full copy of that value in the JSON, so shared structure is duplicated rather than linked. Comments (# ...) have no JSON equivalent and are discarded entirely during conversion.
• Indentation must be spaces, never tabs — YAML forbids tab characters for indentation and relies on consistent spaces to define nesting. A single stray tab causes a parse error, and mixing indentation widths can silently change which key a value belongs to.
• The Norway problem: unquoted booleans and nulls — In YAML 1.1 (still used by many parsers), bare words like no, off, yes, and on parse as booleans, so a country code NO can become false, and ~ or empty means null. Quote ambiguous scalars ("NO", "3.10") to force them to stay strings.
• Multi-document streams only convert one document — A YAML file can contain several documents separated by ---, but a single JSON value can't hold all of them at once. Converters typically take the first document or require you to wrap them, so split multi-doc files or expect only the first to appear.