Common Config workflows
Configuration formats disagree on types: YAML infers booleans and numbers from bare words, TOML has native dates and .env files contain only strings. Compare parsed values rather than text when two files must agree, and validate the converted file with the program that will read it.
Compare two environments
Compare parsed values across YAML, TOML, JSON or environment files. Differences in quoting or key order are ignored; changed, added and removed settings are listed.
- Config Diff — Compare configuration values and types across formats.
- .env to JSON — Convert .env files to JSON, YAML, Docker or Kubernetes.
- YAML Validator — Validate YAML and catch the Norway problem and other gotchas.
Fix a broken manifest
Validate the YAML to find the first syntax error with its line and column, then format it to make indentation problems visible. Multi-document files are checked document by document.
- YAML Validator — Validate YAML and catch the Norway problem and other gotchas.
- YAML Formatter — Re-indent and tidy YAML without losing comments.
- YAML to JSON — Convert YAML (with anchors and multiple docs) to JSON.
Convert configuration files
Convert between YAML, TOML and JSON. Check how dates, booleans and null values are represented in the destination before replacing a working configuration.
- YAML to JSON — Convert YAML (with anchors and multiple docs) to JSON.
- JSON to YAML — Convert JSON to clean, correctly quoted YAML.
- TOML to JSON — Convert TOML config files like Cargo.toml to JSON.
- JSON to TOML — Convert JSON to TOML tables and arrays of tables.
Quote values that must stay strings
YAML 1.1 parsers read some unquoted words such as yes, no and on as booleans, and values like 0644 as numbers. Quote country codes, versions and file modes when they must stay strings.
TOML dates have no JSON equivalent
JSON has no date type, so TOML date-times become strings. Keep the original file when a program depends on the native type.
Frequently asked questions
Is YAML a superset of JSON?
YAML 1.2 is designed to accept JSON documents, so most JSON parses as YAML. The reverse is not true: anchors, comments and multiple documents have no JSON form.
Does converting YAML to JSON keep comments?
No. JSON has no comments, so they are dropped. Keep the YAML file as the source of truth when its comments document the configuration.
Tools process your input on this device. Read the privacy policy, or save the tool library for offline use.