How to instantly convert all caps to AP style title case for blog articles without breaking proper nouns

ALL CAPS HEADLINE GRABS ATTENTION BUT DESTROYS READABILITY vs. AP Style Title Case That Balances Impact With Professionalism

I've been editing blog submissions for over nine years. Last Tuesday alone, I processed 34 contributor drafts. Seventeen of them arrived with headlines screaming in all caps — stuff like "HOW TO USE GOOGLE ANALYTICS TO TRACK CONVERSIONS IN 2024." The writers thought uppercase conveyed urgency. In reality, it made their headlines look like spam emails from 2003.

Here's what happens when I run that same headline through a proper case converter tuned for AP style title case: "How to Use Google Analytics to Track Conversions in 2024." Same words. Same meaning. But now it reads like it belongs on a legitimate publication. The difference isn't subtle — it's the difference between a reader clicking through or bouncing.

But there's a trap hiding in that conversion. Most online title case converters will hand you "How To Use Google Analytics To Track Conversions In 2024." Notice the capitalized "To" and "In"? That's wrong. AP style lowercase specific short words. And worse — some converters will mangle proper nouns, giving you "Google analytics" instead of "Google Analytics." One wrong click and your headline looks amateurish.

Let me walk you through how I convert all-caps headlines to clean AP style title case without breaking a single proper noun. I've refined this workflow across thousands of submissions, and it saves me roughly 12 minutes per editing session. That adds up to about 5 hours saved every month.

The Wrong Way vs. The Right Way: What Most Case Converters Get Wrong

Wrong: Blind Capitalization That Ignores AP Rules

Most free title case converter tools apply a simple rule: capitalize the first letter of every word. That's it. No logic. No awareness of AP style guidelines. Run "APPLE UNVEILS NEW IPHONE PRO MAX WITH AI FEATURES" through one of these tools and you'll get "Apple Unveils New Iphone Pro Max With Ai Features."

Three problems jump out immediately:

• "Iphone" should be "iPhone" — Apple's branding uses a lowercase "p"
• "With" should be lowercase per AP style — it's a preposition
• "Ai" should be "AI" — it's an acronym, not a word

The headline went from one problem (all caps) to three new problems (broken proper noun, wrong preposition capitalization, mangled acronym). You traded a sledgehammer for a scalpel that keeps slipping.

Right: AP-Aware Conversion With Proper Noun Protection

The correct output should read: "Apple Unveils New iPhone Pro Max With AI Features." Wait — actually, in AP style, "with" stays lowercase. So the final version is: "Apple Unveils New iPhone Pro Max with AI Features."

That's what a proper AP style title case conversion looks like. Short conjunctions and prepositions stay lowercase. Acronyms stay uppercase. Branded proper nouns retain their original capitalization. The headline now meets publication standards on the first pass.

AP Style Title Case Rules: The Short List You Actually Need

I keep a cheat sheet taped to my monitor. After nine years, I still reference it. AP style title case follows specific rules, and once you internalize them, you'll spot conversion errors instantly.

Capitalize These Words

• The first word in the headline — always, even if it's "the"
• The last word — always, even if it's a preposition
• All nouns, pronouns, adjectives, verbs, adverbs
• Subordinating conjunctions (because, although, if, when)

Lowercase These Words (Unless They're First or Last)

• Articles: a, an, the
• Coordinating conjunctions: and, but, or, for, nor
• Prepositions with three or fewer letters: in, on, at, to, of, by, for, up

Here's where most capitalization converter tools fail: they treat four-letter prepositions inconsistently. AP style lowercases prepositions of three letters or fewer. "With" has four letters, so some editors lowercase it and others don't. The AP Stylebook itself has evolved on this — currently, AP lowercases all prepositions regardless of length in titles. But many publications still follow the three-letter rule as a house style adaptation.

My recommendation? Pick one approach, document it in your style guide, and stick with it. Consistency matters more than which side of the debate you land on.

Proper Noun Protection: Where Every Case Converter Falls Short

This is the section I wish someone had handed me six years ago. I once published a blog post with "McDonalds" instead of "McDonald's" and "Iphone" instead of "iPhone" in the same headline. The author emailed me within an hour. That was embarrassing enough to change my entire workflow.

The Proper Noun Problem

Standard text case conversion tools don't understand brand names. They treat every word equally — apply a rule, move on. But proper nouns follow their own capitalization rules:

• iPhone, iPad, iMac — lowercase "i," uppercase second letter
• McDonald's — capital "M," lowercase "c," capital "D," apostrophe
• YouTube — capital "Y," capital "T" in the middle
• LinkedIn — capital "L," capital "I" in the middle
• eBay — lowercase "e," capital "B"
• GitHub — capital "G," capital "H"

No automated tool handles all of these perfectly. Some maintain databases of common brand names. Others let you create custom exception lists. The best ones do both.

My Proper Noun Protection Workflow

Here's what I do for every single headline conversion:

Step 1: Run the all-caps headline through a case converter that supports AP style rules. This gets me 80% of the way there.

Step 2: Scan the output for brand names, product names, and acronyms. I keep a running list of the ones that appear most frequently in my niche. For a tech blog, that list includes about 40 entries — iPhone, GitHub, YouTube, macOS, iOS, PayPal, WhatsApp, and so on.

Step 3: Manually verify each proper noun's capitalization against the brand's official style. Yes, manually. It takes 15 seconds per headline. That's time well spent.

Step 4: Check acronyms. AI, HTML, CSS, API, SEO, ROI — these should stay fully uppercase. A naive converter might give you "Ai" or "Html." Fix them.

Step 5: Read the headline aloud. Your ear catches what your eyes miss. If something sounds off, it probably looks off to readers too.

Building a Conversion Workflow That Actually Scales

Processing 30+ headlines per week means I need a system that's fast but not sloppy. Here's the exact workflow I use, refined over years of trial and error.

The 90-Second Headline Conversion System

On average, I spend about 90 seconds converting and verifying each headline. Here's the breakdown:

• 15 seconds: Paste the all-caps headline into the title case converter and run AP style conversion
• 20 seconds: Scan for proper nouns and brand names against my mental checklist
• 15 seconds: Verify acronym capitalization
• 20 seconds: Confirm prepositions and articles follow AP rules
• 20 seconds: Read aloud and final visual check

That's 90 seconds per headline. For 30 headlines, that's 45 minutes total. Compare that to the old days when I'd manually retype each headline — that took 3-4 minutes per headline, or nearly two hours for the same batch. The case converter cut my time by more than half.

Batch Processing Without Losing Quality

When I'm processing a batch of submissions, I convert all headlines first, then do a single proper-noun pass across all of them. This lets me get into a rhythm. My brain shifts from "conversion mode" to "verification mode" rather than context-switching for every single headline.

Here's a real example from last month. I received 28 headlines in all caps. After batch conversion, I found 11 proper noun errors, 6 acronym issues, and 4 preposition capitalization mistakes. Total fix time: 14 minutes. Had I not used the systematic approach, I would have missed at least half of those errors — and published headlines with "Iphone," "Seo," and "With" incorrectly capitalized.

Common Mistakes I Still See (And How to Fix Them)

Mistake 1: Trusting the First Output Blindly

Bad headline: "HOW TO OPTIMIZE YOUR WORDPRESS SITE FOR SEO IN 2024"

Naive conversion: "How To Optimize Your WordPress Site For Seo In 2024"

Correct AP version: "How to Optimize Your WordPress Site for SEO in 2024"

The naive version capitalized "To," "For," and "In" (all should be lowercase in AP style) and lowercased "SEO" to "Seo." Three errors from a single headline.

Mistake 2: Forgetting Hyphenated Words

Bad headline: "THE ULTIMATE GUIDE TO SEO-FRIENDLY CONTENT MARKETING"

Naive conversion: "The Ultimate Guide to Seo-friendly Content Marketing"

Correct AP version: "The Ultimate Guide to SEO-Friendly Content Marketing"

AP style capitalizes both parts of a hyphenated compound in titles. "SEO-Friendly," not "Seo-friendly." And the acronym stays uppercase.

Mistake 3: Mishandling Colons and Em Dashes

Bad headline: "CONTENT MARKETING 101: HOW TO WRITE BLOG POSTS THAT CONVERT"

Naive conversion: "Content Marketing 101: How To Write Blog Posts That Convert"

Correct AP version: "Content Marketing 101: How to Write Blog Posts That Convert"

After a colon, the first word is capitalized — that part most converters get right. But "To" after "How" should be lowercase. The conversion tool treated "How To" as a unit and capitalized both.

The Bottom Line for Blog Editors

Converting all-caps headlines to AP style title case isn't complicated, but it requires attention to detail that most automated tools skip. The process breaks down into three phases: convert with an AP-aware tool, verify proper nouns and acronyms manually, and read the final headline aloud to catch anything you missed.

The writers submitting all-caps headlines aren't being lazy — they just don't know better. Your job as an editor is to transform their raw input into polished, publication-ready headlines without introducing new errors. A reliable case converter gets you 80% of the way there. Your eyes and ears handle the remaining 20%.

Ninety seconds per headline. A running list of proper nouns in your niche. A habit of reading aloud. That's the system that's kept my publication's headlines clean for years — and it'll work for yours too.