.env File Compare
Compare two or more environments to find missing keys and value differences. Values stay hidden until you reveal them.
2 environments · 0 unique variables
Practical guide
How to compare .env files
Use the ENV comparison tool to find configuration drift before a deployment. It compares keys and values across two or more dotenv files while keeping values hidden by default.
- 1Paste or load each .env file into a separate environment card.
- 2Review variables that are missing, different, or identical across every file.
- 3Copy the missing assignments for a specific environment, then review their values before use.
What this tool handles
- Two or more development, staging, production, or .env.example files
- Missing variables and variables with different values
- Comments, blank lines, quoted values, and shell-style export prefixes
- Duplicate and malformed assignments reported by the shared ENV parser
Example
.env.example API_URL= LOG_LEVEL= .env.production API_URL=https://api.example.com Result: LOG_LEVEL is missing from production
Frequently asked questions
Are ENV values uploaded for comparison?
No. Files are read with the browser File API and compared in this tab. EnvSift does not send their contents, keys, values, or filenames to a server or analytics service.
Can I compare more than two .env files?
Yes. Add as many environment cards as needed. The result shows missing keys per file and value differences across every complete row.
Does EnvSift expose secret values in the result?
Values remain masked until you choose Reveal values. Missing-key exports should still be reviewed before they are copied into another environment.