YML

YAML ↔ JSON Converter

LOCAL · Browser-Only

Convert between YAML and JSON formats instantly

Direction

Indent

Sort keysMinify JSON

Input

Output

·Share recipe

Was this tool helpful?

What is YAML ↔ JSON Converter?

Free online YAML ↔ JSON converter to convert YAML to JSON or JSON to YAML instantly with this free online converter.

Paste data in either format and get a validated, properly formatted output in the other. The tool handles complex nested structures, arrays, multi-line strings, comments (in YAML), and special data types. Convert a Kubernetes manifest from YAML to JSON, turn a Docker Compose file into JSON for a script, or rewrite a GitHub Actions workflow from JSON back to YAML. It also helps when converting an OpenAPI or Swagger spec between formats, fixing YAML indentation errors, or pasting a config to validate its structure. Everything runs in your browser - your configuration data stays private. No signup required.

How to Use YAML ↔ JSON Converter

1Select the conversion direction: YAML to JSON or JSON to YAML
2Paste your YAML or JSON data into the input editor
3Click 'Convert' to generate the output in the target format
4Review the validated output and copy it for use in your project

Frequently Asked Questions

What is the difference between YAML and JSON?

YAML (YAML Ain't Markup Language) uses indentation and minimal syntax for readability, supports comments, and is commonly used for configuration files. JSON (JavaScript Object Notation) uses braces and brackets, is more verbose but universally supported by programming languages. Both represent the same data structures.

Are YAML comments preserved when converting to JSON?

No. JSON does not support comments, so YAML comments are lost during conversion to JSON. When converting JSON to YAML, you can add comments manually to the YAML output afterward.

Does it handle multi-line strings and special YAML types?

Yes. The converter handles YAML multi-line strings (using | and > block scalars), anchors and aliases, and special types like dates, booleans, and null values. These are converted to their closest JSON equivalents.

Can I use this for Kubernetes or Docker Compose files?

Absolutely. This tool is ideal for converting Kubernetes manifests, Docker Compose files, GitHub Actions workflows, and other DevOps configurations between YAML and JSON formats for debugging or integration purposes.

How do I convert an OpenAPI or Swagger spec between YAML and JSON?

Paste the full spec into the input. Both YAML and JSON are valid OpenAPI formats, so converting one to the other does not change the API definition. Use it when a tool only accepts one format, or to make a YAML spec easier to query as JSON.

Why does my YAML fail to convert?

The most common cause is inconsistent indentation, since YAML uses spaces (not tabs) to define structure. Tab characters, a missing space after a colon, or unquoted strings containing special characters can all break parsing. The validation message points to the line that needs fixing.

Share this tool

Related Tools

<{>

Json to xml

Free online JSON to XML converter - convert JSON data to XML format instantly

📊

Convert csv to json online

Free online CSV to JSON converter - convert CSV data to JSON format with delimiter options and preview

{ }

Json validator

JSON formatter and validator online - format, beautify, and validate JSON data instantly in your browser

🔄

Xml json converter

Free online XML to JSON converter - convert XML documents to JSON format

⇄

Toml parser

Convert between TOML and JSON online - bidirectional converter with full TOML v1.0 support

CSV

JSON to CSV Converter

Free online JSON to CSV converter - convert JSON arrays to CSV format for spreadsheets and databases

{ }

Json schema from json

Free online JSON schema generator - generate JSON Schema from sample JSON data automatically

XML

Xml pretty print

Free online XML formatter - format, validate, and beautify XML data with proper indentation

Keep reading: Docker Cheat Sheet and http status codes reference. Doing this in code instead? See the encoding endpoints.