Convert Text to Capitalized Case

Convert text to Capitalized Case: each word starts uppercase, rest lowercase. Ideal for proper nouns, product names, and formatted display text.

ZERO UPLOAD · ALL LOCAL
  1. Type or paste text into the input box — all 14 conversions appear instantly.
  2. The Character Case Formats section shows 5 character-level transformations.
  3. The Word Case Formats section shows 9 word-level transformations.
  4. Use the Copy buttons to grab any individual result.
  5. Click "Use as input" to chain conversions (e.g. snake_case → camelCase → kebab-case).

Worked examples for this use case

snake_case database fields → display labels

Before
first_name
last_name
created_at
phone_number
After
First Name
Last Name
Created At
Phone Number

lowercase tag names → formatted category labels

Before
user authentication
payment processing
order management
After
User Authentication
Payment Processing
Order Management

INPUT TEXT

CHARACTER CASE FORMATS

lower case
UPPER CASE
Capitalized Case
aLtErNaTiNg cAsE
InVeRsE CaSe

WORD CASE FORMATS

camelCase
PascalCase
snake_case
SCREAMING_SNAKE
kebab-case
dot.case
path/case
sentence case
Title Case

Capitalized Case Converter,Capitalize Every Word

When every word needs equal visual weight, Capitalized Case gives you a simple rule. It makes every word start with an uppercase letter and lowercases the rest, which fits proper nouns in prose, product names in documentation, and formatted display text.

Capitalized Case differs from Title Case only in the treatment of the existing characters: Title Case on this tool produces the same result because both capitalize every word. The distinction matters in word processors that implement style-specific rules for articles and prepositions, but this tool applies simple word-boundary logic to all words for product labels and prose terms alike.

Where Capitalized Case is used

Product names in documentation and marketing copy use Capitalized Case: "User Authentication Service", "Payment Gateway Integration". Proper noun phrases in prose require it: "New York City", "North Atlantic Treaty Organization". Navigation labels in legacy software and some enterprise applications use Capitalized Case rather than the Sentence case preferred in modern design systems.1 Building on this, database column display names (as opposed to identifiers) often use Capitalized Case in admin UIs.2 Salesforce, HubSpot, and Airtable all use Capitalized Case for field labels throughout their interfaces,3 so when you build integrations that map database fields to these platforms, the display names should follow the same pattern. Academic reference lists in APA and Chicago styles use Capitalized Case for article and book titles,4 making this the expected format for bibliography entries in research software and citation management tools.

Edge cases: apostrophes, hyphens, and acronyms

Apostrophes in contractions and possessives do not start a new word: "it's" stays "It's" (not "It'S"). Hyphenated words are treated as two words: "well-known" becomes "Well-Known". Acronyms already in UPPERCASE (like "API") get converted to "Api" because the splitter sees each uppercase letter as a potential word boundary, then applies capitalize logic. Consequently, for strings containing acronyms, review the output before use. Mixed-case inputs that already follow Capitalized Case, like "UserProfile", are preserved correctly because the converter detects existing word boundaries and rebuilds the same form. Single-character words like "a" and "i" capitalize to "A" and "I", which is correct for display text. Leading or trailing whitespace is trimmed before processing, so accidental spaces in pasted input do not produce unexpected results.

Workflow: formatting product name lists for documentation

Building on this, here is a common use: when writing feature lists or product category names in documentation, paste a list of raw lowercase or snake_case identifiers, convert to Capitalized Case, and copy the display names directly into your Markdown or HTML. CapyToolkit processes each line independently, so 30 product names convert in one pass. You get display-ready text without manually fixing each word's capitalization. For API documentation generated from OpenAPI specs, the summary and description fields often start as camelCase method names. Converting those to Capitalized Case before writing them into the spec produces human-readable endpoint descriptions in the generated docs without a separate formatting pass. When the API surface grows to hundreds of endpoints, this batch conversion saves hours of manual editing.

Formatting database column names as display labels in admin UIs

Admin dashboards and data tables need human-readable column headers. Database column names are snake_case by convention, but display labels in a grid or report need to be readable to non-technical users. Converting them in batch is faster than writing each label manually. Building a consistent display-label convention into your admin tooling from the start prevents the drift where every new column gets a hand-typed label that does not match the rest of the interface.

snake_case fields to display-ready strings

Paste a list of column names from your schema (first_name, created_at, is_email_verified) and copy the Capitalized Case output (First Name, Created At, Is Email Verified). Those are display-ready labels for a schema column, so use them as headers in your admin table, CSV export, or PDF report. CapyToolkit processes each line independently, so a 30-column schema converts in one pass. The result is display-ready copy without manual label writing.

A consistent display-label convention also helps downstream report generators and exporters. When the same column renders as "First Name" in a grid and as "first_name" in a CSV, analysts lose trust in the export. Running every schema column through this converter once, before the report template is built, guarantees that the grid header and the exported file use the same words. The Microsoft Power Apps guidance for column display names points in the same direction: readable labels beat raw identifiers wherever a non-technical user sees the data.

Matching display label conventions in enterprise software integrations

Enterprise tools like Salesforce, HubSpot, and Airtable use Capitalized Case for field labels throughout their interfaces. If you are building an integration or import tool that maps database fields to these platforms, using Capitalized Case for the mapped field display names creates visual consistency between your output and the target platform's existing UI. Users see labels that match the pattern they already recognize.

Capitalized Case versus Title Case in word processors and CMS tools

Capitalized Case and Title Case produce visually similar results, but they differ in one important way: Capitalized Case capitalizes every word without exception, while full Title Case implementations in style-guide-compliant tools lowercase articles and short prepositions. Knowing which rule applies to your context prevents output that looks correct on short phrases but breaks on longer ones.

Which to use when your CMS offers both options

If your CMS or word processor has a "Capitalize" option, it likely applies Capitalized Case (every word, no exceptions). An explicit "Title Case" option may apply Chicago or APA rules, lowercasing words like "of", "in", "the", and "a".5 For most display text in web UIs and data tables, Capitalized Case is what you actually want because the exceptions in APA and Chicago style only matter in formal publishing contexts. CapyToolkit's Capitalized Case converter applies the simpler, more predictable rule, making it the right choice for product copy and data labels.

When to use this

Use this when formatting product names, proper noun phrases, database column display labels, or navigation items that should have every word capitalized.

Examples

snake_case database fields → display labels

Before
first_name
last_name
created_at
phone_number
After
First Name
Last Name
Created At
Phone Number

lowercase tag names → formatted category labels

Before
user authentication
payment processing
order management
After
User Authentication
Payment Processing
Order Management
Sources
  1. 1.

    "Capitalization," Microsoft Style Guide, learn.microsoft.com, accessed June 2026. https://learn.microsoft.com/en-us/style-guide/capitalization

  2. 2.

    "Column Display Names," Microsoft Power Apps, learn.microsoft.com, accessed June 2026. https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/work-with-data-cube

  3. 3.

    Salesforce, "Object Reference," developer.salesforce.com, accessed June 2026. https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/

  4. 4.

    "The Chicago Manual of Style Online," chicagomanualofstyle.org, accessed June 2026. https://www.chicagomanualofstyle.org/home.html

  5. 5.

    "APA Style: Title Case Capitalization," apastyle.apa.org, accessed June 2026. https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case

FAQ