The difference in one glance
- Title Case: "How to Bake the Perfect Sourdough" — major words capitalized.
- Sentence case: "How to bake the perfect sourdough" — only the first word (and proper nouns) capitalized.
Title case is formal and traditional; sentence case is calm and contemporary. Neither is universally "correct" — context decides. Our title case rules guide covers the capitalization details when you choose title case.
What readability research says
Sentence case has a measurable edge in scanning speed. The varied word shapes created by mixed capitalization help the eye distinguish words faster than the uniform rectangles of title case — the same reason ALL CAPS is hardest to read. Studies on interface text consistently find sentence case faster to parse, which is why Apple, Google, and Microsoft standardized on it for UI.
Title case, meanwhile, carries signaling value: it marks text as a title, lending formality and importance. In editorial contexts (book titles, article headlines), readers expect it and parse the signal instantly.
Where each belongs
- Use title case for: book and article titles, academic paper headings, formal headlines, presentation slide titles.
- Use sentence case for: user interfaces (buttons, menus, dialogs), email subject lines, subheadings in modern web writing, form labels, error messages.
- Either works for: blog post H1s — pick one and be consistent across the site.
The trend is clearly toward sentence case on the web: it feels friendlier, localizes better (many languages lack title-case conventions), and avoids the endless "is this word major?" debates.
Converting between them
Paste any text into our case converter and switch between Title Case and Sentence case with one click — handy when repurposing a formal headline for an email subject line or UI string. Whatever you choose, apply it consistently: mixed casing across a site looks accidental, and accidental looks unprofessional.
The accessibility angle
Casing choices have real accessibility consequences. Screen readers may interpret ALL CAPS as acronyms, spelling them out letter by letter — "SALE" becomes "S-A-L-E," a miserable experience. (The fix some sites use — normal text styled uppercase via CSS — is invisible to assistive tech and to copy-paste, which creates its own problems.)
For readers with dyslexia, the evidence favors sentence case: distinctive word shapes aid recognition, while uniform capitalization flattens the visual cues dyslexic readers rely on. Title case sits between the two — better than all caps, worse than sentence case.
Cognitive load matters for everyone, not just diagnosed conditions: interfaces scanned under stress, on small screens, or in a second language all benefit from the calmest casing. This is one more reason the industry converged on sentence case for UI — it is not just aesthetics, it is inclusion. Whatever style guide you follow, keep body text and interface strings in sentence case as the accessible default.
Auditing is straightforward: search your product or site for ALL-CAPS strings longer than a few characters — legitimate acronyms (NASA, HTML) excepted — and convert them to sentence case with our case converter. Pay special attention to error messages and warnings, which are the most likely to be shouted in caps and the most stressful to encounter. Calm casing in stressful moments is a small kindness with an outsized effect on user trust — and it costs nothing at all to implement across an entire product today.
For developer contexts with their own conventions, see camelCase vs. snake_case.