.env Diff and Missing Key Checker

Compare two dotenv snapshots and report missing, extra, or changed environment keys.

Also useful for: dotenv diff env diff checker missing env key checker dotenv compare tool .env Diff and Missing Key Checker

.env Diff and Missing Key Checker

Runs in your browser. Inputs are not uploaded.
Input
Results
Summary: 3 left keys compared with 3 right keys. 1 error, 1 note.

Stats
- Left Keys: 3
- Right Keys: 3

Issues
- Critical: API_KEY is missing from the second env file.
- Note: REDIS_URL exists only in the second env file.

Output
[ERROR] general: API_KEY is missing from the second env file.
[INFO] general: REDIS_URL exists only in the second env file.

.env Diff and Missing Key Checker Example Run

Compare a real env file against an example file.

Sample inputs
Env files
Source .env:
API_URL=https://api.example.com
DATABASE_URL=postgres://example
API_KEY=secret
Target .env:
API_URL=
DATABASE_URL=
REDIS_URL=

Generated result
Summary: 3 left keys compared with 3 right keys. 1 error, 1 note.

Stats
- Left Keys: 3
- Right Keys: 3

Issues
- Critical: API_KEY is missing from the second env file.
- Note: REDIS_URL exists only in the second env file.

Output
[ERROR] general: API_KEY is missing from the second env file.
[INFO] general: REDIS_URL exists only in the second env file.

What the .env Diff and Missing Key Checker Checks

  • Two dotenv snapshots

    Left and right env files are compared after parsing KEY=value lines.

  • Missing keys

    Keys present in the first file but absent from the second are treated as blocking gaps.

  • Extra keys

    Keys that exist only in the second file are reported as informational differences.

  • Changed non-empty values

    When both files have non-empty but different values, the key is flagged for review.

  • Key-focused comparison

    The tool compares env keys and simple values, not deployment secrets or runtime availability.

.env Diff and Missing Key Checker Questions

  • Q: Does the .env diff and missing key checker upload my env files? A: No. Inputs are processed in your browser, and pasted content is not sent to analytics or a server.
  • Q: What should I paste into the .env diff and missing key checker? A: Paste the source env file, a separator line with three hyphens, then the target env file or .env.example.
  • Q: What can I copy or download? A: You can copy the missing, extra, and changed key report.
  • Q: What does the .env diff and missing key checker not verify? A: It does not connect to hosting providers, decrypt secret stores, or decide which value should win.

Related Tools

Updates

  • v1.0.0 New 2026-05-17: Initial dotenv comparison for missing, extra, and changed keys added.

Use .env Diff and Missing Key Checker with an LLM

Copy the prompt or pass the llms.txt contract link to your assistant.

Prompt
Use the CleanUtils .env Diff and Missing Key Checker tool for this request.
Tool contract: https://cleanutils.com/developer-tools/env-diff-missing-key-checker/llms.txt

Read the llms.txt contract, ask me for any missing required input, then follow the contract exactly. If the contract includes JavaScript, run `runCleanUtilsTool(userInput)` in a sandboxed JavaScript runtime and return the result with any warnings or errors.