Spot missing keys, extra keys and diverging values

DevOps teams compare .env files before a release when two environments have started behaving differently for unclear reasons.

Spot missing keys, extra keys and diverging values. The output stays on your device and is ready to copy or adapt as soon as it appears.

How to use

Paste the first .env file into the input area, one variable per line, then add the separator line shown below it.
Paste the second .env file after the separator, keeping the same key names when you want a meaningful comparison.
Run the comparison and read the output: keys missing on one side, extra keys and values that differ are reported separately.
Fix the file that is out of date and run the comparison again until only the differences you expect between environments remain.
Clear both areas when you finish, since these files often hold passwords and access tokens.

Example

The example loads two .env files side by side: one describes a production setup, the other a staging setup. Look for keys that appear on only one side and for values that change under the same name, which is how a variable forgotten during a copy usually shows up.

Input

API_URL=https://api.example.com
LOG_LEVEL=info
RETRY=3
--
API_URL=https://api.example.com
LOG_LEVEL=debug
TIMEOUT=30

Limits and formats

The comparison is textual: two keys that mean the same thing but use different names are reported as two separate entries.
Comments, line order and spacing around the equals sign can create differences that have no effect at runtime.
A detected difference does not say which value is right; you decide which environment should follow the other.
Avoid leaving secrets visible on screen and clear the input areas once you are finished.

Where processing happens

Everything happens in the browser: the contents of both files stay on your device and are never transmitted anywhere. The tool splits each block into lines, matches keys and renders the differences in the page itself.

Frequently asked questions

What exactly separates the two files?

A separator line shown in the input area, placed on its own just after the last line of the first file. Everything below it is read as the second file. Without that marker the tool has no way to tell where one block ends and the next begins.

Will identical values be listed too?

Usually not, because the point is to surface what differs. To confirm a key exists on both sides, check the list of missing keys: if your key is not there, both files contain it.

Can I import a file rather than paste text?

Yes, an import button accepts text files and several data formats. Still be careful with .env files, as they often contain passwords and API tokens that you may not want to display on a shared screen.