The four cases, with real examples
| Case | Result |
|---|---|
| Original | the QUICK brown fox jumps over the LAZY dog |
| UPPERCASE | THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG |
| lowercase | the quick brown fox jumps over the lazy dog |
| Title Case | The Quick Brown Fox Jumps Over the Lazy Dog |
| Sentence case | The quick brown fox jumps over the lazy dog |
How each conversion is defined
- UPPERCASE
- Every cased character becomes its uppercase form using the browser's Unicode case tables. German “ß” becomes “SS”, Turkish “i” follows the browser's locale, and characters with no uppercase form (CJK ideographs, digits, emoji) pass through unchanged.
- lowercase
- The exact inverse: every cased character becomes lowercase. Nothing else is altered.
- Title Case
- The first letter of each word is capitalised and the rest lowercased. Hyphenated and slashed compounds capitalise each part, so state-of-the-art becomes State-of-the-Art. With Keep short words lowercase switched on, a fixed list of short function words — a, an, and, as, at, but, by, for, if, in, nor, of, on, or, per, the, to, via, with, from and similar — stays lowercase unless it is the first or last word of the text. This is the convention most book and newspaper style guides use.
- Sentence case
- Everything is lowercased, then the first letter after a full stop, question mark, exclamation mark or ellipsis is capitalised. Closing quotes and brackets immediately after the punctuation are handled, so "like this." capitalises correctly. Proper nouns are not restored — sentence case cannot know that “paris” should be “Paris” — so give the result a quick read before publishing.
Why Unicode-aware casing matters
Naive case conversion using ASCII ranges mangles anything outside a–z. With
proper Unicode casing, “é” becomes “É”, Greek “α” becomes “Α”, Cyrillic “я” becomes “Я”, and
the Turkish dotless “ı” is treated as its own letter rather than as an “i”. Text that mixes
scripts — common in multilingual documents, subtitles and academic work — survives intact.
A note on ALL CAPS. Converting a whole document to UPPERCASE is fine for labels, acronyms and code constants, but long passages in capitals are measurably slower to read and are read aloud letter by letter by many screen readers. Use it deliberately, not as a default.
Common uses
- Fixing text that arrived in ALL CAPS from a legacy system or a shouty spreadsheet column.
- Making headings and table labels consistent when converting a document to HTML.
- Producing lowercase slugs, tags and identifiers from human-readable labels.
- Standardising names and titles in a mailing list before a merge.
Frequently asked questions
- Is title case the same as capitalising every word?
- No. Capitalising every word (sometimes called Start Case) gives The Quick Brown Fox Jumps Over The Lazy Dog. True title case, as used by most book and newspaper style guides, keeps short function words lowercase: The Quick Brown Fox Jumps Over the Lazy Dog. Switch on Keep short words lowercase to get the second form.
- What is the difference between sentence case and lowercase?
- Lowercase turns every letter lowercase, including the first letter of each sentence. Sentence case lowercases everything and then capitalises the first letter after a full stop, question mark, exclamation mark or ellipsis, which is how ordinary prose is written.
- Does sentence case fix proper nouns like names of places?
- No, and no tool can do this reliably. Sentence case has no way to know that “paris” should be “Paris”, so give the result a quick read before publishing. That limitation applies to every sentence-case converter, not just this one.
- Why did “ß” become “SS” in UPPERCASE?
- Because that is the correct Unicode uppercase mapping for German sharp S. Uppercasing is not always a one-to-one letter swap: some characters expand into more than one character. The converter uses the browser's own Unicode case tables, so accented letters, Greek, Cyrillic and other scripts convert correctly rather than being mangled outside a–z.
- Can I convert only part of my text?
- Yes. Select the passage you want in the input box and the converter restricts the change to your selection; with nothing selected it converts the whole box.
- Is ALL CAPS bad for accessibility?
- Long passages in capitals are measurably slower to read, and many screen readers spell words out letter by letter. Capitals are fine for labels, acronyms and code constants, but for body text use title case or sentence case instead.