PascalCase Converter

PascalCase converter: class names, components, and types

PascalCase capitalizes the first letter of every word and removes spaces: UserProfile, OrderLineItem, HttpResponseCode. It is the default for C# classes, Java types, React components, and many API model names. This tool turns plain English, snake_case columns, or camelCase labels into consistent PascalCase tokens.

Paste a product feature name, database table label, or component title and copy the result into your codebase. For variables and object properties, use camelCase instead; for URL segments and CSS classes, use kebab-case.

How to use this converter

1. Enter a phrase, label, or identifier—spaces, hyphens, underscores, and mixed capitals all work as input.
2. Read the PascalCase output and check acronyms (API, HTTP) against your team style guide.
3. Copy the token into a class, React component, type definition, or exported symbol.

Before and after examples

Review acronyms and product names against your team style guide.

When should you use PascalCase?

Use PascalCase for types, classes, React/Vue components, C# and Java public types, and enum names in many codebases. It signals “this is a noun you instantiate or import,” not a variable holding data.

Do not use PascalCase for JavaScript variables, JSON properties, URL slugs, or SQL column names—those layers have their own conventions. When a designer hands you a Title Case frame label, convert only the symbol name, not the visible marketing copy.

What PascalCase is (and how it differs from camelCase)

camelCase starts lowercase (userProfileId); PascalCase starts uppercase (UserProfileId). Both glue words without separators. TypeScript and C# linters often enforce PascalCase for public types and camelCase for fields—mixing them signals unfamiliarity with the ecosystem.

Brand names and acronyms need a manual pass: “API Gateway” might become ApiGateway or APIGateway depending on your style guide. The converter applies mechanical rules; your team doc wins on edge cases.

React, Vue, and UI component names

React function components are conventionally PascalCase: UserCard, SettingsPanel, CheckoutForm. File names often match (UserCard.tsx). When designers label frames “user card” in Figma, run the label through this tool before scaffolding the component.

Storybook titles and design-system exports benefit from one spelling. If marketing copy uses Title Case headlines, convert the feature name—not the whole sentence—to PascalCase for the code symbol.

C#, Java, and enterprise APIs

C# namespaces and classes use PascalCase by convention. Java public classes follow the same pattern. OpenAPI generators often emit PascalCase model names even when JSON properties stay camelCase—know which layer you are naming.

When importing legacy ALL CAPS constants from mainframes or spreadsheets, lowercase first if needed, then PascalCase for new type names while keeping CONSTANT_CASE for true env vars.

How input is split before casing

Spaces, hyphens, underscores, dots, and camelCase boundaries become word breaks. user_profile_id becomes UserProfileId; “blog post title” becomes BlogPostTitle.

Leading digits are preserved inside words but identifiers cannot start with a number in most languages—rename manually if the output begins with a digit.

Common mistakes

Using PascalCase for JavaScript variables (userId should be camelCase; UserId reads like a type).

Letting the converter guess acronym casing—ApiKey versus APIKey is a team decision, not a universal rule.

Renaming a public type without updating imports, file names, and Storybook entries in the same change.

Applying PascalCase to SQL table names when your database standard is snake_case—ORM class names and table names are often different on purpose.

Best practices

Document acronym rules once (HTTPResponse vs HttpResponse) and link the doc from your README.

Match file names to component names when your bundler expects that pairing.

When mapping snake_case database columns to PascalCase models, keep a single source of truth for the mapping in your ORM config.

For headline copy, use the title case converter; keep PascalCase for code symbols only.

Pair with other Case Modify converters

Typical handoffs: PascalCase for exported types, camelCase for JSON fields, snake_case for warehouse tables, kebab-case for routes. Document the mapping in your API README so client teams do not guess.

For headline copy, use the title case converter; for code symbols, use this page. Keeping editorial casing separate from identifier casing avoids accidental PascalCase blog titles.

Frequently asked questions

Guides and deeper reading

• Complete guide to text case
• What is PascalCase?
• What is camelCase?
• camelCase vs snake_case
• kebab-case vs snake_case