.env File Maker
Build a .env and a matching .env.example from your variable names — entirely in your browser. This tool never asks for real secret values.
sk_test_xxxxxxxx, not a real key). This tool runs in your browser and never sends anything anywhere — but a placeholder is still the right habit, since .env.example is meant to be committed to git.
| Variable Name | Example Value (for .env.example) | Description (optional) |
|---|
.gitignore:
.env
A .env file holds configuration and secrets as simple NAME=value lines, loaded into your app's environment at startup. The convention that keeps teams out of trouble is splitting it in two: a real .env that never leaves your machine, and a .env.example with the same variable names and harmless placeholder values that does get committed, so anyone cloning the repo knows exactly what to configure.
Why This Tool Only Asks for Placeholders
There's no technical reason a form couldn't accept a real secret and hand back a file — but that's exactly the habit worth avoiding. Typing a real production key into any web form, even one that (like this one) never transmits it anywhere, normalizes a risky pattern. This tool is scoped to what you actually need before you have real secrets: the shape of your config.
What To Do With Real Secrets
| Situation | Recommended approach |
|---|---|
| Local development | Paste real values directly into your local .env — never through a web tool |
| Sharing secrets with teammates | A password manager (1Password, Bitwarden) or a secrets tool built for it (Doppler, Vault, SOPS) |
| CI/CD and production | Your platform's own secret store (GitHub Actions secrets, Vercel/Netlify env vars, AWS Secrets Manager, etc.) |
| A secret accidentally committed to git | Rotate it immediately, then scrub git history with git-filter-repo or BFG Repo-Cleaner |