How to Convert a Heading to Sentence Case Without Losing Names

An all-capital heading can contain several kinds of text: ordinary words, a product name, and an acronym. Converting everything to lowercase fixes the shouting but can turn WordPress into wordpress and API into api. Use automatic sentence case as a first pass, then restore the spellings that carry meaning.

Decide which heading style you need

Sentence case usually capitalizes the first word while keeping ordinary words lowercase. Proper names and established abbreviations retain their correct capitalization. The Microsoft capitalization guide uses this approach for headings and makes exceptions for brand, product, and service names.

Choose the convention required by your publication before converting a batch. A heading such as Set up WordPress for iPhone API tests follows sentence case; it does not become Set Up WordPress for iPhone API Tests. Neither version changes what the page promises. This is an editing decision, not a ranking technique.

Convert the ordinary words first

1. Keep a copy of the original heading in your document. Write down names and abbreviations you need to preserve, such as WordPress, iPhone, and API.
2. Open the Case Converter and paste the heading into Your text. Put separate headings on separate lines.
3. Select Sentence case. Read the Result before copying it. This mode lowercases the text, then capitalizes at certain sentence boundaries; it does not recognize brands.
4. Choose Copy result, paste into your document or website editor, and restore the names there. The result area itself is not an editing field.

A complete before-and-after example

Here is an original practice heading and the two separate stages of correction:

Original:
SET UP WORDPRESS FOR IPHONE API TESTS

Automatic result:
Set up wordpress for iphone api tests

Manually corrected heading:
Set up WordPress for iPhone API tests

Notice that for and tests stay lowercase. Only the product spellings and abbreviation need restoring. Review the corrected text against your saved original so a capitalization change does not accidentally become a wording change.

Review colons, hyphens, and sentence boundaries

The tool preserves line breaks and processes each line separately. In Sentence case, it capitalizes a letter at the start of a line and after a full stop, question mark, or exclamation mark followed by whitespace. It also restores standalone I. Those rules are mechanical: punctuation in an abbreviation or quoted text can still need a manual check.

For a heading with a colon, both Microsoft and the Google developer capitalization guide capitalize the first word of the subheading. The converter does not apply that colon rule. For example, CHECK SEO: FIX API ERRORS becomes Check seo: fix api errors; revise it to Check SEO: Fix API errors.

Google also recommends capitalizing only the first part of an ordinary hyphenated word at the start of a heading. Thus MOBILE-FIRST WORDPRESS GUIDE can become Mobile-first WordPress guide after restoring the product name. Do not capitalize First merely because it follows a hyphen.

Protect text that must keep its exact spelling

Leave URLs, filenames, command names, and code identifiers out of a batch conversion. For example, getUserID is a code spelling, not a heading word to normalize. Convert the surrounding prose separately and insert the identifier unchanged.

Do not switch to Title Case just to rescue acronyms in an all-capital heading. This tool preserves tokens already written entirely in capitals in that mode, so ordinary all-capital words can remain uppercase too. It also cannot infer the internal capitals in iPhone or WordPress.

Make the final corrections in your destination editor. Editing the input while Sentence case is selected recalculates the result, and Send result back to the box runs the selected conversion again. Either action can lowercase a name you just restored.

Check the whole set before publishing

Read the headings together in their final location. The Google guide to headings and titles recommends descriptive headings that help readers navigate. Consistent capitalization helps your editorial presentation, but a vague heading still needs clearer wording.

• Check every product, person, place, and acronym against its intended spelling.
• Review headings beginning with a quotation mark, a number, or spaces; the initial-letter rule may not handle them as you expect.
• Apply the same colon and hyphen convention throughout the page.
• Compare your original and edited versions using this draft comparison workflow when processing several headings.
• If your submission also has a word limit, check the final text with the Word Counter after completing the edits.

Copy the reviewed version into the page title or heading field and preview it once more. That final read is where you catch a misplaced capital, a lost name, or a heading that no longer matches the section underneath.