What next?
Changing case is one text transform. These are the rest.
How to use this tool
- Paste or type your text.
- Pick the case you want — UPPER, lower, Title, Sentence, camelCase and more.
- Copy the converted text.
What your result means
The converted text is your original wording with only the letter casing and word separators changed — no words are added, removed or reordered. Converting to camelCase or snake_case also strips the spaces, because those conventions use capitalisation or underscores to mark word boundaries instead.
That makes most conversions reversible, but not all of them. Going from "the quick brown fox" to camelCase and back is safe; going from ALL CAPS back to Sentence case cannot restore proper nouns, because the information about which words were capitalised was destroyed on the way. Convert away from a lossy case, not back into one, and always eyeball acronyms and names afterwards.
Why this one is different
Nothing is discarded silently. Punctuation that the identifier styles cannot keep is counted and named before you copy, and text with no lower-case letters is flagged, because no transform can work out which words were proper nouns once that has been lost. Under the box, a single paste is rendered in all eight styles at once, so the choice is made by reading rather than by clicking through them one at a time.
Why programmers argue about camelCase vs snake_case
Behind every tidy codebase is a quiet holy war over naming: camelCase, snake_case, kebab-case. It sounds trivial, but consistent casing is what keeps huge projects readable — and mismatched casing is a classic source of bugs.
Whether you’re fixing a shouty ALL-CAPS paragraph or formatting variable names, converting case in one click saves retyping and mistakes.
Case types explained
Worked example
The phrase parse HTML file in every supported case:
Sentence case Parse html file
camelCase parseHtmlFile
PascalCase ParseHtmlFile
snake_case parse_html_file
kebab-case parse-html-file
Note what happened to HTML. Every convention here treats it as an ordinary word, so it becomes Html. Most style guides — Google’s among them — prefer exactly that, because parseHTMLFile becomes unreadable once two acronyms sit next to each other. If your house style keeps acronyms uppercase, fix them by hand after converting.
Naming conventions are readability rules, not style preferences
Every language has a dominant convention, and matching it is the difference between code that reads as native and code that reads as translated. JavaScript and Java use camelCase for variables and PascalCase for classes; Python and Ruby use snake_case for both variables and functions; constants are SCREAMING_SNAKE_CASE almost everywhere; CSS classes and URL slugs use kebab-case, because a hyphen is a word separator to a search engine while an underscore is not.
Databases add their own wrinkle. SQL identifiers are case-insensitive unless quoted, so a camelCase column name usually arrives back from the database folded to lowercase — which is why snake_case is the near-universal convention for table and column names regardless of the application language sitting on top.
Acronyms are the genuinely unresolved case. HTTPServer, HttpServer and httpServer are all in active use, and no convention wins outright; Google's Java style guide treats acronyms as ordinary words, giving HttpServer, which is the more consistent choice if you have to pick. Whatever you choose, apply it everywhere — a codebase that mixes both is harder to search than one that picks the "wrong" one.
Frequently asked questions
When would I use camelCase or snake_case?＋
Mostly in programming — camelCase for JavaScript variables, snake_case for Python and databases, kebab-case for URLs and CSS classes.
Does converting lose my original text?＋
Each button transforms the text in the box. Re-type or paste to start over — nothing is saved or sent anywhere.
What is the difference between Title Case and Sentence case?＋
Title Case capitalises each significant word, as in headings. Sentence case capitalises only the first word and any proper nouns, which is what most style guides now prefer for UI labels and headlines.
Which case should I use for a URL slug?＋
kebab-case, all lower case with hyphens. Search engines treat hyphens as word separators while underscores are read as part of a single token.
Why does camelCase matter in code?＋
Most languages have a dominant convention: camelCase for variables in JavaScript and Java, snake_case in Python and Ruby, PascalCase for classes almost everywhere. Matching the convention is what makes code readable to others.
Does it handle acronyms sensibly?＋
Acronyms are the awkward case in any converter. HTTPServer and HttpServer are both defensible; check the output when your text contains initialisms rather than assuming.
Related tools
Assumptions & limitations
Case conversion is mostly mechanical, with a few edge cases:
- Title Case here capitalises each word. Editorial style guides differ on whether short prepositions and articles should be lowercased, so check the house style you are writing for.
- Acronyms are not detected — converting to camelCase turns "parse HTML file" into "parseHtmlFile", which most style guides prefer but some do not.
- Conversion between naming conventions is lossless only where word boundaries are unambiguous. A single lowercase run with no separators cannot be split reliably.
- Locale-specific casing rules — most famously the dotless i in Turkish — are handled by your browser's own case mapping.
Sources & references
Casing conventions and the character rules behind them are defined by:
- Unicode Standard Annex #21 — case mappings, including locale-specific rules
- MDN Web Docs — locale-aware case conversion in the browser
- Google Style Guides — naming conventions across programming languages