Move between config formats
Convert JSON samples into YAML config, or convert YAML into JSON for easier handling in code.
🔒 Browser-side processing
Convert JSON and YAML while moving structured data between formats.
Guide
Move structured data such as API responses, config files, and manifests between JSON, YAML, and simple CSV output.
Convert JSON samples into YAML config, or convert YAML into JSON for easier handling in code.
Check whether arrays, objects, strings, numbers, booleans, and null values survive conversion as intended.
Turn simple array data into CSV when you need a quick spreadsheet or review table.
Workflow
Examples
Input
{"name":"api","port":8080,"debug":false}
Output
name: api
port: 8080
debug: false
Input
{"db":{"host":"localhost","ports":[5432,5433]}}
Output
db:
host: localhost
ports:
- 5432
- 5433
Troubleshooting
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.
YAML does not accept tabs for indentation. Use spaces and keep the width consistent across the file.
Values like 08 or a phone number can be parsed as octal or numeric. Quote phone numbers, postal codes, and version strings.
Review
YAML can interpret values that look like yes, no, or dates. Quote sensitive string values when exact text matters.
JSON has no comments, and YAML comments or original formatting may be lost during conversion. Keep the original config separately.
Related