.env · workflow

.env.example Generator

Turn any .env file into a safe .env.example template. Strips values while keeping keys and comments intact.

Be the first to rate

keep default values for non-secret keys (NODE_ENV, PORT, etc)sort alphabetically

.env input

.env.example output

DATABASE_URL=
NODE_ENV=development
PORT=3000
JWT_SECRET=
STRIPE_SECRET_KEY=

What it does

▸Strips all values, keeps keys and comments
▸Optional: preserve default values for non-secrets
▸Sort or group keys
▸Produces a safe .env.example ready to commit
▸Client-side only

Privacy

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

client-side only

Usage examples

Case 1 · Full strip

DATABASE_URL=postgres://user:pass@host/db
JWT_SECRET=super-secret-xyz
STRIPE_SECRET_KEY=sk_test_xxx

DATABASE_URL=
JWT_SECRET=
STRIPE_SECRET_KEY=

Case 2 · Keep non-secret defaults

NODE_ENV=development
PORT=3000
JWT_SECRET=super-secret-xyz

NODE_ENV=development
PORT=3000
JWT_SECRET=

Case 3 · Preserve comments

# App config
NODE_ENV=development

# Auth
JWT_SECRET=xyz

# App config
NODE_ENV=development

# Auth
JWT_SECRET=

When to use this tool

→Repo never had a .env.example — generate one from your live .env
→Onboarding — commit the example so new hires know what to fill in
→After adding a new env var, regenerate the example to keep it in sync
→Audit — see your .env structure at a glance without values

Common mistakes

⚠Forgetting to actually commit the .env.example after generating
⚠Leaving one key's real value in by accident — always diff before committing
⚠Stripping values that should be committed (NODE_ENV=development is a sensible default)
⚠Using it as a replacement for a secrets manager — .env.example only documents structure

.env.example Generator

A .env.example file ships the structure of your env without exposing secrets. Paste your live .env and this tool produces a committable example file — values stripped, keys and comments preserved.

Frequently asked questions

Should .env.example be committed to git?

Yes — that is the entire point. .env.example documents which variables the app requires without exposing their values. Commit it and keep it in sync with your actual .env as you add or remove keys.

What exactly gets stripped — just the values?

Yes. Keys and comments are preserved; only the value part (everything after =) is removed. If you enable 'keep safe defaults', non-secret values like NODE_ENV=development and PORT=3000 are preserved.

Can I keep placeholder values for some keys?

The tool strips all values automatically. After generating, edit the output to add descriptive placeholders (e.g. DATABASE_URL=postgres://user:pass@host/dbname) for keys that need context for new developers.