handyman
Hazuu Tools

YAML to JSON Converter

Convert YAML to JSON format — paste, convert, and copy instantly.

Input YAML
Output JSON
Converted JSON will appear here...
info

About YAML to JSON Converter

YAML to JSON Converter is a free online tool that transforms YAML configuration data into clean, formatted JSON. YAML is the dominant syntax for DevOps tooling — Docker Compose files, Kubernetes manifests, GitHub Actions workflows, Ansible playbooks, and Helm charts all use it — because its indentation-based structure is easy to write by hand. JSON is the universal data interchange format used by REST APIs, JavaScript applications, databases like MongoDB, and virtually every programming environment that consumes structured data.

When you need to feed YAML-defined configuration into an API endpoint, pass a Kubernetes spec to a JSON-only SDK, or inspect a deeply nested YAML structure in a JSON tree viewer, converting manually is tedious and error-prone. This tool does it in one click using the js-yaml library, the same parser used by thousands of Node.js projects. It handles every standard YAML feature: scalars, sequences, mappings, multi-line block strings, anchors, aliases, and inline flow syntax — outputting either 2-space or 4-space indented JSON depending on your preference.

Every conversion happens entirely inside your browser. Your YAML text is never uploaded, logged, or transmitted anywhere. That means secrets, tokens, and internal service configurations in your config files stay on your machine. There are no file-size limits, no accounts, and no cost — just paste and convert.

star

Key Features

check_circle

Accurate type preservation

Strings, integers, floats, booleans, nulls, arrays, and nested objects all map to their correct JSON equivalents. A YAML true becomes a JSON true — not the string "true".

check_circle

Configurable indentation

Toggle between 2-space and 4-space indentation to match the style guide of your project or the requirements of the tool consuming the JSON.

check_circle

YAML anchors and aliases resolved

Anchors (&) and aliases (*) are fully dereferenced in the output, so the JSON contains the actual repeated values rather than unresolved references.

check_circle

Multi-line string support

Both literal block scalars (|) and folded block scalars (>) are parsed correctly, preserving newlines or collapsing them as YAML specifies.

check_circle

Inline error reporting

If your YAML contains a syntax error, the exact error message from js-yaml appears immediately above the editor — no guessing which line broke the parse.

check_circle

100% client-side and private

The js-yaml parser runs entirely in your browser. Kubernetes secrets, API tokens, and CI/CD credentials in your configs are never sent to a server.

help

How to Use

01

Paste YAML

Copy your YAML data and paste it into the left input pane.

02

Convert

Click "Convert" to transform your YAML into JSON format.

03

Copy Result

Use the copy button to grab your JSON output.

code_blocks

Example

A Kubernetes-style config with nested mappings, a sequence, and type-specific values converts to correctly indented JSON with all types preserved.

YAML input
service:
  name: api-gateway
  port: 8080
  tls: true
  replicas: 3
  tags:
    - production
    - v2
  metadata:
    owner: platform-team
    reviewed: null
JSON output
{
  "service": {
    "name": "api-gateway",
    "port": 8080,
    "tls": true,
    "replicas": 3,
    "tags": [
      "production",
      "v2"
    ],
    "metadata": {
      "owner": "platform-team",
      "reviewed": null
    }
  }
}
lightbulb

Common Use Cases

  • arrow_circle_right

    Feeding Kubernetes manifests into JSON-only SDKs

    Kubernetes specs are written in YAML but many client libraries — and tools like kubectl debug output — work with JSON. Convert the manifest first to pipe it into programmatic tooling without rewriting it by hand.

  • arrow_circle_right

    Testing REST APIs that accept structured config

    When an API endpoint expects a JSON body and you authored the payload in YAML for readability, convert it here before pasting into Postman, Insomnia, or curl.

  • arrow_circle_right

    Inspecting GitHub Actions and CI pipeline configs

    JSON tree viewers and diff tools give a clearer picture of deeply nested workflow syntax than raw YAML. Convert the workflow file to explore it in a structured inspector.

  • arrow_circle_right

    Migrating configuration between tools

    Some infrastructure tools output YAML while downstream tools expect JSON. Convert once and avoid maintaining two copies of the same configuration in different formats.

  • arrow_circle_right

    Validating YAML data types before code integration

    Because js-yaml resolves every YAML type rule, seeing the JSON output confirms whether a value parsed as a number, boolean, or string — catching subtle type coercion bugs before they reach production.

quiz

Frequently Asked Questions

What is YAML to JSON Converter? expand_more
YAML to JSON Converter is a free online tool that converts YAML markup into equivalent JSON data. It parses your YAML structure and outputs properly formatted JSON that can be used in APIs, configuration files, and JavaScript applications.
Does it preserve data types? expand_more
Yes. The converter accurately preserves all YAML data types including strings, numbers, booleans, nulls, arrays, and nested objects. The resulting JSON faithfully represents the same data structure as your original YAML.
Is my data secure? expand_more
Yes. All conversion happens entirely in your browser using JavaScript. No data is sent to any server, ensuring your configuration files and sensitive data remain completely private and secure.
What YAML features are supported? expand_more
The tool supports all standard YAML features including scalars (strings, numbers, booleans, nulls), sequences (arrays), mappings (objects), anchors and aliases, multi-line strings (literal and folded block scalars), and inline flow syntax.
Can I use multi-document YAML? expand_more
Only the first document in a multi-document YAML file is converted. If your YAML contains multiple documents separated by ---, only the content of the first document will appear in the JSON output.
How is this different from the YAML Formatter? expand_more
The YAML Formatter keeps your data as YAML and re-indents or normalises it for readability. This converter changes the format entirely — the output is JSON, not YAML. Use the formatter when you want tidy YAML; use this converter when you need JSON for an API, SDK, or tool that does not accept YAML.
How is this different from the XML to JSON converter? expand_more
Both tools output JSON, but they accept different input formats. The XML to JSON converter takes XML markup — angle-bracket tags with attributes — as its input. This tool accepts YAML — indentation-based key-value syntax. Choose the tool that matches the format you are starting from.
Can I convert Kubernetes YAML to JSON? expand_more
Yes. Kubernetes manifests are valid YAML and convert cleanly. This is useful when passing a spec to a JSON-only API client or inspecting it in a JSON diff tool. Anchors and aliases used in Helm-style templates are also resolved in the output.
Why does a YAML boolean like "yes" or "on" convert to true in JSON? expand_more
YAML 1.1 (used by js-yaml by default) treats yes, no, on, off, true, and false as boolean values. If you need the literal string "yes", wrap it in quotes in your YAML: value: "yes". The converter faithfully applies these YAML type rules to the JSON output.