.env · debug🔥 popular

Missing ENV Detector

Paste your .env and a list of required keys. Instantly see which variables are missing, empty, or extra.

Be the first to rate
2 issues across 4 required keys
missing2
JWT_SECRET
STRIPE_SECRET_KEY
empty0
— none —
ok2
DATABASE_URL
NODE_ENV
extra (unused)2
PORT
OLD_UNUSED_KEY

What it does

  • Flags every required key that's missing or empty
  • Shows extra (unused) keys too — useful for cleanup
  • Accepts a plain list, a .env.example, or a schema
  • Generates a pastable checklist for CI
  • 100% client-side

Privacy

Runs 100% in your browser. Your .env never touches our servers.

client-side only

Example

Paste your .env + required keys → see what's missing
# Your .env:
DATABASE_URL=postgres://...
PORT=3000

# Required keys (one per line):
DATABASE_URL
JWT_SECRET
STRIPE_SECRET_KEY
✗ missing: JWT_SECRET
✗ missing: STRIPE_SECRET_KEY
⚠ extra:   PORT
✓ ok:      DATABASE_URL

Missing ENV Detector — find env variables before they break prod

A missing .env variable is the single most common cause of a broken deploy. This detector compares your .env file against a list of required keys — paste either as a plain list or a .env.example — and flags what's missing, what's empty, and what's unused.

What it checks

  • Missing: required key doesn't exist in your .env
  • Empty: key exists but has no value
  • Extra: key exists in your .env but isn't on the required list (often dead config)

Why this matters

Production crashes on missing env vars get blamed on "the deploy." In reality, the root cause is usually that a key was added locally, never documented in .env.example, and never set on the host. Running your .env through this detector before merging a PR catches it at code review instead of during an incident.

Related tools

Learn more

coming soon

Get notified when env syncing launches

We're building a tiny tool to keep .env files in sync across teammates and environments. Leave your email — no spam, just a single launch ping.