.env Configuration Checker

What it does

• Detects variables missing in production but declared in the example
• Flags empty values and unchanged default placeholders
• Surfaces undocumented variables set only in production
• Runs entirely on paste — no files uploaded

How it works

1. 1Paste your .env.example into the first box.
2. 2Paste your production .env into the second.
3. 3Press Compare and read the grouped findings.

Use cases

• Pre-deploy checklist: confirm no required variable is missing
• Auditing secrets that still hold example placeholders
• Documenting variables that exist only in production

Frequently asked questions

Does my .env leave my browser?

Only the pasted text is sent to our server to compare — no files are uploaded. Avoid pasting real secret values; use placeholders for the check.

What does “unchanged default” mean?

A production value that still equals the example placeholder — a sign a real secret was never rotated in.

Which lines are ignored during comparison?

Blank lines, comments and lines that are not valid KEY=VALUE assignments are ignored. The parser also accepts assignments prefixed with export.