.env Configuration Diff
Full instructions and common questions
.env Configuration Diff
Compare two .env files locally and find added, removed, or changed variables. Likely secrets are masked by default; values are never interpolated or executed.
How to use
- Paste the old and new configuration.
- Review variable changes and parse notes. Reveal sensitive fields only when needed.
- Export the CSV diff. Check that secret values stay masked before sharing it.
Try an example
The old file has API_URL and API_KEY. The new file changes API_URL and adds DEBUG. The tool marks API_URL as changed and DEBUG as added; API_KEY is masked.
Limits and privacy
Supports common KEY=value and export KEY=value lines. Variable references are not expanded, commands are not executed, and complex shell syntax is not parsed. Text remains in page memory.
Common questions
Why could some lines not be parsed?
Check for KEY=value syntax. Comment lines may start with #; multi-line shell expressions are unsupported.
How are likely secrets detected?
Names containing common terms such as token, password, secret, or key are masked. Check custom sensitive fields yourself.