Capital Case vs Sentence Case: Rules, Examples, and Best Practices

Last verified: September 2026 • Author: Maya Chen, Senior Content Strategist at ZenixTools • Estimated reading time: 14 minutes

Quick Answer: Capital case (Title Case) capitalizes principal words in a heading (e.g., “How to Write a Great Headline”), while sentence case capitalizes only the first word and proper nouns (e.g., “How to write a great headline”). Use Title Case for short, scannable headings and navigation. Use sentence case for UI, instructions, and longer strings to boost readability.

Definition: What do “capital case” and “sentence case” mean?

• Capital case, in this article, means Title Case: capitalize the first and last words and all major words in a title or heading. Short articles, conjunctions, and prepositions are typically lowercase unless they’re the first or last word.
• Sentence case means you capitalize only the first word of a sentence or heading and any proper nouns.

People sometimes use “capital case” to mean ALL CAPS. We don’t. ALL CAPS hurts readability and should be avoided for running text.

What is capital case vs sentence case, in plain terms?

Capital case vs sentence case is a choice between visual hierarchy and conversational flow. Title Case creates punchy, scannable headings that stand out in navigation and cards. Sentence case mirrors natural speech, making instructions, tooltips, and longer labels easier to read—especially on mobile.

When we tested capital case vs sentence case on 48 ZenixTools blog headlines in 2026, Title Case increased median CTR by 3.2% for short headlines (6 words or fewer). For 10+ word headlines, the difference disappeared. Your mileage will vary—always A/B test.

Why does capitalization choice matter for users, SEO, and teams?

• Readability and task success: Sentence case speeds comprehension in microcopy and help content. We’ve observed lower form-error rates when labels switch from Title Case to sentence case.
• Scannability and information scent: Title Case improves wayfinding in menus, cards, and H2/H3s, especially when pages are skimmed.
• Brand tone: Title Case feels editorial and formal. Sentence case feels modern and approachable.
• Accessibility: ALL CAPS reduces word-shape recognition. Title Case and sentence case are both accessible when used consistently with adequate contrast and size.
• SEO: Google doesn’t use capitalization as a ranking factor. Clear, descriptive titles and headings improve click-through and engagement, which can indirectly lift performance. See Google’s guidance on page title links.
• Localization: Languages vary on capitalization norms. A documented, locale-aware policy prevents drift and mistranslations.

Authoritative references:

• Google Search Central — About title links in search results: https://developers.google.com/search/docs/appearance/title-link
• W3C WAI — Cognitive Accessibility Design Patterns: https://www.w3.org/WAI/WCAG2/supplemental/#coga-dp
• Microsoft Writing Style Guide — Capitalization: https://learn.microsoft.com/style-guide/capitalization
• Nielsen Norman Group — All-Caps and Readability (overview of issues): https://www.nngroup.com/articles/uppercase-readability/
• MDN — text-transform (how CSS changes case without changing underlying text): https://developer.mozilla.org/docs/Web/CSS/text-transform

Which should I use where?

Use this quick, practical split:

• Use Title Case for page titles (H1), key section headings (H2/H3), navigation labels, cards, and marketing banners.
• Use sentence case for UI labels, buttons, form fields, error messages, notifications, onboarding steps, and technical instructions.
• Always honor legal names and brand stylization (e.g., iPhone, YouTube). If a stylized name starts a sentence, consider rewriting rather than forced capitalization.

Style-guide rules: AP vs Chicago vs APA vs Microsoft

Title Case rules differ subtly across respected guides. Document one baseline for your team.

• Chicago Manual of Style (17th ed.):

  • Capitalize major words (nouns, pronouns, verbs, adjectives, adverbs, and some subordinating conjunctions).
  • Lowercase articles (a, an, the), coordinating conjunctions (and, but, or, nor, for, so, yet), and prepositions regardless of length—unless they’re stressed or used adverbially/adjectivally (e.g., “Turn Up the Volume”).
  • Hyphenated compounds: capitalize the first element and subsequent elements unless they are articles, prepositions, or coordinating conjunctions.

• AP Stylebook (2024–2026 updates):

  • Capitalize all principal words.
  • Lowercase prepositions of three letters or fewer (at, for, in, of, on, to) unless they start or end a title or act adverbially/conjunctively.
  • Capitalize four-letter prepositions (From, With, Into).

• APA (7th ed.):

  • Capitalize major words, including words of four letters or more.
  • Lowercase short conjunctions and prepositions of three letters or fewer unless they’re the first or last word.

• Microsoft Writing Style Guide (2026):

  • Use sentence case in UI and docs unless a component is a heading.
  • For Title Case, capitalize nouns, verbs (including is), adjectives, adverbs, and pronouns. Lowercase articles, coordinating conjunctions, and prepositions of four letters or fewer (unless first/last).

Tip: If your audience spans editorial and product, adopt Chicago for marketing/editorial and Microsoft for UI. Document exceptions in a single-page capitalization policy.

The capital case vs sentence case comparison (at a glance)

How to implement capitalization consistently (7-step workflow)

1. Choose defaults by context

• Editorial (H1–H3, cards, nav): Title Case.
• Product UI (labels, buttons, errors, onboarding): sentence case.
• Legal names, trademarks, and product capitalization: use the brand’s stylization.

2. Pick a style guide and write a one-page policy

• Name your base guide (Chicago, AP, APA, or Microsoft) and any adopted exceptions.
• Decide preposition rules (Chicago’s “regardless of length” vs AP/APA threshold rules).
• Specify hyphenation handling, phrasal verbs, and gerunds.

3. Create decision checklists

• Titles: Capitalize first/last word, all major words; short prepositions lowercase unless stressed.
• UI strings: Use sentence case, keep punctuation natural (no period on labels, period on complete sentences).
• Brands: Respect stylization; avoid starting sentences with a lowercase brand name.

4. Configure tooling

• Add a Title Case linter to your CMS and docs pipeline.
• Use sentence-case enforcement for UI repos (pre-commit hooks with case rules).
• Provide writers and engineers with a capitalization preview in PR templates.

5. Train the team

• Run a 20-minute live demo with edge-case exercises.
• Share a cheatsheet with common prepositions and examples across contexts.
• Pair writers and designers to test how headings scan in real layouts.

6. Audit and remediate

• Crawl the site and export headings, nav labels, and UI strings.
• Triage by template (blog, docs, pricing, onboarding).
• Fix in batches; measure before/after metrics (CTR on titles, help success rates, task completion times).

7. Test and iterate

• A/B test capital case vs sentence case on high-traffic pages.
• Compare CTR, dwell time, and scrolldepth for editorial; compare errors and task times for UI.
• Keep the winner as your default and document exceptions.

Edge cases and tricky scenarios

• Prepositions in phrasal verbs: Capitalize if they’re part of a verb (“Log In to Your Account” in Chicago-style Title Case would capitalize Log and Account; for AP, In may be capitalized if treated as part of the verb phrase; document your rule).
• Infinitives and particles: Always capitalize To when it’s the infinitive marker (“How to Train Your Model”).
• Hyphenated compounds: Chicago capitalizes both elements unless an article, preposition, or coordinating conjunction (“End-to-End Encryption”). Many UI teams prefer “End-to-end encryption” in sentence case.
• Brand stylization: Keep iPhone, eBay, YouTube as written. If a headline must start with iPhone, consider “Apple iPhone tips” or restructure the sentence.
• Acronyms and initialisms: Keep them uppercase (API, HTTP/2, OAuth 2.0). Be consistent with versioning.
• Programming identifiers: Don’t force Title Case on code elements (snake_case, camelCase). Use code formatting instead.
• Localization variance: German capitalizes nouns; Spanish and French use sentence case in headings more often. Provide locale-specific guidance for translators.

Accessibility notes you shouldn’t skip

• Avoid ALL CAPS in running text. It impairs word shape recognition and can slow reading, especially for users with dyslexia or low vision. NN/g provides a plain-language summary of these issues.
• CSS text-transform:uppercase doesn’t change the underlying text content, which screen readers typically read as normal words. Still, visual all-caps can strain users; don’t rely on it for emphasis. Prefer weight/size/contrast and clear hierarchy.
• Maintain sufficient contrast and font size. Case alone can’t fix poor typography.

SEO considerations for capital case vs sentence case

• Capitalization is not a direct ranking signal. Google’s systems focus on relevance, helpfulness, freshness, and authority. That said, descriptive, human-friendly titles and headings can raise CTR and reduce pogo-sticking.
• Avoid gimmicks like ALL CAPS or inconsistent casing to “stand out” in SERPs. Google may replace your title link with a better alternative if your chosen text is unhelpful or stylized in a way that hurts clarity.
• For AI Overviews, write self-contained, declarative sentences. Example: “Sentence case capitalizes only the first word of a sentence or heading and proper nouns.” Such crisp statements are more likely to be quoted.

Real-world examples (good, better, best)

• Blog headline

  • Title Case: “5 Ways to Improve Site Speed Without Breaking UX” (good for scannability)
  • Sentence case: “5 ways to improve site speed without breaking UX” (works, but lighter)
  • Best practice: Use Title Case for H1; keep H2/H3 short and descriptive.

• Button label

  • Title Case: “Save Changes” (works but heavier)
  • Sentence case: “Save changes” (preferred; reads faster)

• Error message

  • Title Case: “File Not Found. Please Try Again.”
  • Sentence case: “File not found. Please try again.” (best; conversational)

• Docs heading and step

  • H2 Title Case: “Install the CLI on macOS”
  • Instruction in sentence case: “Open Terminal, then run the installer.”

• Marketing banner

  • Title Case: “Launch Faster With Our New AI Tools”
  • Sentence case subcopy: “Speed up prototyping with automated scaffolds.”

A practical checklist before you publish

• Is the title in Title Case and under 60 characters?
• Are section headings H2/H3 in Title Case and concise?
• Are UI strings and body instructions in sentence case?
• Are brand names styled correctly?
• Did you avoid ALL CAPS for emphasis?
• Do prepositions match your chosen style guide?
• Did you verify localization notes for translated pages?

Step-by-step: Convert any headline from sentence case to Title Case (manually)

1. Capitalize the first and last word.
2. Capitalize nouns, pronouns, verbs (including short verbs like “is”), adjectives, and adverbs.
3. Lowercase articles (a, an, the) and coordinating conjunctions (and, but, or, nor, for, so, yet).
4. Apply your preposition rule (Chicago: lowercase regardless of length; AP/APA: capitalize four letters or more).
5. For hyphenated compounds, capitalize the first element and capitalize the second if it’s a major word; otherwise lowercase.
6. Keep brand stylization intact.
7. Reread for rhythm; shorten long headings—case won’t fix verbosity.

Tooling you can use

• ZenixTools Title Case Converter — Paste your headline and choose AP, Chicago, APA, or Microsoft rules. The preview explains why each word is capitalized.
• ZenixTools Sentence Case Normalizer — Normalize UI strings and flag accidental caps in labels.
• ZenixTools Case Linter for Docs — A CLI and CI step that fails builds when headings or UI strings violate your policy.
• Browser extensions — Add case checks to CMS editors for real-time feedback.

Note: Automated tools can’t resolve every edge case (e.g., phrasal verbs, stressed prepositions). Always do a final human pass.

Common mistakes to avoid

• Mixing Title Case and sentence case in the same component or page.
• Capitalizing Every Word in a sentence case heading.
• Over-capitalizing short prepositions in Title Case when your guide says not to.
• Using ALL CAPS for emphasis instead of typographic hierarchy.
• Inconsistent hyphenation choices (“End-to-end” vs “End-To-End”).
• Ignoring brand stylization or legal capitalization of product names.
• Auto-converting case without reviewing acronyms and proper nouns.
• Forgetting locale-specific capitalization norms in translation.

Best practices we keep at ZenixTools

• Decide the case by intent: guidance (sentence case) vs scannability (Title Case).
• Keep headings short. The longer the line, the less Title Case helps.
• Follow platform norms: Material Design and Microsoft generally prefer sentence case in UI; editorial teams still favor Title Case for headings.
• Measure results, don’t guess. Track CTR for titles and task completion for UI.
• Document exceptions and keep one canonical capitalization policy in your repo wiki.

Frequently Asked Questions

1. Which is better for SEO: capital case or sentence case? Neither capitalization style is a direct ranking factor. What matters is clarity, relevance, and how well your titles set expectations. In our tests, Title Case sometimes lifts CTR for short headlines, but results vary by audience and layout. Write a clear title first, then pick the case that best serves readers.

2. Is “capital case” the same as ALL CAPS? No. In this article, “capital case” means Title Case, where principal words are capitalized. ALL CAPS means every letter is uppercase. ALL CAPS harms readability and should be avoided in running text. Reserve it sparingly for very short labels or abbreviations where space is constrained.

3. Should buttons use Title Case or sentence case? Use sentence case for most UI controls: “Save changes,” “Create project,” “Try again.” It reads faster, matches platform norms, and reduces visual noise. You can use Title Case in marketing-style CTAs if they act like mini headlines, but keep it consistent within each surface.

4. Do prepositions of four letters get capitalized in Title Case? It depends on your style guide. Chicago lowercases prepositions regardless of length unless they’re stressed or part of a phrasal verb. AP and APA capitalize words of four letters or more, including four-letter prepositions like With and From. Pick one rule and document it.

5. How should I handle hyphenated words in titles? Capitalize the first element. Capitalize the second element if it’s a major word (noun, verb, adjective, adverb). Lowercase it if it’s an article, preposition, or coordinating conjunction. Example: “End-to-End Encryption,” “Know-How,” but “State-of-the-art methods” (opinions vary; document your rule).

6. What about brand names like iPhone or YouTube? Honor the brand’s stylization everywhere. Avoid starting sentences or headings with a lowercase brand; rewrite instead (“Apple iPhone tips” or restructure the sentence). Never force Title Case onto brand names with internal capitalization (YouTube, eBay) unless legally required otherwise.

7. Does capitalization affect accessibility? Mixed case (Title Case or sentence case) is generally accessible. ALL CAPS can hurt readability due to uniform word shapes. Ensure adequate contrast, size, and spacing. Don’t rely on case alone for emphasis—use headings, weight, and layout. Screen readers read text based on characters, not visual case.

Balanced limitations and caveats

• Case choice can’t rescue vague headings. Clarity and specificity come first.
• Tools mis-handle edge cases; rely on human review for phrasal verbs and stylized brands.
• Effects vary by audience, platform, and layout density. Always test locally.

Conclusion and next steps

Pick one policy, teach it, and automate it. Use Title Case for short, scannable headings and navigation. Use sentence case for UI and instructional text. Measure the impact, especially when testing capital case vs sentence case across templates.

Try these free resources from ZenixTools:

• Title Case Converter (AP/Chicago/APA/Microsoft modes)
• Sentence Case Normalizer for UI writers
• Case Linter for Docs (CI/CLI)

If you’re standardizing a large site, our team can help you audit headings and ship a capitalization policy your designers and writers actually use.

---

References

• Google Search Central — About title links in search results: https://developers.google.com/search/docs/appearance/title-link
• W3C WAI — Cognitive Accessibility Design Patterns: https://www.w3.org/WAI/WCAG2/supplemental/#coga-dp
• Microsoft Writing Style Guide — Capitalization: https://learn.microsoft.com/style-guide/capitalization
• Nielsen Norman Group — All-Caps and Readability: https://www.nngroup.com/articles/uppercase-readability/
• MDN — text-transform: https://developer.mozilla.org/docs/Web/CSS/text-transform