camelCase is a naming convention where words are joined without spaces, with each word except the first starting with a capital letter. Example: myVariableName

snake_case is a naming convention where words are separated by underscores and all letters are lowercase. Example: my_variable_name

Text Processing

String Case Converter

Convert identifiers between camelCase, snake_case, kebab-case, and 5 other formats instantly.

Case Conventions

camelCase — JS/TS variables and functions
PascalCase — classes and React components
snake_case — Python, Ruby, database columns
kebab-case — CSS classes, HTML attributes, URLs
CONSTANT_CASE — constants and env variables
Advanced text manipulation: Advanced String Manipulation Techniques

Common Use Cases

Code migration — converting between language conventions
API integration — matching external naming styles
Database mapping — DB columns to code identifiers
Style guide — enforcing consistent naming

Tips

Input can be any mixed format — the converter splits on spaces, hyphens, underscores, and case boundaries
Numbers are treated as word characters
Be consistent within a codebase — inconsistency hurts readability
Acronyms like API become api in snake_case

Frequently Asked Questions

Does it handle mixed input?

Yes — input can be camelCase, snake_case, kebab-case, or plain words with spaces. The converter extracts words and reformats them in your chosen style.

What about acronyms?

Acronyms like XMLParser are treated as words. Conversion may split them: xml_parser in snake_case. Handle acronyms manually if your style guide requires XMLParser → xmlParser.

Which case for CSS?

BEM methodology uses kebab-case for blocks and elements: nav-bar__item--active. Tailwind uses kebab-case utility classes.

Which case for Python?

PEP 8 recommends snake_case for functions and variables, PascalCase for classes, and CONSTANT_CASE for module-level constants.