Title Case vs. Sentence Case: When to Use Each in UI Labels
October 29, 2026This topic always comes up when designing any sort of navigation, product names, content headers, etc. So I though it may be helpful to lay out some of the foundational methodologies we’ve referenced in the past to move toward consistencies. Which really is the key – Once you pick an approach for your project, stick with it through and through.
Some best practices to consider:
Use Title Case for short, fixed navigation labels on platforms that expect it. Use sentence case for almost everything else. That is where the major design systems have landed, and it is the safest default for a new product.
Capitalization looks like a small detail, but every button, tab and menu item carries it. Choose inconsistently and the interface feels assembled from parts. Choose deliberately and the product reads as one voice.
The two styles differ simply:
- Title Case capitalizes the major words: Save As Draft, Account Settings.
- Sentence case capitalizes only the first word and proper nouns: Save as draft, Account settings.
What the major design systems say
Only Apple still leans on Title Case. Google, IBM and most web and SaaS products have moved to sentence case.
| Platform | Buttons | Field Labels / Menus / Tabs | Headings / Titles | Overall Trend |
|---|---|---|---|---|
| Apple HIG | Title Case (traditional) | Title Case | Title Case | Title case for structure |
| Google Material 3 | Sentence case | Sentence case | Sentence case | Sentence case everywhere |
| IBM Carbon | Sentence case | Sentence case | Sentence case | Sentence case preferred |
| Many web/SaaS | Sentence case | Mix (often sentence) | Title or sentence | Sentence case winning |
Apple. Apple’s guidelines define two styles, title-style and sentence-style, and let the type of element decide which applies (Apple text style guidelines). In practice, buttons, menu items and window titles on Apple platforms have long used Title Case.
IBM Carbon. Carbon’s rule is direct: “Use sentence-style capitalization for headings, titles, labels, banners, and similar elements, unless noted otherwise” (Carbon writing style).
Google Material 3. Material uses sentence case across buttons, labels and headings.
Others. Red Hat’s PatternFly tells teams to “default to sentence case across all UI elements,” including navigation, page titles and buttons (PatternFly capitalization).
When to use Title Case
Title Case works best for short labels that name a place or a thing rather than describe an action.
- You’re building for Apple platforms. Native macOS and iOS apps that use Title Case for menus, buttons and window titles feel at home next to system apps. Matching the platform matters more than your personal preference.
- Short, fixed navigation. One- to three-word labels in a top nav, sidebar or tab bar read like signposts: Pricing, Case Studies, Contact Us. Title Case gives them a crisp, scannable look.
- Product, feature and plan names. Proper nouns stay capitalized in any style: Smart Inbox, Pro Plan. Title Case here signals that the label is a name, not a description.
- Your brand voice is formal. Law firms, financial services and enterprise products sometimes choose Title Case for its more traditional, authoritative tone. If you do, apply it everywhere the rule says, not just where it looks good.
When not to use Title Case
Avoid Title Case once a label grows past a few words or starts to read like a sentence.
- Longer button labels. Send Me A Copy Of This Message is harder to read than Send me a copy of this message. Every capital is a small bump the eye has to cross.
- Messages, errors and help text. Alerts, toasts, tooltips and form hints are sentences. Write them that way: Your password must be at least 8 characters.
- Form field labels. Labels like Email address and Company name sit right next to sentence-case help text. Sentence case keeps the form calm and consistent.
- Products built for many languages. Most languages don’t use Title Case, and its rules vary even in English. Sentence case translates cleanly and saves translators from guessing.
- Friendly, conversational brands. Sentence case sounds like a person talking. That’s why Google, IBM and most SaaS products now default to it.
- When your team can’t apply the rules reliably. Title Case has tricky exceptions (a, of, with, to). Inconsistent capitalization looks worse than either style done well. Sentence case has one rule, so it’s much harder to get wrong.
Rules of thumb
If you’re unsure, use sentence case. It’s the modern default and the easiest to keep consistent.
| UI Element | Recommended Style | Example |
|---|---|---|
| Buttons | Sentence case | Save changes |
| Main navigation and tabs | Either; pick one | Case studies / Case Studies |
| Page and section headings | Sentence case | Recent projects |
| Form field labels | Sentence case | Email address |
| Messages, errors, tooltips | Sentence case, with punctuation | Your file was uploaded. |
| Product, feature and plan names | Always capitalized as names | Pro Plan |
| Native Apple app menus and buttons | Title Case | Save As… |
Before you ship, ask these questions:
- Is the platform’s convention clear (for example, a native Apple app)? Follow it.
- Is the label more than three or four words? Use sentence case.
- Is it a full sentence or a message? Use sentence case and end punctuation.
- Is it a proper name? Capitalize it, whatever the surrounding style.
- Will it be translated? Lean toward sentence case.
- Does it match the labels around it? Consistency beats either style.
The bottom line
Pick one style, write it down and apply it everywhere. Neither style is wrong, but switching between them is.
For most web products today, that choice is sentence case, with Title Case kept for proper names and, if you like, short top-level navigation. Add the rule to your style guide or design system so every designer, developer and writer makes the same call.
