Every naming case, and when to use which
Programming languages never agreed on how to spell multi-word identifiers. JavaScript and Java settled on camelCase, Python and Ruby on snake_case, HTTP headers and CSS on kebab-case, constants everywhere on SCREAMING_SNAKE_CASE, and class names on PascalCase. A case converter exists because real work constantly crosses those borders: API payloads from a Python backend, environment variables, CSS custom properties, database columns.
The hard part is not the casing itself — it is splitting the input back into words. Naive tools butcher acronyms (XMLHttpRequest should become xml_http_request, not x_m_l_http_request) and panic on digits (md5Hash is md5_hash, while version2Update is version_2_update). This title case converter and identifier re-caser handles both, and its Title Case mode uses simple per-word capitalization: every word capitalized, no small-word exceptions for and/of/the.
Open the free Case Converter — no signup, runs entirely in your browser.
How to use it
- Paste or type your text — any mix of camelCase, snake_case, kebab-case, spaces or all-caps works.
- Pick one of the 8 target cases from the labeled selector (camelCase through Title Case).
- Read the converted result live, then hit Copy to put it on your clipboard.
- For bulk renames, paste a whole list — every identifier converts in one pass.
Why this one
- Acronym runs split correctly: XMLHttpRequest → xml_http_request, parseHTML → parse_html.
- Digit-aware: short tokens like md5, utf8 and sha256 stay glued; version2Update splits as version / 2 / update.
- Messy separators tolerated — mixed underscores, dashes and repeated spaces are normalized.
- Unicode-safe casing: accented and non-Latin letters follow standard Unicode rules, never get mangled.
Frequently asked questions
What is the difference between camelCase and PascalCase?
Both join words without separators and capitalize each word — the only difference is the first word. camelCase keeps it lowercase (userProfileImage) and is used for variables and functions; PascalCase capitalizes it (UserProfileImage) and is reserved for classes, types and components in most style guides.
Does Title Case follow AP or Chicago style rules?
No — and that is deliberate. Style-guide title case lowercases small words like and, of and the, which is great for headlines but unpredictable for identifiers and labels. This converter capitalizes every word uniformly, so War and Peace becomes War And Peace. Simple, deterministic, and clearly documented.
How are numbers handled when converting case?
Digit runs are split into their own word unless they follow a very short letter run. That keeps common tokens intact — md5, utf8 and sha256 survive as single words — while a standalone number after a longer word becomes its own word, so version2Update converts to version_2_update in snake_case.
What happens to apostrophes and punctuation?
Apostrophes are stripped outright — don't becomes dont — because leaving them in would leak punctuation into identifiers like don-t. All other punctuation acts as a word separator, so foo_bar-baz qux cleanly splits into four words regardless of the mixed separators.