.env Diff Checker — Find Missing Variables Fast
The .env.example in the repo says one thing; your local .env says another; production says a third. A purpose-built diff checker answers the only questions that matter — what is missing, what is extra, what changed — without the noise of a line-by-line text diff.
- ✓New teammate onboarding: hand them the template, let them check their own file in ten seconds.
- ✓Code review: a variable was renamed in the example file, and three environments quietly broke.
- ✓Duplicate keys, export prefixes and quoted values are parsed the way your framework actually reads them.
- ✓A one-page report (Markdown or JSON) drops straight into your PR or incident notes.
FAQ
Which file goes on which side?
File A is your reference (usually .env.example or the known-good file), File B is the one you are checking. 'Missing in B' means A has it and B does not.
Does it handle export FOO=bar and quoted values?
Yes — export prefixes are stripped, single- and double-quoted values are unquoted, comments and blank lines are ignored, and values may contain '=' signs.
Can I export the result?
Yes, as a Markdown or JSON report. Exporting the full report is part of the one-time Pro unlock; the on-screen diff is free.