Sentence Case vs Title Case for UI Copy

A designer leaves a comment: “Can we sentence-case the buttons?” An engineer replies that the design system says Title Case for nav. A PM pastes the Figma screenshot into Slack in Capitalize Each Word. Three people, three mental models, one settings screen that looks slightly wrong in every build.

Sentence case vs title case for UI copy is a product decision, not a grammar quiz. Publication headlines and news SERPs can happily use Title Case. Inside an app — buttons, toggles, menu items, empty states — sentence case usually wins on clarity. This guide shows when to break that default, with examples you can paste into a sentence case converter or Title Case converter.

The two patterns in one glance

Same strings, two house styles:

save changes
delete this project
account preferences
how notifications work

UI element	Sentence case	Title Case
Button	Save changes	Save Changes
Destructive action	Delete this project	Delete This Project
Settings row	Account preferences	Account Preferences
In-product heading	How notifications work	How Notifications Work

Sentence case lifts the first word (and proper nouns). Title Case lifts principal words and argues about this / How. For short UI chrome, that argument is rarely worth the pixels.

Why product teams default to sentence case

1. It sounds like a person. Buttons read as verbs in a conversation: Send invite, Add filter. Title Case can feel like a newspaper shouting inside a dialog.
2. Fewer style debates. You do not need AP vs Chicago for a 12-character button. First word up is enough.
3. Matches body help text. Error messages and tooltips are almost always sentence case. Mixing Title Case labels with sentence-case help creates a patchwork.
4. Design-system trend. Material Design, many open-source systems, and a large share of SaaS products document sentence case for UI labels. Apple’s human interface guidance has also steered many teams toward sentence-style labels in modern releases — always check the HIG version you target.

None of that makes Title Case “incorrect.” It makes sentence case the lower-friction default for product chrome.

Where Title Case still belongs in a product

Use Title Case (with a real style guide if the string is long) when the UI is presenting something that behaves like a title of a work:

• Help-center article titles that follow your docs style sheet.
• Branded feature names that are proper nouns (Smart Compose, Focus Mode) — treat them as names, not as generic labels.
• Marketing pages embedded in the app that intentionally match the public blog’s headline style.
• Platform constraints: a desktop shell or partner portal whose HIG still mandates title-style commands.

Feature name (proper):  Focus Mode
Generic label:          Focus mode settings
Article H1 (Chicago):   How Focus Mode Works with Offline Sync

If everything is Title Case — including On, Off, and To in the middle of toggles — you drifted from “feature naming” into “capitalization noise.”

Buttons, settings, navigation, and empty states

Buttons and actions

Prefer sentence case:

Save changes
Send invite
Download CSV

Keep the verb. Avoid ALL CAPS (SAVE CHANGES) unless a legal or OS template forces it. For the rare label that is a branded object, capitalize the brand, not every word: Open in Figma, not Open In Figma, unless Title Case is the documented standard.

Settings and form labels

Sentence case scales better when labels get long:

Send weekly summary emails
Show read receipts
Use dark theme after sunset

Title Case on those lines (Show Read Receipts) adds capitals without adding meaning. Proper nouns still stand up: Slack, Google Calendar, iOS.

Navigation

Short nav items are where teams split.

Style	Examples
Sentence case	Home, Projects, Team settings, Billing
Title Case	Home, Projects, Team Settings, Billing

Single-word items look identical. Multi-word items reveal the policy. Pick one and encode it in the design system — do not decide per screen.

Empty states and onboarding

Write these as prose:

No projects yet
Create a project to invite your team and track deadlines.

Title-casing the body (Create A Project To Invite…) makes onboarding feel like a brochure. Use sentence case for the paragraph; reserve Title Case for a formal headline above it if marketing insists.

Capitalized case and ALL CAPS are usually the wrong cousins

Capitalized Case (Save Changes To This Project) lifts To and This. That is Word’s Capitalize Each Word / Excel PROPER, not a UI system. Designers sometimes paste it from a spreadsheet of feature names. Run those strings through sentence case before engineering implements them. The Capitalized Case converter is useful for name lists — not for button labels.

UPPER CASE labels fatigue the eye and can look like warnings even when they are not. Prefer hierarchy (size, weight, color) over caps lock. If you truly need shouting for a destructive confirm, sentence case plus a red variant is clearer than DELETE THIS PROJECT FOREVER.

Aligning design, content, and engineering

A durable setup:

1. Document one default in the design system (“UI chrome: sentence case; article titles: Chicago Title Case”).
2. Keep a short exception list (branded feature names, legal strings).
3. Normalize copy decks before handoff. Paste a column of labels into the sentence case converter; skim for proper nouns; paste back into Figma or the CSV.
4. Don’t rely on CSS text-transform: capitalize. It produces capitalized case, breaks mid-sentence edits, and fights translators.

Before (messy deck)

SAVE CHANGES
Delete This Project
account Preferences
How Notifications Work

After (sentence-case UI policy)

Save changes
Delete this project
Account preferences
How notifications work

Account and How stand up because they start the label. This and notifications stay small. Restore iPhone / NASA with smart casing when those brands appear.

Microcopy checklist

• Buttons: sentence case, strong verb, no trailing period
• Settings: sentence case; proper nouns preserved
• Nav: one policy for multi-word items
• Errors: full sentences, sentence case
• Help articles: Title Case or sentence case per docs style — may differ from chrome
• No text-transform: capitalize as a substitute for content design
• Translators receive the policy; some languages capitalize differently

Related reading

• Style books for publication titles: AP vs APA vs Chicago vs MLA title case
• Mode definitions: title case vs sentence case vs capitalized case
• SERP titles (different job): title case for SEO and SERP titles
• Office mechanics: how to change case in Word, Excel, and Google Docs

Next steps

Open the sentence case converter for buttons, settings, and empty states. Use the Title Case converter only when the string is truly a title of a work or your HIG demands it. Paste once, normalize the deck, and ship UI that sounds like one product instead of three committees.