# ENV Diff

Compare two .env files and see which variables were added, removed or changed. Paste for example .env.example and your .env, or staging and production settings. Values are hidden by default, so you can share the result without exposing secrets, and can be shown when you need them.

## Frequently asked questions

### What does the result show?

Counts of added, removed, changed and unchanged variables, and a table of every variable that differs with its status. Keys are sorted alphabetically.

### Why are values hidden?

.env files often hold passwords and API keys. By default only key names and their status are shown. Turn on show values to see the old and new values, shortened to 80 characters.

### How do I find variables missing from my .env?

Paste .env.example as the first file and your .env as the second. Variables listed as removed are in the example but missing from your file.

### How are the files read?

With the same dotenv rules as the other ENV tools: comments and export prefixes are ignored, quotes are removed and escapes in double quotes are decoded, so KEY="a" and KEY=a count as equal.

### What if a key appears twice in one file?

The last value counts, as when dotenv loads the file. Run the ENV Checker to find such duplicates.

### Why is one of my files rejected?

A line without an equals sign, an invalid key or an unclosed quote stops the comparison, and the message names the line so you can fix it.

Your ad here?

[Email us](mailto:hi@dennn.is?subject=Advertising%20on%20OneClick%20Pro)

[Ad 433 tools for your AI agents through one MCP server.](https://multitaskai.com/?ref=oneclickpro)
