Compare Config Files Across Environments
Compare application.yml, .properties and .env files across DEV, QA and PROD. See missing and different keys with secrets masked. Runs locally.
Config Drift Compare tool
Runs entirely in your browser. Nothing you paste is uploaded or stored.
Accepts application.yml, .properties and .env text. Values for keys that look like passwords, tokens or keys are hidden by default.
Found a problem or have an idea for this tool? Send feedback.
About this tool
Most 'works in QA, fails in PROD' problems are a config key that differs or is missing. Paste your application.yml, .properties or .env content for each environment and see which keys are different or missing, with the differing values side by side.
Keys that look like passwords, tokens or secrets are hidden by default, so the result is safe to share. Comparing two environments is free; a third is part of Pro.
How to use it
- Paste the config for each environment.
- Review keys marked Different or Missing.
- Copy the report into your ticket or pull request.
Limitations
- Secret detection is by key name and is a convenience, not a guarantee.
- Only a practical subset of YAML is supported.
Example
server:
port: 8080
spring:
datasource:
url: jdbc:postgresql://dev-db/orders
password: dev-secret
feature:
newCheckout: true
---
server:
port: 8443
spring:
datasource:
url: jdbc:postgresql://prod-db/orders
password: prod-secret
Missing feature.newCheckout true (missing)
Different server.port 8080 8443
Different spring.datasource.password •••••• ••••••
Different spring.datasource.url jdbc:postgresql://dev-db/orders jdbc:postgresql://prod-db/ordersCommon use cases
Release checks
Confirm PROD has every key a new release expects.
Environment debugging
Find the one property that explains different behaviour.
Config reviews
Share a drift report without exposing secrets.