Skip to content
Kordu Tools Kordu Tools

YAML to JSON Converter

Runs in browser

Convert YAML to JSON or JSON to YAML bidirectionally — type preservation, null handling, and configurable indentation.

Last updated 01 Apr 2026

Convert YAML to formatted JSON or JSON to clean YAML with a single click. Handles nested objects, arrays, YAML anchors, aliases, multi-line strings, and all standard scalar types (strings, numbers, booleans, nulls). Configurable indentation. Free, browser-based, no data sent to any server, no signup required.

Indent:
Loading rating…

How to use

  1. 1

    Paste your YAML or JSON

    Paste your YAML config, Kubernetes manifest, GitHub Actions workflow, or any YAML document into the input panel on the left.

  2. 2

    Choose conversion direction

    Click YAML → JSON to convert YAML to formatted JSON output, or JSON → YAML to convert in the reverse direction.

  3. 3

    Configure indentation

    Select 2-space or 4-space indentation for JSON output to match your project's code style.

  4. 4

    Copy the output

    Click Copy to copy the converted result to your clipboard. The output is ready to paste into your editor, terminal, or API client.

Frequently asked questions

What YAML features are supported?
The converter supports YAML 1.2 including nested objects and arrays, multi-line strings (literal | and folded > block styles), YAML anchors and aliases (& and *), document markers (--- and ...), and all standard scalar types: strings, numbers, booleans, and nulls.
Are YAML types preserved correctly in JSON?
Yes. YAML booleans (true/false/yes/no) become JSON booleans, YAML nulls (null/~) become JSON null, numeric scalars become JSON numbers, and quoted strings remain strings. The converter does not silently coerce types.
Will YAML comments appear in the JSON output?
No. Standard JSON does not support comments, so YAML comments (# ...) are stripped during conversion. When converting JSON back to YAML, the output also has no comments since JSON has no comment syntax.
Does it support Kubernetes manifests and Helm charts?
Yes. Kubernetes YAML files, Helm chart values.yaml, and templated YAML (after template rendering) are all valid YAML 1.2 that the converter handles correctly. Multi-document YAML files separated by --- are also supported.
What happens with YAML anchors and aliases?
Anchors (&anchor) and aliases (*anchor) are resolved during conversion. The JSON output contains the fully expanded values — there are no anchor references in JSON output since JSON has no equivalent concept.
Is there a file size limit?
There is no enforced size limit. Very large files may take a moment to convert, but all processing is done locally in your browser with no upload.
Is my data sent to a server?
No. All conversion logic runs client-side using the js-yaml library. Your YAML and JSON content never leaves your device.
Can I validate YAML syntax without converting it?
Yes. Paste your YAML and click YAML → JSON. If the YAML has a syntax error, a clear error message with the line number is shown. If it converts successfully, your YAML is syntactically valid.
Can I convert GitHub Actions workflow YAML to JSON?
Yes. Paste the YAML from your .github/workflows/*.yml file and convert to JSON for programmatic processing, schema validation, or API submission. The converter handles all standard GitHub Actions YAML features including multi-line run scripts and anchors.

YAML to JSON Converter handles bidirectional conversion between YAML and JSON with

correct type semantics. Paste YAML on the left and click YAML → JSON to get a

properly formatted JSON output. Paste JSON and click JSON → YAML to get clean,

human-readable YAML.

The converter uses js-yaml under the hood, which implements YAML 1.2 with full

support for all scalar types, nested objects and arrays, multi-line strings (literal

| and folded > block styles), YAML anchors and aliases (& and *), and document

markers (--- and ...). Type preservation is correct: YAML booleans become JSON

booleans, nulls become null, numbers stay numbers — no silent coercion to strings.

Configurable JSON indentation (2 or 4 spaces) lets you match your project's code

style. Common uses include converting Kubernetes/Helm chart YAML to JSON for API

payloads, transforming CI/CD pipeline YAML for validation, converting GitHub

Actions workflow files for programmatic processing, or simply validating that

a YAML config parses correctly.

Syntax errors are reported clearly so you can locate and fix invalid YAML before

it causes a runtime failure in your application. All conversion runs in your

browser with no data sent to any server.

Related tools

JSON Formatter

Format, validate, and minify JSON instantly — with configurable indentation, error location, and tree view.

CSV to JSON Converter

Convert CSV to JSON or JSON to CSV instantly — paste data or upload a file with full delimiter and header control.

Diff Checker

Compare two texts, code files, or documents side by side — word-level diff highlighting, private and browser-based.

SQL Formatter

Format, beautify, and minify SQL queries with dialect support for MySQL, PostgreSQL, SQL Server, BigQuery, and more.

Learn more

JSON vs XML vs YAML vs TOML: When to Use Each Format

Compare JSON, XML, YAML, and TOML with real config examples. 70% of APIs use JSON (Postman, 2025) - learn which format fits your use case.