Title case vs sentence case — which to use for headings

Anyone writing headings, titles, or navigation labels eventually runs into the same small but persistent decision: should every major word be capitalized, or just the first word and proper nouns? The two options — title case and sentence case — look similar at a glance but read differently, and mixing them inconsistently across a site or document is one of the more noticeable small polish issues a reader picks up on, even if they can’t name what’s off.

Neither style is objectively correct. Both are widely used, and the right choice depends on tone, platform conventions, and consistency with whatever else you’ve already published. This guide breaks down exactly how each style works, where each tends to fit best, and how to apply either one consistently.

What title case actually means

Title case capitalizes most major words in a heading, while typically leaving small connecting words lowercase unless they start or end the phrase. A typical title case rule set looks like this:

• Capitalize nouns, pronouns, verbs, adjectives, and adverbs.
• Lowercase short articles (a, an, the), coordinating conjunctions (and, but, or), and short prepositions (in, on, of) — unless one of them is the first or last word.
• Always capitalize the first and last word of the title, regardless of what part of speech it is.

Example: “How to Get a Color Palette From Any Photo” — note that “From” is capitalized here because style guides vary on preposition length thresholds, which is exactly why title case can feel inconsistent without a clear rule to follow.

What sentence case actually means

Sentence case is simpler: capitalize only the first word (and any proper nouns), exactly as you would in a normal sentence.

Example: “How to get a color palette from any photo” — only “How” is capitalized, matching ordinary sentence structure.

Because it mirrors regular writing, sentence case tends to look calmer and less formal than title case, which is part of why it’s become the default style across a lot of modern web content, software interfaces, and documentation.

Side-by-side comparison

	Title case	Sentence case
Feel	Formal, traditional	Casual, modern
Common in	Books, print headlines, some news sites	Blog posts, software UI, documentation
Capitalization rule	Most major words capitalized	Only first word and proper nouns
Consistency risk	Higher — rules for short words vary by style guide	Lower — matches normal sentence writing
Reading pace	Can feel visually “busier”	Reads more smoothly, closer to natural text

When title case tends to fit better

Title case still suits contexts where a more formal, traditional tone is expected — print publications, certain types of book titles, formal reports, or brand contexts that have always used it. If an existing style guide, publication, or brand already uses title case consistently, switching to sentence case for just a subset of content would create more inconsistency than it solves.

When sentence case tends to fit better

Sentence case has become the more common default for web content, particularly blog headings, product interfaces, and documentation, largely because it’s easier to apply consistently — there’s no need to memorize which short words get capitalized and which don’t. It also tends to read a little faster, since it matches the capitalization pattern readers already process automatically in regular sentences.

Software interfaces have shifted heavily toward sentence case for buttons, menu labels, and headings in recent years, which has reinforced it as a familiar, modern default for a lot of readers.

Picking one and sticking with it

The most important factor isn’t which style you choose — it’s applying it consistently across every heading, title, and label in a given piece of content or site. A page that mixes both styles across different headings looks unintentional rather than stylistically deliberate.

A simple approach:

1. Check whether an existing style guide or brand standard already specifies one.
2. If not, default to sentence case for most web content, since it’s easier to apply consistently at scale.
3. Reserve title case for contexts where formality or an existing convention calls for it.
4. Apply the chosen style to every heading level — H1, H2, H3 — not just the page title.

Converting existing text between styles

Manually rewriting the capitalization of dozens of existing headings is tedious and error-prone, especially with title case’s exceptions for short words. A case converter can switch a batch of text between title case, sentence case, and other common formats in seconds, which is useful when standardizing an inconsistent set of headings across an older site or document.

If you’re revisiting heading length at the same time as capitalization style, it’s worth checking word count too — see the guide on how long a blog post should be for related guidance, and a word counter for a quick check on headline or meta title length specifically.

Common mistakes when switching styles

Moving an existing site or document from one capitalization style to the other is more error-prone than it looks, mostly because of a handful of recurring mistakes:

• Missing proper nouns. Sentence case still capitalizes proper nouns — brand names, place names, product names — so a blanket “lowercase everything except the first word” pass will incorrectly lowercase names that should stay capitalized.
• Inconsistent short-word handling in title case. Different title case style guides disagree on exactly which short words stay lowercase and how long a word needs to be to count as “short,” which is a common source of visible inconsistency across a site that wasn’t converted with one consistent rule set.
• Forgetting acronyms. Both styles keep acronyms fully capitalized (like “SEO” or “PDF”) regardless of where they fall in a heading — a naive case converter that doesn’t account for this can incorrectly alter them.
• Applying the change inconsistently across content types. It’s easy to update page titles and forget email subject lines, button labels, or navigation menus, leaving a site with two different capitalization conventions depending on which part of it you’re looking at.

Reviewing a sample of converted headings by eye after using any automated tool is worth the extra few minutes, specifically to catch proper nouns and acronyms that a general-purpose conversion might miss.

Does the choice vary by language or region?

Capitalization conventions aren’t universal across languages. Many languages other than English don’t use mid-sentence capitalization for common nouns at all, which makes the entire title case vs. sentence case debate somewhat English-specific (and applicable to a handful of other languages with similar capitalization habits). If a site or document is multilingual, it’s worth confirming what convention is standard for each language rather than assuming the English-language rule automatically transfers.

FAQ

Which style is better for search engine results? Neither style has a meaningful direct effect on search ranking. Clarity and relevance of the heading text matter far more than capitalization style.

Should I capitalize “vs” in a title case heading? Style guides vary here, but treating “vs” as a short word (lowercase, unless it’s the first or last word) is a common convention.

Do H2 and H3 headings need the same capitalization style as the main title? Yes, consistency across every heading level is what makes the style choice look intentional rather than accidental.

Is sentence case less professional than title case? No, sentence case is now standard across a wide range of professional software, documentation, and publications — it reads as modern rather than informal.

Summary

Title case and sentence case are both valid, and the choice comes down to tone and consistency rather than one being objectively correct. Sentence case has become the more common default for web content because it’s easier to apply consistently and reads a little faster, while title case still suits more formal or traditional contexts. Whichever you choose, apply it across every heading — and use a case converter to fix any existing inconsistency quickly rather than rewriting headings by hand.