Input

Output

JSON and YAML conversion review

Move structured data such as API responses, config files, and manifests between JSON, YAML, and simple CSV output.

Move between config formats

Convert JSON samples into YAML config, or convert YAML into JSON for easier handling in code.

Inspect structure

Check whether arrays, objects, strings, numbers, booleans, and null values survive conversion as intended.

Flatten simple arrays

Turn simple array data into CSV when you need a quick spreadsheet or review table.

Errors you will hit

Unquoted "no" turns into false

YAML 1.1 reads no, yes, on, and off as booleans. The country code NO becoming false is known as the Norway problem. Quote the value to keep it a string.

Indentation breaks

YAML does not accept tabs for indentation. Use spaces and keep the width consistent across the file.

Leading zeros disappear

Values like 08 or a phone number can be parsed as octal or numeric. Quote phone numbers, postal codes, and version strings.

Things to check

YAML infers types

YAML can interpret values that look like yes, no, or dates. Quote sensitive string values when exact text matters.

Comments may not survive

JSON has no comments, and YAML comments or original formatting may be lost during conversion. Keep the original config separately.

Unquoted YAML values are risky

Bare yes, no, on, off and null parse as booleans or null rather than strings. The country code NO becoming false is the classic example. Quote anything that must stay a string.

Tabs are not allowed for indentation

The YAML spec permits only spaces for indentation. An editor inserting tabs causes a parse error that looks fine on screen. Enable tab-to-space conversion for YAML files.

YAML anchors do not survive JSON

YAML anchors and aliases reuse a block, and JSON has no equivalent. Converting expands every reference, inflating the file, and the original structure cannot be restored on the way back. Avoid anchors if you need a round trip.

Real input and output

JSON to YAML

Input

{"name":"api","port":8080,"debug":false}

Output

name: api
port: 8080
debug: false

Nested structures

Input

{"db":{"host":"localhost","ports":[5432,5433]}}

Output

db:
  host: localhost
  ports:
    - 5432
    - 5433

Tools that pair well

JSON ↔ YAML Converter

JSON and YAML conversion review

Move between config formats

Inspect structure

Flatten simple arrays

Errors you will hit

Unquoted "no" turns into false

Indentation breaks

Leading zeros disappear

Things to check

YAML infers types

Comments may not survive

Unquoted YAML values are risky

Tabs are not allowed for indentation

YAML anchors do not survive JSON

How to use it

Real input and output

JSON to YAML

Nested structures

Tools that pair well