Convert text to seven case styles at once
Type or paste a sentence and see it in UPPERCASE, lowercase, Title Case, Sentence case, camelCase, snake_case and kebab-case simultaneously. Comparisons stay on one screen, so you can pick the right style for a headline, a variable name or a URL without retyping anything.
UPPERCASE
For short warning labels, acronym-heavy data fields and list headers where the text is scanned rather than read.
THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG
lowercase
Useful for normalising tags, email addresses, file names on case-insensitive systems and search terms before comparison.
the quick brown fox jumps over the lazy dog
Title Case
Headlines and book titles. Short joining words (a, an, the, of, for, and, to) stay lowercase unless they open or close the title; acronyms such as API and JSON are preserved.
The Quick Brown Fox Jumps Over the Lazy Dog
Sentence case
Sentence case is the calm default for body copy, buttons and help text: capital on the first word of each sentence, everything else lowercase.
The quick brown fox jumps over the lazy dog
camelCase
JavaScript and Java variables, JSON keys and CSS-in-JS properties. Each word after the first is capitalised and all separators disappear.
theQuickBrownFoxJumpsOverTheLazyDog
snake_case
The convention in Python, Ruby and most SQL schemas: lowercase words joined by underscores, readable in a monospaced editor.
the_quick_brown_fox_jumps_over_the_lazy_dog
kebab-case
HTML attributes, package names, class names in utility CSS frameworks and — most importantly — URL slugs, where hyphens are read as word breaks.
the-quick-brown-fox-jumps-over-the-lazy-dog
Boundaries are detected, not just spaces: myVariableName becomes three words, so camelCase input round-trips through snake_case and kebab-case cleanly. Apostrophes are dropped in the code styles (don't stop → dontStop) because identifiers cannot contain them.
Which style belongs where
| Style | Example | Typical home |
|---|---|---|
| UPPERCASE | NET TOTAL | Table headers, short labels, data exports |
| lowercase | net total | Tags, emails, search terms |
| Title Case | Net Total for March | Article titles, book and course names |
| Sentence case | Net total for March | Buttons, menus, help text, body copy |
| camelCase | netTotal | JavaScript and Java variables, JSON keys |
| snake_case | net_total | Python, Ruby, SQL columns, config keys |
| kebab-case | net-total | URLs, HTML attributes, npm package names |
Two rules cover most of the mistakes people make. First, pick the convention that the surrounding code or publication already uses, even if you dislike it — mixed conventions cost more review time than a suboptimal one. Second, never run a bulk case conversion over URLs, email addresses, code or file names without checking the result: lowercasing a case-sensitive path breaks it, and Title Case can turn example.com into Example.Com.
For the reasoning behind each style, including how the major style manuals disagree about small words, read the seven case styles explained.