Text Case Converter
Ten cases, one click each
UPPER, lower, Title, Sentence, camelCase, PascalCase, snake_case, kebab-case, CONSTANT and aLtErNaTiNg.
Text Case Converter
Runs in your browser · nothing uploaded01 — How to use Text Case Converter
02 — Getting good results
03 — Questions
No. Every conversion is a string operation running in this browser tab. Nothing is sent to a server, nothing is stored, and closing the tab discards it.
It splits on the transition from a lowercase letter or digit to a capital, and on the boundary between an acronym and a following word — so HTTPServerError separates into HTTP, Server and Error rather than one blob or three letters.
No fixed limit. The work happens on your machine, so the practical ceiling is your browser's memory. Documents of a few megabytes convert instantly.
Because it alternates on letters only. If it counted spaces and punctuation, the rhythm would shift unpredictably at every word break instead of reading as a steady alternation.
04 — More about Text Case Converter
Why programming cases exist at all
Most programming languages forbid spaces in identifiers, so every naming convention is a different answer to the same question: how do you show where one word ends and the next begins without using a space? camelCase and PascalCase use a capital letter as the boundary marker, snake_case and CONSTANT_CASE use an underscore, and kebab-case uses a hyphen — which is why kebab-case appears in CSS and URLs, where hyphens are legal, but not in most languages, where a hyphen means subtraction. None is more correct than another; what matters is that a codebase picks one per context and holds to it, which is exactly the job this tool speeds up when moving a name from one context to another.
The acronym problem
Acronyms are where naming conventions quietly break down. In camelCase, parseXMLDocument runs three capitals together and the eye cannot find the word boundary; parseXmlDocument is unambiguous but looks wrong to anyone who reads XML as a word rather than three letters. Major style guides genuinely disagree: Microsoft's .NET guidance says capitalise only the first letter of acronyms longer than two characters, while much of the Java and JavaScript world preserves them whole. This tool does not take a side. Preserve acronyms on gives you the first convention, off gives you the second, and the only real mistake is mixing them within one codebase.
61 more tools
where this came from.
Same shell, same shortcuts, same promise: nothing leaves your browser.