Dev
Environment Variable Name Generator
Used by developers, writers, and creators worldwide.
An environment variable name generator produces conventional SCREAMING_SNAKE_CASE names for the configuration values an application reads from its environment. Environment variables hold things like database hosts, API keys, and ports, and the near-universal convention is uppercase words joined by underscores, often grouped by a prefix such as DB_ or API_. This generator hands you well-formed names following that convention, useful as placeholders in a .env example, scaffolding for a new config, or simply inspiration for naming your own variables consistently. Consistent, predictable names make a configuration far easier to read and maintain, and a generator removes the small friction of inventing them one at a time.
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many variable names you want.
- Click Generate to produce SCREAMING_SNAKE_CASE names.
- Use them in a .env example, config, or documentation.
- Adapt the prefixes and names to your actual settings.
Use Cases
- •Placeholder names in a .env example file
- •Scaffolding configuration for a new project
- •Naming environment variables consistently
- •Documentation and tutorial config examples
- •Inspiration for grouping config by prefix
Tips
- →Group related variables under a common prefix for readability.
- →Keep a committed .env.example with names but no real values.
- →Never commit real secrets — store them in a secrets manager.
- →Be consistent: pick a convention and apply it across the whole config.
FAQ
why are environment variables uppercase
The strong convention is SCREAMING_SNAKE_CASE — uppercase words joined by underscores — which distinguishes environment variables from ordinary shell or program variables and is consistent across operating systems and tools. Following it makes a configuration instantly recognisable and predictable.
should i prefix related variables
Yes — grouping related variables under a common prefix like DB_ or STRIPE_ makes a configuration much easier to scan and reason about. A prefix signals which subsystem a value belongs to and helps avoid name clashes between unrelated settings.
where should i store environment variables
In a .env file for local development (kept out of version control) and in a secrets manager or your platform's environment configuration in production. Never commit real secrets to a repository; use placeholder names like these in any committed example file.