Generate .env.example
The Generate .env.example tool creates a sanitized copy of your .env file with all sensitive values replaced by descriptive placeholders — making it safe to commit to git.
Running the Generator
Click 📄 Generate .env.example in the Pro Tools panel, or run ENV Manager Pro: Generate .env.example.
The extension reads your active .env file and writes a .env.example file in the same directory.
How Placeholders Are Chosen
Each key is classified by name pattern:
| Key pattern | Placeholder |
|---|---|
Contains TOKEN, SECRET, KEY, PASS, PWD, CREDENTIAL | your_secret_here |
Contains URL, URI, HOST, DSN | https://your-host-here |
| Everything else | your_value_here |
Input .env:
DATABASE_URL=postgres://user:pass@localhost/mydb
JWT_SECRET=abc123supersecret
APP_NAME=MyApp
PORT=3000
Output .env.example:
DATABASE_URL=https://your-host-here
JWT_SECRET=your_secret_here
APP_NAME=your_value_here
PORT=your_value_here
Comments and blank lines are preserved exactly, so the structure of the example file matches the original.
Why .env.example Matters
The .env.example file is committed to git and serves as documentation for what variables a new developer needs to configure. Without it, onboarding developers have to guess which variables exist and what format they should take.
By generating it automatically from your actual .env file, the example always stays in sync — no manual maintenance required.
Run Check Missing Keys (in the Variables panel overflow menu) to compare your .env against .env.example and find keys you forgot to add to either file.