List your variables
One per line as NAME:purpose:scope — the tool infers a likely format and safe example for each.
ENV VAR MANIFEST
List required environment variables with their purpose, format, scope, and safe example values from a simple schema.
Planning guidance only. Validate important decisions with customer evidence and your delivery team.
YOUR INPUTS
Complete every field. The result updates only when you choose Calculate.
One per line as NAME:purpose:scope — the tool infers a likely format and safe example for each.
Anything that looks like a secret but is scoped to 'client' is flagged immediately.
Use the generated manifest as your project's example env file, with placeholder values only.
Continue learning: Managing secrets and config safely
Any environment variable bundled into client-side code is visible to anyone who opens their browser's dev tools — real secrets (API keys, tokens) must stay server-only.
A simple heuristic based on the variable name — URL/URI, PORT, KEY/SECRET/TOKEN, EMAIL, and boolean-style prefixes each map to a likely format and safe example.
Yes, with placeholder values only — that's exactly what a .env.example file is for. Never commit the real .env file with actual secrets.
Treat it as a starting draft — correct the format/example manually for any variable the heuristic misclassifies.
| Feature | MVPHub | Doppler | Notion |
|---|---|---|---|
| Instant manifest from a simple list | Included | Not included | Not included |
| Client-exposure security check | Included | Not included | Not included |
| No account required | Included | Not included | Included |
| Actual secret storage and injection | Not included | Included | Not included |
Doppler manages and injects real secrets into your running environment. This tool documents what variables exist and flags an obvious security mistake before you ever touch a secrets manager.
Add this tool to your site with the canonical iframe below. It remains hosted and maintained by MVPHub.