🔤 Case Converter
Why Naming Conventions Matter in Programming
Every programming language and framework has its own preferred naming convention. JavaScript uses camelCase for variables, Python prefers snake_case, CSS uses kebab-case, and C# follows PascalCase. Using the wrong convention doesn’t break your code, but it violates community standards, makes code harder to read, and can trigger linter warnings that clutter your development workflow.
When you’re refactoring code between languages, porting a Python library to JavaScript, or converting database column names to API response fields, you need to convert between these formats repeatedly. Doing it manually is error-prone and tedious — a case converter eliminates that friction.
Supported Formats
| Format | Example | Used in |
|---|---|---|
| camelCase | myVariableName | JavaScript, Java, TypeScript |
| PascalCase | MyVariableName | C#, .NET, React components |
| snake_case | my_variable_name | Python, Ruby, Rust, databases |
| SCREAMING_SNAKE | MY_VARIABLE_NAME | Constants in most languages |
| kebab-case | my-variable-name | CSS, HTML attributes, URLs |
| dot.case | my.variable.name | Java packages, property files |
| path/case | my/variable/name | File paths, REST API routes |
| Title Case | My Variable Name | Headings, UI labels |
| Sentence case | My variable name | Paragraphs, descriptions |
| UPPER CASE | MY VARIABLE NAME | Acronyms, emphasis |
| lower case | my variable name | Normalization, search |
| Alternating | mY vArIaBlE nAmE | Meme text, sarcasm |
| Reverse | eman elbairaV yM | Puzzles, encoding |
Real-World Conversion Scenarios
Database to API
SQL columns are typically snake_case (user_first_name), but JSON API responses use camelCase (userFirstName). Convert column names when building serializers.
Python to JavaScript
Porting a Python module to JS means converting every snake_case function and variable name to camelCase.
CSS class naming
Converting component names from PascalCase (React) to kebab-case (CSS) when writing corresponding stylesheets.
Environment variables
Config values in .env files follow SCREAMING_SNAKE_CASE. Convert readable names to this format for deployment configs.
Frequently Asked Questions
Yes. Paste multiple names separated by newlines, and each one will be converted independently. This is especially useful when refactoring a list of database columns or API fields.
The converter splits your input into individual words by detecting separators (underscores, hyphens, dots, spaces, slashes) and camelCase boundaries (lowercase-to-uppercase transitions). It then reassembles the words in your chosen output format.
Acronyms like “API” or “HTML” in input text are treated as single words. So parseHTMLResponse converts to parse_html_response in snake_case. This follows the convention used by most code style guides.
No. All conversion happens in your browser using JavaScript string manipulation. Your code and variable names are never transmitted anywhere.