Env File Sanitizer (.env.example)
Turn a .env file into a safe .env.example by stripping the secret values.
Sharing config without sharing secrets
A .env file holds a project's configuration, including secrets — API keys, passwords, tokens — that must never be committed or shared. But other developers need to know which variables the project expects. The convention is an .env.example that lists the keys with the values blanked out. This takes your real .env and produces that safe example, stripping the sensitive values while keeping the variable names.
Paste your .env and get back a shareable example with the secrets removed.
Why this matters so much
Committing a real .env with live secrets is one of the most common and damaging security mistakes — keys leaked in a public repo get found and abused within hours. An .env.example solves it: the real file stays out of version control, and the example documents what is needed without exposing a single secret. Generating the example from the real file, rather than maintaining it by hand, means it stays in sync and you never accidentally leave a real value in it.
Frequently asked questions
What does it strip?
The secret values, keeping the variable names, so the result documents what config is needed without exposing any secrets.
Why not just commit the real .env?
Because it contains live secrets. Committing one, especially to a public repo, is a serious security incident.
Is my file uploaded?
No. The sanitising happens in your browser, so your real secrets never leave your machine.