This CONSTANT_CASE converter uppercases your text and joins the words with underscores — turning max retry count into MAX_RETRY_COUNT. It is the convention for constants and environment variables.
How to use the CONSTANT_CASE converter
- Paste a phrase or an existing identifier.
- The CONSTANT_CASE (SCREAMING_SNAKE_CASE) version appears instantly.
- Copy it into your config, enum or
.envfile.
When to use CONSTANT_CASE
Also called SCREAMING_SNAKE_CASE, this style flags values that never change: fixed configuration keys, enum members and environment variables such as DATABASE_URL or MAX_RETRY_COUNT. The all-caps form makes constants stand out from ordinary variables at a glance.
Environment variables and .env files
The place you meet CONSTANT_CASE most often is environment configuration. Shell variables such as PATH and HOME have been uppercase since the earliest Unix systems, and .env files inherited the habit — DATABASE_URL, API_KEY, NODE_ENV. Following the convention matters in practice: libraries look variables up by exact name, so a variable saved as database url in the wrong style simply will not be found where DATABASE_URL is expected. Paste each setting name here to get the canonical uppercase form.
Examples
| Input | CONSTANT_CASE |
|---|---|
| max retry count | MAX_RETRY_COUNT |
| databaseUrl | DATABASE_URL |
| api-base-path | API_BASE_PATH |