Title Case vs Sentence Case: Which to Use and When

Capitalization looks trivial until you’re staring at a heading wondering which words to capitalize. Here are the common styles, when each fits, and how to switch between them instantly.

Our own tool gets this “wrong”, and that is the lesson. Running the lord of the rings: return of the king through our case converter gives:

Title Case     The Lord Of The Rings: Return Of The King
Sentence case  The lord of the rings: return of the king

Look at the Title Case line: “Of” and “The” are capitalised. That is naive title case — capitalise every word. Chicago and AP keep short prepositions and articles lowercase, so an editor writes “The Lord of the Rings”. Sentence case has no such ambiguity, which is exactly why many style guides now prefer it for headings: there is nothing to get wrong.

The main styles

• Title Case — Capitalize The Major Words (nouns, verbs, adjectives), lowercase short words like a, the, of, and. Used for titles and headlines, especially in US editorial styles.
• Sentence case — Only the first word and proper nouns are capitalized. Increasingly the default for headings and UI because it reads naturally and is easier to get consistent.
• UPPERCASE — All caps. For short labels, acronyms or emphasis — but hard to read in long runs.
• lowercase — All small. A deliberate stylistic choice for a casual, modern tone.

Four inputs through our own case converter, so the difference is output rather than description:

Input	UPPER	Title	Sentence	lower
the lord of the rings	THE LORD OF THE RINGS	The Lord Of The Rings	The lord of the rings	the lord of the rings
HTTP response code	HTTP RESPONSE CODE	Http Response Code	Http response code	http response code
iPhone 15 Pro Max	IPHONE 15 PRO MAX	Iphone 15 Pro Max	Iphone 15 pro max	iphone 15 pro max
XMLHttpRequest	XMLHTTPREQUEST	Xmlhttprequest	Xmlhttprequest	xmlhttprequest

Which should you use?

• Blog/article titles: Title Case (traditional) or Sentence case (modern, cleaner). Pick one and be consistent site-wide.
• UI labels, buttons, form fields: Sentence case — it’s friendlier and easier to maintain.
• Navigation, tags: Title Case or sentence case; avoid ALL CAPS for anything long.

The golden rule is consistency: pick a style per context and apply it everywhere.

Watch out for

• Proper nouns always keep their capitals (iPhone, GitHub, Taiwan).
• Title-case rules vary by style guide (AP vs Chicago) on which small words to capitalize — automated title case gets you 95% there; eyeball the rest.

Two of those rows are the caveat you should know before trusting any tool with a headline. the lord of the rings becomes The Lord Of The Rings — every word capitalised, including of and the, because our converter applies the mechanical rule rather than a style guide’s small-word list. And iPhone 15 Pro Max becomes Iphone 15 Pro Max: the lower-case i that the brand depends on is gone. Sentence case handles the first correctly (The lord of the rings) and would mangle the second the same way. Proper nouns and brand casing are the one thing no mechanical rule can recover, so check those by eye.

Convert in one click

• Case converter — switch text between Title Case, Sentence case, UPPERCASE and lowercase instantly, in your browser.
• Counting words or characters for a headline limit? Word counter.

Pick a style, run it through the converter, and your headings and labels stay clean and consistent.

AP vs Chicago: the small-word rules

Both capitalize the important words; they disagree on the little ones.

• AP style capitalizes any word of four letters or more, including prepositions like Over, With and From. It lowercases short articles, conjunctions and prepositions (a, an, the, and, but, or, for, nor, to).
• Chicago style lowercases all prepositions regardless of length, plus articles and coordinating conjunctions. So a four-letter preposition stays small.

The classic tell is a word like over:

AP:      The Cat Jumps Over the Wall
Chicago: The Cat Jumps over the Wall

Both always capitalize the first and last word of the title, no matter what.

The other “cases” — in code

In programming, “case” describes how you join words in an identifier, and each ecosystem has a favorite:

• camelCase — variables and functions (JavaScript, Java)
• PascalCase — classes, types, React components
• snake_case — Python variables, database columns
• kebab-case — URLs, CSS classes, file names
• SCREAMING_SNAKE_CASE — constants

These aren’t style preferences like prose casing — mixing them up can break code. See naming conventions in code for when to use each.

The same limitation shows up harder in code identifiers. XMLHttpRequest came back as Xmlhttprequest — our converter splits on case transitions, and a run of capitals like XMLH reads as a single token, so the internal word boundaries are lost. That is worth knowing rather than working around: any acronym-heavy identifier should be re-cased by hand.

Quick reference

Where	Use
Blog/article title	Title Case or Sentence case (pick one)
Section subheads	Sentence case
Buttons, form labels	Sentence case
Nav items, tags	Title Case or Sentence case
Code identifiers	camelCase / snake_case, per language

FAQ

Is title case wrong now?

No — it’s still standard in US publications and many blogs. Sentence case is simply more common in product UI, where it feels friendlier and is easier to keep consistent.

What do big tech sites use?

Apple, Google and most modern design systems default to sentence case for headings and interface text. It reduces the “which word gets a capital?” guesswork.