Text Case Converter
Convert text to UPPERCASE, lowercase, Title Case, camelCase, snake_case, kebab-case, a URL slug and more, instantly in your browser.
A text case converter rewrites the same words in a different capitalisation or token style. Paste a phrase and get it back as UPPERCASE, lowercase, Title Case, Sentence case, and the programming styles camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case and dot.case, plus a URL slug. Each result has its own copy button, so you can grab exactly the form you need.
Loading Text Case Converter… If nothing happens, please enable JavaScript.
Frequently asked questions
What is the difference between camelCase and PascalCase?
How is the URL slug generated?
Will it correctly convert text that is already camelCase or snake_case?
How does Title Case decide which words to capitalise?
What is CONSTANT_CASE used for?
Is my text sent to a server?
About Text Case Converter
These styles are not interchangeable, and using the wrong one causes real bugs. JavaScript and Java conventionally use camelCase for variables and PascalCase for classes; Python and Ruby use snake_case; environment variables and constants use CONSTANT_CASE; CSS classes, file names and URL paths favour kebab-case. A URL slug goes one step further: it lowercases the text, replaces every run of non-alphanumeric characters with a single hyphen, and trims stray hyphens, producing something clean and readable like 'my-first-blog-post'.
The converter is token-aware. It splits on spaces and punctuation but also on case boundaries, so an input that is already camelCase or snake_case is understood and re-cased correctly rather than being mangled. Everything runs in your browser, with no upload and no length limit worth worrying about.
Why programmers argue about case
The naming styles have nicknames that stuck. 'camelCase' is named for the hump in the middle, and 'snake_case' for the way the underscore makes words slither along the baseline. 'kebab-case' imagines the words skewered on hyphens. These are not just aesthetics: the choice is so tied to language culture that mixing styles in one codebase is considered a code smell, and most teams enforce a single convention with a linter.
The split runs deep. The Python community formalised snake_case in its PEP 8 style guide, while JavaScript and Java leaned into camelCase from their C and C-derived roots. When data crosses between systems, for example a snake_case JSON API consumed by a camelCase front end, developers often write a conversion layer to translate keys, which is exactly the kind of mechanical re-casing this tool does by hand.