What each case is for
| Case | Example | Used for |
|---|---|---|
| Sentence case | The lord of the rings | Body text, most modern headings, UI labels |
| Title Case | The Lord of the Rings | Book and article titles, headlines in US style |
| UPPERCASE | THE LORD OF THE RINGS | Short labels and acronyms — hard to read in bulk |
| lowercase | the lord of the rings | Normalising data, tags, email addresses |
| camelCase | theLordOfTheRings | Variables in JavaScript, Java, Swift |
| PascalCase | TheLordOfTheRings | Class names, React components, C# types |
| snake_case | the_lord_of_the_rings | Python, Ruby, SQL columns |
| kebab-case | the-lord-of-the-rings | URLs, CSS classes, file names |
How title case is applied here
Title case is not simply “capitalise every word”. The convention most style guides share is to capitalise the first and last words and everything in between except short articles, conjunctions and prepositions: a, an, and, as, at, but, by, for, in, nor, of, on, or, per, so, the, to, up, via, vs, yet.
So the lord of the rings becomes The Lord of the Rings, not The Lord Of The Rings. Style guides differ on prepositions of four or more letters — some capitalise Between and Through — so check the result against your house style.
Notes on the programming cases
camelCase, PascalCase, snake_case and kebab-case all discard punctuation and split on any non-alphanumeric character. That is deliberate: these are identifier formats, and a stray apostrophe or comma would make the result invalid.
Common questions
Can I undo a conversion?
Yes — the Undo button steps back through every conversion you have applied, including Clear.
Is my text uploaded?
No. Every conversion happens in your browser on this page.
Does it handle accented characters?
Yes. Case changes use full Unicode rules, so é becomes É correctly, and accents survive the identifier cases as best they can.