Paste .env.example and .env side by side. Missing, unused and matching keys update live as you type.
The required file goes left, your candidate .env goes right. A sample is preloaded.
Missing, extra and matched keys with live counts in a single table.
Every row has a copy button for a ready-to-paste KEY=value line.
Live comparison, 100% in your browser
Missing
3
Extra
0
Matched
4
Keys compared
7
| Status | Key | Value | |
|---|---|---|---|
| Missing | REDIS_URL | redis://localhost:6379 | |
| Missing | SECRET_KEY | ||
| Missing | SENTRY_DSN | ||
| Matched | PORT | 3000 | |
| Matched | HOST | 127.0.0.1 | |
| Matched | DATABASE_URL | postgres://dev:dev@localhost:5432/app | |
| Matched | API_KEY | local-dev-key |
7 keys compared · Last validated just now
Runs locally in your browser
Environment drift is a silent killer of deploys.
STRIPE_SECRET_KEY to .env.example.env never gets it, and the payment code shipsA missing-key diff catches this before CI does. It is the difference between a clean deploy and a hotfix at midnight.
.env.example as the contract for every key your app reads..env against it in CI with envy diff.Common questions about comparing .env files
A key that exists in your required file (.env.example) but not in the candidate (.env). At runtime, code reading it gets undefined, which is how environment drift breaks production.