Turn a real .env into the committable example file, with secret values replaced by placeholders and a check that no detected secret survived into the output.
Waiting for a .env file
Paste the real one. Nothing is uploaded, and the secret values are what gets removed.
The example appears here
The same keys with every secret value removed, ready to commit.
Secret detection works from the variable's name, the value's shape and its entropy. A credential with an ordinary name and a short value can get past all three, so read the output before committing it — the check above tells you that no DETECTED secret survived, which is not the same as none at all. If a secret has already been committed, deleting it now does not remove it from the history; rotate it.
.env.example Generator runs entirely on your device — nothing is uploaded, logged or stored.
You’re on the Free plan. Compare plans
A .env.example is the file people actually read when they clone a repository, and it is usually out of date because keeping it in step with the real one is manual. This does the mechanical part: the same keys, with everything that looks like a credential replaced.
The default is to remove rather than to keep. Every value detected as a secret is replaced with a placeholder, and keeping the safe ones is a separate switch. That ordering is deliberate — the cost of wrongly keeping a value is a leaked secret in version control, and the cost of wrongly removing one is somebody typing `3000` again.
After generating, the output is checked against the input: no value detected as a secret may appear in it. That check is reported on the page rather than assumed, and it is a genuine check rather than a claim — if a value does survive, it says which one and why.
The documentation mode writes the same list as Markdown with each variable's shape described, which makes a better README section than the one most projects have. A variable nobody can explain is a variable nobody will remove when it stops being used.
Nothing is uploaded, logged or written to browser storage.
Read it first. The tool confirms that no DETECTED secret survived, which is not the same as none at all — a credential with an ordinary name and a short value can get past the detection. The check narrows the risk; it does not remove it.
Usually yes. A port, a host or a feature flag with its real default saves whoever clones the repository from guessing. The switch exists because in some projects even those reveal infrastructure you would rather not describe.
Rotate it. Removing it from the file now does nothing about the history, and rewriting the history does not undo the exposure — anyone who cloned the repository already has it.
Because the example file says what the variables are called and not what they are for. A short table in the README with each variable's purpose is the thing that stops someone setting a value to whatever makes the error go away.
No. It is parsed in your browser, never logged, and never written to browser storage.