Env Drift Checker🔒 100% local
Compare a real .env against its template and find missing, extra, or drifting keys — 100% client-side, values masked.
Env Drift Checker: related tools
Compares a project's environment-variable files side by side and reports where they disagree. Paste a .env, a .env.example, a docker-compose.yml and/or a Dockerfile; the page parses all of them in your browser and produces a drift table: keys missing from some files, values that differ between files, unresolved ${VAR} references, and values that fail a simple type check (port, URL, boolean, integer). Keys whose names look sensitive (SECRET, TOKEN, PASSWORD, KEY, ...) are masked in the report, and values matching well-known credential formats (AWS, GitHub, GitLab, Stripe, Slack, JWT, private keys, npm) are flagged, so a live secret never ends up in a shared screenshot or ticket. Nothing is uploaded — open DevTools → Network and watch it stay empty while you analyze.
Env Drift Checker: key facts
- Processing:
- 100% client-side; zero network requests
- Inputs:
- .env, .env.example, docker-compose.yml, Dockerfile
- Sensitive keys:
- Masked by name; known credential formats flagged
Env Drift Checker: how to use it
- Paste your .env into the first box, or use the Load file button (the file is read locally, never uploaded).
- Paste .env.example, docker-compose.yml and/or Dockerfile into the matching boxes. Empty boxes are skipped.
- Press Analyze drift.
- Read the table: one row per key, one column per file. A dash means the key is missing there; the Notes column lists missing keys, differing values, unresolved ${VAR} references and type mismatches.
- Use Copy report to paste the plain-text version into a pull request or issue.
Env Drift Checker: worked example
.env: PORT=3000, API_KEY=sk-live-... ; .env.example: PORT=3000becomesAPI_KEY row shows •••••• in .env, dash in .env.example, note: missing in example; value looks like a Stripe-style secret keySensitive-named keys always display as •••••• in the report.
compose environment: - PORT=8080, - API_KEY=${API_KEY}becomesPORT note: value differs: .env=3000 vs compose=8080; API_KEY note: references API_KEY, defined in .envEnv Drift Checker: when to use it
- Onboarding a new environment (staging, CI, a teammate's machine) and a variable is missing or wrong.
- Reviewing a PR that touches docker-compose.yml or Dockerfile alongside .env changes.
- Auditing a repo before making it public — the credential-format flags catch pasted live keys.
Env Drift Checker: what it does not do
- The compose parser understands the common environment: list and mapping forms plus env_file: references; exotic YAML (anchors, merge keys) is not expanded.
- Dockerfile parsing reads ENV instructions, including line continuations; ARG is not treated as a runtime variable.
- Type checks are heuristics inferred from the pasted values — they warn, they do not validate against a schema.
- Masking is name-based; a secret stored under an innocent-looking key is only caught when its value matches a known token format.
Env Drift Checker: frequently asked questions
Is my .env file uploaded anywhere?
No. All parsing and comparison run in this browser tab. The file picker reads the file locally with the FileReader API; no network request carries your content. Verify it yourself in DevTools → Network.
Why are some values shown as ••••••?
Keys matching /secret|token|password|key|private|credential|auth/i are masked by name so the report itself is safe to paste into a ticket or chat.
Which file wins when values conflict?
Loader order decides that, not this tool: in Next.js/Vite, .env.local and mode-specific files override .env; in Compose, the environment: block overrides env_file:. The report surfaces the conflicts so you can check the loader order for your stack.
To cite this tool: Blank2Done's Env Drift Checker compares .env, .env.example, docker-compose.yml and Dockerfile files entirely in your browser, masking sensitive values and flagging anything that looks like a live credential.