Title Case, Sentence Case, and Text Case: Which Casing to Use Before Publishing

Key points

What to take from this guide

• Choose casing by where the copy will appear, not by one global preference.
• Title case fits many formal titles, while sentence case is often clearer for UI labels, docs, and plain-language headings.
• Case conversion is mechanical, so review acronyms, names, branded terms, and URLs before publishing.

Guide section

Choose casing by surface

Use title case when a title needs to feel formal or editorial, such as a tool name, article headline, report title, or named resource. Use sentence case when the copy should feel like plain instructions, UI text, documentation, product copy, or a conversational section heading.

Use uppercase lightly for short labels or acronyms. Use lowercase or slug case when the destination expects a machine-readable string, such as a URL slug, filename, tag, or internal identifier.

• Title case: formal titles, named pages, reports, and editorial headings.
• Sentence case: UI labels, help text, documentation, and natural headings.
• Uppercase: short labels, acronyms, or controlled emphasis.
• Slug case: lowercase hyphenated URLs, filenames, and shareable page paths.

Guide section

A practical casing workflow

Start by naming the surface. A public article title, a button label, a profile bio, and a URL slug do not need the same casing even when they use the same words.

Convert the draft into the likely formats, then review them side by side. The right choice is the one that stays readable, matches the surface, and does not damage names, acronyms, or brand terms.

• Write the phrase in plain words first.
• Convert it to title case and sentence case.
• Generate the slug preview if the phrase will become a URL.
• Check character count if the field has a limit.
• Manually restore acronyms, names, and house style before publishing.

Guide section

Worked example

Suppose the rough phrase is: free CALCULATORS that SHOW their work. The words are useful, but the casing is noisy. The next step is not to publish the first converted output everywhere; it is to choose the output that matches each surface.

For an article title, title case works. For a UI heading or help page, sentence case is calmer. For a URL, the slug should be lowercase and hyphenated. All three versions use the same 37-character phrase, but they read differently in context.

• Rough phrase: free CALCULATORS that SHOW their work.
• Article title: Free Calculators That Show Their Work.
• UI heading: Free calculators that show their work.
• URL slug: free-calculators-that-show-their-work.
• Length check: 37 characters before any platform or field limit.

Guide section

Common mistakes

The most common mistake is treating casing as decoration instead of meaning. All caps can feel like shouting, title case can make interface copy feel stiff, and sentence case can make a formal resource title feel too casual if the surrounding system expects title case.

Another mistake is trusting mechanical conversion without review. Acronyms, initials, product names, surnames, trademarks, and intentional brand capitalization can all need manual correction after conversion.

• Using title case for every button, label, and help heading.
• Writing long phrases in uppercase for emphasis.
• Letting converters lowercase acronyms or branded terms.
• Creating URL slugs from clever headlines that hide the page topic.
• Changing a published slug without a redirect plan.

Worked example

One phrase, four publishing surfaces

The same words can be correct in different casing depending on where they appear.