Text to PascalCase converter

What PascalCase is and how it differs from camelCase

PascalCase, also called upper camel case, joins several words into one token by capitalizing the first letter of every word, including the first, and removing the spaces: UserProfileImage, HttpClient, OrderStatus. It is identical to camelCase except for that first letter. camelCase writes userProfileImage with a lowercase start; PascalCase writes UserProfileImage with a capital. The name honors the Pascal programming language, which popularized the style for its identifiers.

The distinction is not cosmetic; in most languages the two cases carry different meaning. PascalCase is conventionally reserved for things that are types: class names, interfaces, enums, structs, type aliases, and, in React and most component frameworks, component names. camelCase is for instances of those things: variables, properties, and functions. Following the convention lets another developer tell at a glance whether OrderStatus is a type and orderStatus is a value of it. React enforces this directly, since it treats a lowercase tag as an HTML element and an uppercase one as a component.

How the converter produces PascalCase

The conversion happens in two steps. First the input is split into words at every boundary the tool detects: spaces, underscores, hyphens, dots, and the capitals inside an existing camelCase or PascalCase name. This means a plain phrase, a snake_case field, and a kebab-case slug all convert cleanly. Second, the first letter of every word is capitalized, the rest of each word is lowercased, and the words are concatenated with no separator.

So "user profile image" becomes UserProfileImage, "order_status" becomes OrderStatus, and "http-client" becomes HttpClient. Because PascalCase capitalizes the first letter, the result is always a valid name for a class or component in C#, Java, TypeScript, Swift, and React. Leading and trailing whitespace is trimmed and multiple separators collapse, so the output is a clean single token.

The acronym question is sharper in PascalCase than elsewhere because types are so visible. Should it be HttpClient or HTTPClient, ApiKey or APIKey? Microsoft's .NET guidelines say to treat acronyms longer than two letters as words (Html, not HTML), while many TypeScript and Java codebases keep short acronyms uppercase. The converter keeps common runs together; pick the rule your codebase follows and apply it consistently to the converted names.

When to convert text to PascalCase

The most common need is naming a new type or component from a human description. A spec calls for an "Order confirmation email" component, and you need OrderConfirmationEmail; a data model needs a "Customer billing address" type, and you want CustomerBillingAddress. Pasting the phrase and copying the result is faster than capitalizing and joining the words yourself, and it guarantees a valid identifier.

Code generation and migration also lean on PascalCase. When you scaffold TypeScript interfaces from a database, every snake_case table and column name often becomes a PascalCase type, so user_profiles turns into UserProfiles. ORMs, GraphQL schema generators, and API client generators all perform this conversion internally, and doing it manually for a one-off type is exactly what this converter is for.

Use the live converter above to turn your words or an existing identifier into PascalCase instantly. The side panel shows camelCase next to it, so when you need both the type name and an instance variable, such as OrderStatus and orderStatus, you can copy each without converting twice.