Environment Variable Diff Checker

Compare two .env files or environment variable blocks, find added, removed, changed, duplicate, empty, and secret-looking variables directly in your browser.

Environment A

Paste your first .env file, local variables, staging variables, or old deployment variables.

Environment B

Paste the second .env file, production variables, CI variables, or new deployment variables.

Compare Options

Output

Hide secret valuesHide values for keys that look like tokens, passwords, secrets, and API keys.Trim valuesIgnore extra spaces around values when comparing.Ignore commentsSkip comment lines that start with #.Case-sensitive keysTreat API_URL and api_url as different variables.

Diff Output

Environment variable diff output will appear here.

Environment variable comparison happens directly in your browser. The values you paste are not uploaded to a server.

Comparing Environment Variables Before Deployment

Environment variable differences are a common reason for broken deployments. A missing API URL, changed feature flag, empty secret, wrong database string, or duplicate key can make local, staging, and production behave differently.

This Environment Variable Diff Checker compares two .env files or variable blocks and shows what was added, removed, changed, or kept the same. It also points out duplicates, empty values, and secret-looking keys so you can review risky changes before shipping.

Checking Two .env Files

Paste the first environment block into Environment A.
Paste the second environment block into Environment B.
Choose whether comments, spaces, and key case should matter.
Review added, removed, changed, duplicate, and empty variables.
Copy the summary, JSON, or patch-style diff output.

Common Environment Variable Diff Use Cases

Comparing local and production .env files.
Checking staging variables before a deployment.
Comparing .env.example with a real .env file.
Finding missing variables in CI/CD settings.
Reviewing changed feature flags or API URLs.
Finding duplicate keys and empty secret values.

Example Environment Difference

Environment A:
NODE_ENV=development
API_URL=https://api-dev.example.com
LOG_LEVEL=debug

Environment B:
NODE_ENV=production
API_URL=https://api.example.com
LOG_LEVEL=info

Changed:
NODE_ENV
API_URL
LOG_LEVEL

Be Careful With Secrets

Environment files often contain database URLs, tokens, API keys, passwords, private endpoints, and service credentials. The tool hides secret-looking values by default in copied output.

Before sharing a diff in a ticket, chat, or screenshot, replace real values with safe examples. Keep production secrets out of public messages and documentation.

Frequently Asked Questions

What does an environment variable diff checker do?

It compares two .env files or variable blocks and shows which variables were added, removed, changed, or stayed the same.

Can this compare .env.example and .env?

Yes. Paste .env.example in one side and your .env file on the other side to check missing or changed variables.

Does this hide secrets?

Secret-looking values are hidden in copied output by default, but you should still avoid sharing real production secrets.

Are my environment variables uploaded anywhere?

No. Comparison happens directly in your browser, and your values are not uploaded to a server.