Config Compare

Compare .env, .properties, JSON, and YAML configs by key, with secrets masked.

Your data stays in your browser

Environments

2 of 6

NameShared with other tools

Waiting for data

Interpret as

Name

Waiting for data

Interpret as

Optional: keys every environment must define.

No result

Paste a config in each environment above, then press Compare configs.

Names DEV and PROD

DB_HOST=db.dev
DB_PORT=5432
DEBUG=true
API_KEY=abc

# production
API_KEY=xyz
DB_PORT=5432
DB_HOST=db.prod

Changed: DB_HOST (db.dev → db.prod)
Only in DEV: DEBUG
Only in PROD: none
Secrets changed: API_KEY
Same: DB_PORT

Keys are matched by name, so order and comments never count. Nested keys become paths such as server.port, and list items can match by a key such as name.
.env and .properties values are text. JSON and YAML also compare types, so "5" and 5 differ. YAML follows version 1.2, so yes and on stay text.
Missing, null, and empty values stay apart. In .env, KEY= and KEY="" are both empty. A key defined twice is flagged, and its last definition is used.
Secret-looking keys and values, such as access tokens, are masked and still compared. Reveal one on screen, or mark more paths as secret. Copies and downloads stay masked.
Compare up to six environments, with one as the baseline. Ignore noise with patterns such as **.timestamp, and check required keys from a list or an .env.example.