A LITTLE CLARITY FOR YOUR DATA

JSON to YAML. Room to breathe.

Convert JSON to readable YAML 1.2. Keep nested objects, arrays, and data types clear.

Your workspace

JSON

Convert JSON to

Input

Your JSON goes here

18 lines·376 BUTF-8

Output

JSON

{
  "project": "jsonformatkit",
  "description": "A little clarity for your data",
  "version": "1.0.0",
  "isAwesome": true,
  "tools": [
    "Format & validate",
    "Convert & explore",
    "Share something beautiful"
  ],
  "settings": {
    "indentation": 2,
    "sortKeys": false,
    "privacy": "Your data stays yours"
  },
  "madeWith": "care",
  "nextBigIdea": null
}

Formatted JSON376 B

Ctrl↵

Looking good. Your JSON is valid.

Object with 11 keys. All brackets, quotes, and commas are in their happy place.

VALID JSON

Exports YAML 1.2. Tab indentation uses 2 spaces because YAML requires spaces.

All done? Take it with you.

Copy your result or download it in a click.

GO A LITTLE FURTHER

More than a pretty print.

A QUICK FIELD GUIDE

Create YAML 1.2 from a JSON document

YAML uses indentation and compact markers to make structured data readable. Converting JSON to YAML can help when preparing configuration for tools that prefer YAML while keeping familiar objects, arrays, strings, numbers, booleans, and null values.

jsonformatkit produces YAML 1.2. The serializer quotes strings when needed to distinguish them from other types or to handle special characters. Nested objects and arrays remain structured data rather than being flattened into table cells.

Choose 2 or 4 spaces for indentation. If Tabs is selected, YAML output uses 2 spaces because indentation tabs are not allowed. The converter starts from a parsed JSON value, so JavaScript numeric precision and duplicate-key handling apply before serialization. It does not add comments or invent configuration settings.

How to use JSON to YAML

Paste valid JSON or upload a JSON file.
Select 2-space or 4-space indentation and choose Convert to YAML.
Check the generated YAML and download the .yaml file.

Up to 2 MB of JSON and 100 nesting levels. URL imports require public HTTPS sources with CORS enabled.

A small example

INPUT

{"name":"Ada","active":true,"roles":["editor","admin"]}

RESULT

name: Ada
active: true
roles:
  - editor
  - admin

Frequently asked questions

Which YAML version does the converter produce?

It produces YAML 1.2. Check the YAML version expected by your receiving application, especially for strings or values interpreted differently by older YAML 1.1 parsers.

Can I use tabs to indent YAML?

YAML indentation requires spaces. When Tabs is selected in the shared toolbar, YAML conversion uses 2 spaces instead. Choose 4 spaces if you prefer wider indentation.

Will the converter keep my JSON comments?

Standard JSON cannot contain comments, so input with comments fails validation. YAML comments cannot be inferred from JSON and are not added to the generated output.

Built around open standards: JSON (RFC 8259), JSON Schema, and YAML 1.2.