Change text to UPPERCASE, lowercase, Title or Sentence case.
Paste text and convert it between upper case, lower case, sentence case, title case and the programming conventions. It is a small job that is tedious by hand and easy to get subtly wrong, particularly title case, which follows rules most people apply inconsistently.
| Style | Example | Used for |
|---|---|---|
| UPPER CASE | THE QUICK BROWN FOX | Headings, acronyms, emphasis |
| lower case | the quick brown fox | Normalising input, tags, URLs |
| Sentence case | The quick brown fox | Body text, UI labels |
| Title Case | The Quick Brown Fox | Headlines, book and article titles |
| camelCase | theQuickBrownFox | Variables in Java, JavaScript |
| PascalCase | TheQuickBrownFox | Class names, React components |
| snake_case | the_quick_brown_fox | Python, Ruby, database columns |
| kebab-case | the-quick-brown-fox | URLs, CSS classes, filenames |
The convention most style guides follow capitalises the first and last words, plus all major words, but leaves short function words lowercase in the middle of a title:
So it is The Sound and the Fury, not The Sound And The Fury. Style guides disagree at the margins: Chicago lowercases all prepositions regardless of length, while AP capitalises those of four letters or more, making it Gone With the Wind in one and Gone With The Wind in neither. Verbs are capitalised however short they are, which is why Is and Be take capitals in a headline.
Most modern interface style guides — including Google's and Apple's — now specify sentence case for headings, buttons and labels. The reasoning is that it reads faster, handles product names and acronyms more gracefully, and translates into other languages without the awkwardness that title case creates in German or French, where capitalisation rules differ entirely. If you are writing UI text and have no house style, sentence case is the safer default.
Case style in code is not decoration; it carries meaning that readers rely on.
For URLs specifically, hyphens are preferable to underscores. Search engines treat a hyphen as a word separator and an underscore as a word joiner, so blue-widgets is read as two words and blue_widgets as one.
Case conversion is not universal. Chinese, Japanese, Korean, Arabic, Hebrew and several Indic scripts have no concept of case at all, so conversion leaves them unchanged. Where case does exist, it can behave unexpectedly:
This tool applies standard Unicode case mapping, which handles most of this correctly but uses the default locale rather than a language-specific one.
The conversion happens in your browser. Nothing you paste is uploaded, which matters if you are reformatting anything confidential. Long documents convert instantly since it is a straightforward character mapping.
Title case leaves articles, coordinating conjunctions and short prepositions lowercase in the middle of a title, so it is "The Sound and the Fury". Capitalising every word would give "The Sound And The Fury", which no major style guide accepts.
Sentence case is the modern default for interfaces and increasingly for web content — both Google and Apple specify it. Title case remains standard for book titles, article headlines and academic references. If you have a house style, follow it.
Only the first letter. camelCase starts lowercase and is used for variables and functions; PascalCase starts uppercase and is used for classes, types and components. The distinction lets a reader tell a type from a value at a glance.
Hyphens. Search engines treat a hyphen as a word separator and an underscore as a joiner, so "annual-report" is read as two words while "annual_report" is read as one. Hyphens are also easier to read in a long slug.
Yes, using standard Unicode case mapping, so accented Latin, Greek and Cyrillic convert correctly. Scripts without case — Chinese, Japanese, Arabic, Hebrew, Devanagari — pass through unchanged.