Convert YAML to JSON

Why Convert YAML to JSON?

Converting YAML to JSON is one of the most common data format transformations in modern software development. Since YAML 1.2 is technically a superset of JSON, every valid JSON document is also valid YAML, but not the other way around. When your web APIs, JavaScript applications, or cloud services require JSON input, converting from YAML is often necessary.

This conversion is particularly valuable for developers who write configurations in human-friendly YAML but need to deploy them as JSON for tools like AWS CloudFormation, Azure Resource Manager templates, or Node.js package manifests. It is also essential when feeding data to REST APIs that only accept JSON payloads, or when storing structured data in NoSQL databases like MongoDB.

Our converter accurately parses all YAML data types and maps them to their JSON equivalents: YAML mappings become JSON objects, sequences become arrays, and scalar values are correctly typed as strings, numbers, booleans, or null. The output is properly indented and formatted for readability.

Key Benefits of Converting YAML to JSON:

• API Compatibility: Produce JSON payloads for REST APIs and web services
• Type Preservation: Numbers, booleans, and null are correctly typed in the output
• Browser Ready: JSON can be parsed natively by all web browsers
• Strict Validation: JSON's strict syntax catches ambiguities present in YAML
• Cloud Deployment: Generate CloudFormation, ARM, or Terraform JSON configs
• Database Storage: Store YAML data in JSON-native databases
• Universal Tooling: Use JSON validators, viewers, and formatters on your data

Practical Examples

Example 1: API Configuration

Input YAML file (api-config.yaml):

server:
  host: 0.0.0.0
  port: 3000
  cors:
    enabled: true
    origins:
      - https://example.com
      - https://app.example.com
database:
  url: mongodb://localhost:27017
  name: myapp

Output JSON file (api-config.json):

{
  "server": {
    "host": "0.0.0.0",
    "port": 3000,
    "cors": {
      "enabled": true,
      "origins": [
        "https://example.com",
        "https://app.example.com"
      ]
    }
  },
  "database": {
    "url": "mongodb://localhost:27017",
    "name": "myapp"
  }
}

Example 2: Package Manifest

Input YAML file (package.yaml):

name: my-web-app
version: 1.2.0
private: true
scripts:
  start: node server.js
  build: webpack --mode production
  test: jest --coverage
dependencies:
  express: ^4.18.0
  cors: ^2.8.5

Output JSON file (package.json):

{
  "name": "my-web-app",
  "version": "1.2.0",
  "private": true,
  "scripts": {
    "start": "node server.js",
    "build": "webpack --mode production",
    "test": "jest --coverage"
  },
  "dependencies": {
    "express": "^4.18.0",
    "cors": "^2.8.5"
  }
}

Example 3: User Data

Input YAML file (users.yaml):

users:
  - id: 1
    name: Alice Johnson
    email: [email protected]
    active: true
  - id: 2
    name: Bob Smith
    email: [email protected]
    active: false
total: 2

Output JSON file (users.json):

{
  "users": [
    {
      "id": 1,
      "name": "Alice Johnson",
      "email": "[email protected]",
      "active": true
    },
    {
      "id": 2,
      "name": "Bob Smith",
      "email": "[email protected]",
      "active": false
    }
  ],
  "total": 2
}

Frequently Asked Questions (FAQ)

Q: What is the relationship between YAML and JSON?

A: YAML 1.2 is designed to be a superset of JSON, meaning every valid JSON file is also valid YAML. However, YAML includes additional features like comments, anchors, multi-line strings, and more relaxed syntax rules. When converting from YAML to JSON, YAML-only features like comments are stripped since JSON does not support them.

Q: Are YAML comments preserved in JSON?

A: No. JSON does not support comments in any form, so YAML comments (lines starting with #) are discarded during conversion. If you need to preserve notes, consider including them as data fields (e.g., "_comment": "This is a note").

Q: How are YAML data types mapped to JSON?

A: YAML strings become JSON strings, YAML integers and floats become JSON numbers, YAML booleans (true/false, yes/no, on/off) become JSON booleans (true/false), YAML null (~, null) becomes JSON null, YAML sequences become JSON arrays, and YAML mappings become JSON objects.

Q: What happens with YAML anchors and aliases?

A: YAML anchors (&) and aliases (*) are resolved during conversion. The referenced data is duplicated in the JSON output at each location where an alias appears. JSON has no equivalent to YAML's reference system, so all references become independent copies of the data.

Q: Can I convert multi-document YAML files?

A: YAML supports multiple documents in one file separated by ---, but JSON has no multi-document equivalent. Our converter handles this by wrapping multiple documents in a JSON array, with each YAML document becoming one element of the array.

Q: Will the JSON output be formatted or minified?

A: The converter produces nicely formatted (pretty-printed) JSON with proper indentation for readability. If you need minified JSON for production use, you can run the output through any JSON minifier tool afterward.

Q: Is the conversion lossless?

A: The data content is preserved losslessly. However, YAML-specific features like comments, anchors/aliases, custom tags, and specific string quoting styles are not representable in JSON and will be converted to their closest JSON equivalents. The actual data values and structure remain identical.