Utiltown

Case Converter

Convert any text to camelCase, snake_case, kebab-case, Pascal Case, Title Case, sentence case, UPPERCASE, or lowercase. A free online text case converter that runs entirely in your browser, perfect for naming variables, files, and constants consistently across a codebase.

All computations run locally in your browser, no data uploaded to server. 
  
  
 
How To Use
 
     
  1. Paste or type the text you want to convert.
    2.  
  2. Click the target case: UPPERCASE, lowercase, Title, camel, Pascal, snake, sentence, or kebab.
    3.  
  3. Copy the result with Copy output.
    4.  
 
 
 
Usage Example
 
Input:
 
Utiltown free tools
 
Outputs:
 
UPPERCASE:  UTILTOWN FREE TOOLS
lowercase:  utiltown free tools
Title Case: Utiltown Free Tools
camelCase:  utiltownFreeTools
snake_case: utiltown_free_tools
kebab-case: utiltown-free-tools
 
 
 
Use Cases
 

A case converter saves time whenever identifiers must follow a
        naming convention. Rename JavaScript variables to camelCase before
        committing. Flatten hand-written heading text into snake_case or
        kebab-case for database column names, CSS class names, or file
        names. Convert API response keys between PascalCase and camelCase so
        they match your backend or frontend style. Clean up pasted lists of
        titles, tags, or product names into a consistent format for imports
        and reports. Because the conversion happens locally, you can process
        sensitive or proprietary text with zero upload risk.

 
 
 
Best Practices
 
     
  • 
Decide the convention with your team or linter first — apply the
          tool afterwards so every identifier matches one rule.

    •  
  • 
Use camelCase for JS/TypeScript variables and
          functions, PascalCase for classes and components,
kebab-case for file and URL slugs, and
SCREAMING_SNAKE_CASE for constants.

    •  
  • 
Check acronyms after converting: a phrase like "API Key" becomes
          "apiKey" as expected, but unusual acronym casing may need a quick
          manual tweak.

    •  
  • 
Convert uniformly before sorting or comparing data so
          duplicates and mismatches are caught reliably.

    •  
 
 
 
Frequently Asked Questions
  
Are numbers preserved?
 
Yes. Words are split on non-alphanumeric characters, and numbers remain part of each word.
  
Is my text uploaded?
 
No. All conversions run locally in your browser. Nothing is sent to a server.
  
How are words split?
 
The tool splits on spaces, dots, underscores, hyphens, and other separators. Each resulting word is then re-joined in the chosen case.
  
What is the difference between camelCase and PascalCase?
 
Only the first letter differs. camelCase starts lowercase (myFunctionName), while PascalCase starts uppercase (MyFunctionName). They use the same rules for joining the remaining words.
  
Which case should I use for variables, files, and constants?
 
By convention JavaScript and TypeScript variables and functions use camelCase, components and classes use PascalCase, file names often use kebab-case, and constants use UPPERCASE or SCREAMING_SNAKE_CASE. Your team or linter is the real authority.
  
Does it handle acronyms correctly?
 
They are re-cased as whole words. Acronyms like "API" or "JSON" are not preserved: in camelCase, "JSON API" becomes "jsonApi", so acronym letters are lower-cased or capitalized mid-word and need manual review.
  
What happens with empty or single-word input?
 
Empty or whitespace-only input shows an explicit error message instead of a silent empty result. A single word is converted without joining — for example lowercase "color" stays "color", while camelCase of "COLOR" becomes "color".
  
 
Related Tools