Environment Variable Naming Linter
Paste variable names only to review common naming issues locally. This tool never needs the values assigned to those variables.
Naming review
A QUICK WALKTHROUGH
How to use this tool
- Enter one variable name per line, or separate names with commas or spaces.
- Choose whether names should use uppercase and, optionally, require a prefix.
- Review findings and download the plain-text report if useful.
Names only
Paste environment variable names, not their values. The checker does not parse .env assignments, read files, contact services, or change your input.
Explicit naming rules
Valid names must follow a shell-style identifier pattern: start with a letter or underscore, followed by letters, digits, or underscores. Optional checks flag lowercase letters and names missing the prefix you specify.
Local report
Findings and the downloadable text report are generated in your browser. Nothing is uploaded or saved by this tool.
GOOD TO KNOW
Common questions
Should I paste the contents of my .env file?
No. Enter variable names only, such as API_URL. Never paste API keys, passwords, tokens, or other values.
Does the prefix have to be set?
No. Prefix checking is optional; leave it empty when your project does not require a shared prefix.
Does the linter rename variables?
No. It reports issues without changing names or source files.