NOPPAW

Constant Case Converter

The Constant Case Converter — also called screaming snake case — produces UPPERCASE words joined by underscores: MAX_RETRY_COUNT, DATABASE_URL, FEATURE_FLAG_ON. It is the universal style for environment variables and genuinely constant values across almost every language. Paste a description in any style and get a valid constant name back instantly.

0 characters · 0 words · 0 lines

How to use Constant Case Converter

  1. Type or paste a name or description in any style.
  2. The CONSTANT_CASE version appears in the result box immediately.
  3. Copy it into your .env file, config or source code.

Supported behavior

  • Words are detected across spaces, hyphens, dots and camelCase humps.
  • Accents are stripped, so results are safe in .env files and shells.
  • Pairs naturally with the Snake Case Converter for the lowercase twin of the same name.

Best for

  • Environment variables in .env files.
  • Language-level constants and enum-like flags.
  • CI/CD secret and variable names.

Limits

  • Most shells require names to start with a letter or underscore — if your phrase starts with a number, prepend a word like VALUE_ or move the number later.
  • Acronyms are kept whole: 'api url' becomes 'API_URL', as expected for constants.

Privacy notes

  • Everything runs on your device: the text you type never leaves your browser.
  • Names are converted locally; nothing is sent to a server.

Related tools

Case Converter Convert Case See your text in every case style at once and copy the one you need. Case Converter Camel Case Converter Turn phrases into camelCase identifiers for code. Case Converter Snake Case Converter Turn phrases into snake_case for Python and databases. Case Converter Kebab Case Converter Turn phrases into kebab-case for URLs and CSS classes.

Constant Case Converter FAQ

What is the difference between constant case and snake case?

Only the shouting: constant case is UPPER_SNAKE, snake case is lower_snake. Convention reserves the uppercase form for values that never change at runtime.

Can I use the output directly in a .env file?

Yes — the output uses only A–Z, 0–9 and underscores, which every dotenv parser and shell accepts. Just add '=value' after it.

Does it work from camelCase?

Yes. 'maxRetryCount' becomes 'MAX_RETRY_COUNT' because camel humps are word boundaries.