dotenv environment variable comparison
Compare two .env, categorize additions, deletions, modifications, and duplicate keys; ordinary public values remain in plain text, and only the secret-like fields can optionally be protected.
How to compare dotenv environment variables
dotenv environment variable comparison processes input only in the current browser; nothing is uploaded, networked, or written to persistent storage.
Enter two environment files
Use the default JSON, TOTP feature flags, and other ordinary variable examples, or paste two copies of .env.
Run comparison
View differences in additions, deletions, modifications, duplicate keys, and comments.
Choose a protection method
Selectively protect only fields that are truly secret-like; ordinary demo values remain visible.
Limitations and Notes
- secret-like is only a heuristic classification and does not constitute real secret detection or a security audit.
- By default, variables are not expanded, storage is not written, data is not uploaded, and user input is not modified.
- Duplicate keys and quotation differences should be verified again with the target dotenv parser.
FAQ
Why are ordinary values not masked?
Public examples and ordinary configuration values should be readable; the tool provides field-level protection only for potentially sensitive fields.
Will ${VAR} be expanded?
No. By default, it only compares text and values; it does not perform variable expansion.
Can it replace secret scanning?
No; it only provides assistance with local configuration differences.