Normalize heading case in two passes: apply one declared rule to ordinary prose, then restore acronyms, product names, and codes from an exception ledger. A converter can produce candidates quickly, but it cannot know that API, iPhone, and Wi-Fi each follow a different naming rule.
Classify the headings before changing any letters
Separate the deck's headings into prose, protected names, and machine-like identifiers before choosing a case rule. Only the prose group should receive a general Title Case or sentence case transformation; protected strings and codes need an explicit decision from their owner.
For example, suppose a slide outline contains API ACCESS FOR iPhone AND WI-FI, Quarterly retention review, and XR-500 RELEASE GATE. They may look like three inconsistent headings, but they contain different kinds of text:
Quarterly retention reviewis ordinary prose and can follow the deck's editorial rule.API,iPhone, andWi-Fihave approved spellings that a generic rule should not redefine.XR-500is a product code, so its letters, digits, and punctuation should be treated as data.
Make the classification on a copy of the outline, not inside the only copy of the presentation. Record the source heading, the intended case rule, and every protected string. If the organization already has a brand guide or product-name registry, that source takes precedence over a converter's output.
The rule must also be specific enough to repeat. “Make it look professional” is not a rule; “use sentence case for explanatory slide headings, preserving approved names and all-caps initialisms” is. A clear sentence lets another editor review the result without guessing what the first editor intended.
See exactly what the converter does to a representative heading
Paste one representative heading into Case Converter before processing the rest. The current page shows uppercase, lowercase, Title Case, Sentence case, camelCase, PascalCase, snake_case, and kebab-case results, and each result can be copied separately.
The tool applies character and word-boundary rules rather than an editorial style guide. Spaces, underscores, hyphens, and a lowercase-to-uppercase transition can split words. With API ACCESS FOR iPhone AND WI-FI, the Title Case result can turn the protected pieces into forms such as Api, I Phone, and Wi Fi. Sentence case lowercases the remainder of the input, so it can also change API and iPhone. This early sample exposes the repair work before it spreads through the deck.
For prose headings, choose the output that matches the declared rule. Do not select camelCase, PascalCase, snake_case, or kebab-case simply because they appear tidy; those forms are usually intended for identifiers, field names, or filenames rather than reader-facing slide titles. The tool does not apply small-word exceptions, understand grammar, or preserve typography such as italics.
Case Converter accepts pasted text only. It cannot open a PowerPoint, Keynote, Google Slides, PDF, or Word file, and it does not edit a slide deck. Copying a candidate back into a working presentation is a separate manual step in the presentation application.
Build the exception ledger before the repetitive pass
Write the exception ledger before converting dozens of headings, because memory is unreliable once similar edits accumulate. Give each protected item one approved spelling and, when useful, a source such as the product page, brand guide, interface screenshot, or engineering registry.
A small ledger for the example might contain:
API— keep as an all-caps initialism.iPhone— preserve the product's internal capital letter.Wi-Fi— preserve the hyphen and both capital letters.XR-500— treat the entire code as immutable.
Include plural and possessive decisions when they appear in headings. If the approved copy says APIs, restoring only API may leave an inconsistent suffix. Also list names whose case carries meaning, such as macOS, YouTube, or a product with an intentionally lowercase first letter.
Do not place secrets in the ledger or in the browser tool. The current converter processes input in the page and does not upload it to ToolboxHub, but copied text enters the system clipboard, where clipboard history, synchronization, extensions, or a shared screen may expose it. Use placeholder values for confidential project codes when the actual spelling is not needed to test the case rule.
Convert the working list and restore exceptions immediately
Process one heading at a time when line breaks identify slides. Paste the source heading, copy the chosen prose candidate, and restore protected strings before moving to the next item. This keeps the source, candidate, and exception decisions close together and reduces the chance of applying a later repair to the wrong slide.
For the sample, an editor might select a sentence-style candidate and then restore API, iPhone, Wi-Fi, and XR-500 from the ledger. Check that the transformation changed only capitalization intended by the prose rule. A hyphen disappearing from Wi-Fi, a digit changing, or a product code splitting into two words is not a cosmetic case edit and should stop the pass.
Avoid pasting a multi-page outline as one block when its newlines carry structure. Some case results rebuild text from detected words, so line and hyphen boundaries may not survive in the form the presentation needs. A one-heading unit also makes it easier to identify which exception caused a problem.
If multiple editors are involved, assign one person to own the rule and exception ledger. Parallel edits without a shared ledger often produce two internally consistent but mutually incompatible versions of the same name.
Approve character changes separately from visual layout
Use Text Diff to inspect a source heading and its corrected version at character level. The expected differences should be explainable by the chosen case rule; protected names, digits, punctuation, and factual wording should remain stable.
Text Diff highlights additions and deletions in two pasted texts. It does not understand which capitalization is approved, and a moved phrase may appear as a deletion plus an addition. Use it as an audit aid, not as proof that a brand name or heading is correct. For a long deck, compare the headings in small batches so an accidental missing line is easy to locate.
After the text pass, put the approved headings into the working deck and review them at the actual presentation size. Capitalization can change word width and line wrapping, while restored product names may be wider than the generic candidate. Check title boxes, mobile or shared-screen previews, agenda links, section dividers, chart labels, and speaker-note references.
As a final inventory check, paste the approved heading-only list into Word Counter and compare its line count with the number of headings you intended to process. The counter cannot verify spelling or slide placement, but an unexpected line-count change can reveal a skipped or merged heading. Keep the untouched deck and the exception ledger until the edited copy has been reviewed.
Frequently asked questions
Does Title Case preserve acronyms such as API and URL?
No. The current converter treats detected pieces as ordinary words for its Title Case output, so an acronym can become Api or Url. Restore approved initialisms from an exception ledger.
Can I paste an entire slide deck into Case Converter?
No. The tool accepts pasted text and produces case variants; it cannot open or edit presentation files. Process a heading list or individual heading in a working copy, then update the deck in its original application.
Which output should I use for slide headings?
Use the output that matches the deck's declared editorial rule. Sentence case and Title Case are candidates for prose; camelCase, snake_case, and kebab-case are generally identifier formats, not automatic choices for display text.
Is Text Diff enough to approve product-name spelling?
No. It can show which characters changed, but it does not know the authorized spelling. Compare protected names with a brand guide, product registry, or another approved first-party source.
What should I do when case changes alter a line break?
Review the heading in the actual slide layout. Adjust the text box or approved wording without changing protected names, and keep the original deck until the visual and editorial reviews are complete.