YAML to JSON Converter

YAML to JSON Converter: Free Online Tool for Instant, Accurate Format Conversion

The modern software stack runs on two dominant data formats: YAML for human-authored configuration and JSON for machine communication. Configuration files, CI/CD pipelines, and infrastructure manifests live as YAML. REST APIs, webhook payloads, browser storage, and message queues use JSON. Moving between these formats is a constant need for developers working across cloud infrastructure, API integration, and data pipelines.

This free YAML to JSON converter transforms any valid YAML document into clean, correctly typed JSON instantly in your browser. It handles all YAML features: mappings, sequences, block and flow scalars, anchors and aliases, multiple documents, YAML 1.1 and 1.2 type semantics, and Unicode. No server round-trip, no account needed — just paste and convert.

Whether you are extracting data from a Kubernetes manifest to feed into a JSON API, converting an OpenAPI spec from YAML to JSON for a tool that only accepts JSON, transforming Ansible variables to JSON for a Python script, or debugging a YAML configuration by viewing it as structured JSON, this tool gives you the output you need immediately.

The Relationship Between YAML and JSON

YAML 1.2 was designed to make JSON a strict subset. The specification states that YAML can be viewed as a natural superset of JSON, offering an extended feature set while remaining compatible with the existing JSON specification. This means every valid JSON document is valid YAML — but not every valid YAML document is valid JSON.

The features that YAML has which JSON lacks — and which are therefore lost or transformed during YAML-to-JSON conversion — include:

• Comments: YAML supports # comments; JSON has no comment syntax. All comments are stripped during conversion.
• Anchors and aliases: YAML's &name and *namereuse mechanism. On conversion, aliases are expanded to their full values — the resulting JSON may contain duplicated data where YAML used references.
• Multiline strings: YAML's literal (|) and folded (>) block scalars become regular JSON string values with embedded \n characters.
• Non-string keys: YAML allows any scalar as a mapping key (integers, booleans). JSON requires string keys. The converter converts non-string keys to their string representation.
• Multiple documents: YAML files can contain multiple documents separated by ---. JSON cannot represent multiple documents in one file. The converter handles multi-document YAML by converting each document into a JSON array or NDJSON.

Type Mapping: YAML to JSON

Understanding how YAML types map to JSON types is essential for correct conversion.

YAML Mappings to JSON Objects

A YAML mapping (key-value structure) becomes a JSON object. Keys are always converted to JSON strings. A YAML integer key like 200: "OK" becomes the JSON object key"200". Boolean YAML keys (true:) become the JSON key"true".

YAML Sequences to JSON Arrays

Both block sequences (dash-prefixed list items) and flow sequences ([a, b, c]) become JSON arrays. Nested sequences become nested JSON arrays. Mixed-type sequences (strings and numbers in the same list) are valid in both YAML and JSON.

YAML Scalars to JSON Primitives

Scalar type resolution is the most nuanced part of YAML-to-JSON conversion because YAML's type inference rules differ between YAML 1.1 and 1.2.

YAML booleans: YAML 1.2 recognizes only true and false(any case) as booleans. YAML 1.1 additionally recognizes yes, no,on, and off as booleans — a common source of bugs in Kubernetes YAML where a field value of yes becomes JSON true unexpectedly. The converter defaults to YAML 1.2 semantics.

YAML integers: bare integers (42, -7) become JSON numbers. YAML 1.1 octal (0755 = 493) and hexadecimal (0xFF = 255) are converted to their decimal JSON equivalents.

YAML floats: 3.14, 1.5e10, -0.5become JSON numbers. YAML's special float values .inf, -.inf, and.nan have no JSON equivalent — the converter converts these to nullwith a warning.

YAML null: null, ~, and empty values all become JSON null.

YAML strings: quoted strings always become JSON strings. Unquoted strings that do not match any YAML type pattern also become JSON strings. Unicode content is preserved.

Handling YAML Anchors and Aliases in JSON

YAML's anchor and alias mechanism enables DRY configuration that JSON cannot represent. A YAML file might define a default configuration block with an anchor and reference it in multiple places using aliases, with merge keys to override specific values. On conversion to JSON, aliases are expanded to their full values and merge keys are resolved by merging the referenced mapping into the containing object. The result is valid JSON with duplicated data where YAML used references — JSON has no reference mechanism, so the deduplication is lost in conversion.

Understanding this expansion is important for Helm chart debugging: Helm's _helpers.tplpatterns use YAML anchors for shared configuration, and the expanded JSON shows the actual values that Kubernetes receives after all anchors are resolved.

Handling YAML Block Scalars in JSON

YAML block scalars (multiline strings) become JSON strings with embedded escape sequences. A literal block scalar (|) preserves newlines as \n in the JSON string, with special characters like double quotes escaped as \". The trailing newline behavior depends on the chomp indicator: the default clip mode preserves one trailing newline, strip mode (|-) removes it, and keep mode (|+) preserves all trailing newlines.

A folded block scalar (>) converts single newlines to spaces (folding the lines into a paragraph), while preserving blank lines as actual newlines. This is the YAML-idiomatic way to write long strings without them wrapping in the source file, and the JSON output will contain the folded string as a single line with only paragraph-breaking newlines preserved.

Multi-Document YAML to JSON

A YAML file can contain multiple documents separated by ---. This is common in Kubernetes, where a single manifest file may contain multiple resources (a Service and a Deployment in the same file), and in some CI/CD configurations.

JSON has no multi-document equivalent. The converter offers three options: a JSON array wrapping all documents (most useful for programmatic processing), newline-delimited JSON (NDJSON) with one JSON object per line (the format expected by many streaming APIs and log processors), or conversion of the first document only (for cases where only the primary resource is needed).

Practical Use Cases for YAML to JSON Conversion

Kubernetes API Calls and Debugging

The Kubernetes API server uses JSON for all communication, while developers write manifests in YAML. When you run kubectl apply -f manifest.yaml, kubectl converts the YAML to JSON before sending it to the API server. Understanding the JSON representation helps debug webhook admission controllers (which receive and return JSON), server-side apply strategies, and JSON patch operations. Convert your manifest to JSON to see exactly what the API receives.

For existing resources, kubectl get pod my-pod -o json shows the full server-side JSON including status fields, managed fields, and resource versions. This is often more useful than the YAML output for debugging because it shows the complete object state as the API server sees it.

Helm Chart Debugging

Helm renders YAML templates into Kubernetes manifests. Use helm template to output the rendered YAML, then convert to JSON to feed into JSON-aware tools: jqfor filtering and transforming, JSON Schema validators for structure validation, or custom scripts that process the manifest programmatically. Converting to JSON also resolves all Helm template substitutions and shows the final values.

OpenAPI Spec Format Switching

Some API tools, validation libraries, code generators, and gateways require OpenAPI specifications in JSON format. AWS API Gateway import, some Swagger codegen tools, and certain API management platforms accept only JSON OpenAPI specs. Convert your YAML-authored spec to JSON for these tools without maintaining duplicate files. The conversion is lossless for OpenAPI specs because they avoid YAML-only features like comments and anchors.

Ansible Variables to JSON

Ansible uses YAML for variable files (host_vars, group_vars). When integrating Ansible with external tools that expect JSON — REST APIs, Python scripts using the json module, monitoring and CMDB systems — convert the YAML variable file to JSON. The converter handles Ansible's use of YAML anchors and multiline strings in variable files.

GitHub Actions and CI/CD Debugging

GitHub Actions workflow YAML has complex data structures for matrix configurations, job outputs, and conditional expressions. Converting to JSON makes the data structure easier to understand when debugging matrix strategy configurations, understanding how job outputs are structured, or tracing expression evaluation. The JSON view is especially helpful for complex matrix configurations with includes and excludes.

Using jq with YAML Data

jq is a powerful command-line JSON processor, but it only processes JSON input. To use jq with YAML data, first convert to JSON. The combination is extremely powerful:yq -o=json input.yaml | jq '.items[] | select(.metadata.namespace == "production") | .metadata.name'extracts resource names from a specific namespace in a Kubernetes manifest. Converting YAML to JSON as a preprocessing step unlocks the full power of jq for YAML-native data.

Programmatic YAML to JSON Conversion

Python

The most common approach uses PyYAML and the standard json library:import json, yaml; data = yaml.safe_load(yaml_string); json_out = json.dumps(data, indent=2). Install with pip install pyyaml. Use yaml.safe_load rather thanyaml.load — safe_load disables arbitrary Python object deserialization for security.

For YAML 1.2 semantics (avoiding yes/no being treated as booleans), use ruamel.yaml:from ruamel.yaml import YAML; y = YAML(typ='safe'); data = y.load(stream).

Node.js

Using js-yaml: const yaml = require('js-yaml'); const data = yaml.load(yamlString); const json = JSON.stringify(data, null, 2). Using the yaml package (more TypeScript-friendly):import YAML from 'yaml'; const json = JSON.stringify(YAML.parse(yamlString), null, 2). Both support GFM-style YAML with anchors, aliases, and multi-document files.

Command Line

Using yq (mikefarah's version): yq -o=json input.yaml. Using Python: python3 -c "import sys,json,yaml; print(json.dumps(yaml.safe_load(sys.stdin),indent=2))" < input.yaml. Using Node.js: npx js-yaml input.yaml.

Go

Parse YAML to an interface and marshal to JSON:import "gopkg.in/yaml.v3"; var data interface{}; yaml.Unmarshal(yamlBytes, &data); jsonBytes, _ := json.MarshalIndent(data, "", " ").

Ruby

require 'yaml'; require 'json'; puts JSON.pretty_generate(YAML.safe_load(yaml_string))

JSON Output Formatting Options

The converter offers several JSON output formats: pretty-printed with 2-space indentation (the standard convention for JSON in files and documentation), pretty-printed with 4-space indentation (for projects that prefer it), minified with no whitespace (smallest output, ideal for API payloads and environment variables), and sorted keys (alphabetical key order for deterministic output and git-diff-friendly storage). The pretty-printed 2-space format is the default and most universally readable.

Common Conversion Errors and Solutions

YAML Parse Error: Indentation Problems

The most common YAML errors are indentation-related: tabs instead of spaces (YAML forbids tab characters in indentation), inconsistent indentation levels, or misaligned continuation lines. Run the input through the YAML formatter to validate and normalize indentation before converting. The formatter reports specific line numbers for parse errors.

Unexpected Boolean Conversion

If a YAML value yes or on was intended as a string but became JSON true, the original YAML is using YAML 1.1 boolean semantics. Fix at the source by quoting the value: value: "yes". This is especially important for port numbers, country codes, and any value that coincidentally matches YAML 1.1 boolean patterns.

Large Integer Precision

Integers larger than 2^53 - 1 (about 9 quadrillion) cannot be exactly represented as JSON numbers in most parsers due to IEEE 754 double-precision limitations. The converter warns when this occurs and optionally converts large integers to JSON strings to preserve precision. This affects distributed system IDs (Twitter/X Snowflake IDs, Instagram IDs) and 64-bit Unix timestamps.

Privacy and Performance

All YAML parsing and JSON serialization runs entirely in your browser using JavaScript. No YAML content — configuration values, infrastructure topology, environment variables with credentials, Kubernetes Secrets, or schema definitions — is transmitted to any server. The converter handles documents of any practical complexity (thousands of lines, deep nesting) without performance issues. The tool works offline once the page is loaded.