How to Compare .env Files to Find Missing Variables
Use the .env Diff tool to compare environment variable files between environments and catch missing or mismatched configuration before deploying.
Tool Used
Environment Variable Diff
Prepare your two .env files
Identify the two .env files you want to compare. The most common comparison is your .env.example (committed to git, lists all required variables with placeholder values) versus your production environment variables. Export your production variables to a file or copy them from your deployment platform (Vercel, Railway, Render). Remove any sensitive values you do not want to paste into the browser, or use placeholder replacements.
Paste the files into the left and right panels
Open the .env Diff tool. Paste the first .env file into the left panel and the second into the right panel. Typical use: left panel = .env.example (the template), right panel = your production .env (the actual values). Each file should contain KEY=VALUE pairs, one per line, with optional comments starting with #.
Click Compare and review the diff
Click Compare. The tool highlights three categories of differences: keys present in the left file but missing in the right (shown in red — these are missing from production), keys present in the right but missing in the left (shown in blue — undocumented variables), and keys present in both but with different values (shown in yellow — value mismatches). Secret values are automatically masked.
Add missing variables to production
For each variable shown as missing from production (red), add it to your production environment. If it was missing entirely, the application may be crashing silently or falling back to an undefined value — check your application startup validation logs. Add the missing values through your deployment platform's environment variable settings.
Update .env.example for undocumented variables
For each variable found in production but missing from .env.example (blue), add it to your .env.example with a placeholder or description. This ensures other developers and future environments know the variable is required. Commit the updated .env.example to git. From this point forward, make .env.example review a standard part of your pull request checklist.
All done!
You are ready to use Environment Variable Diff like a pro.