PascalCase, also called UpperCamelCase, capitalises the first letter of every word and joins them with no separators, like UserProfileId. It is the standard for naming classes, types, interfaces, and UI components in most languages.

How is it different from camelCase?

The only difference is the first word. PascalCase capitalises it (UserId) while camelCase leaves it lowercase (userId). Everything else about the two conventions is the same.

How does it split words?

Boundaries are detected at spaces, underscores, hyphens, and dots, and also at lowercase-to-uppercase transitions, so existing camelCase or kebab-case input is re-tokenised correctly. Digit runs are kept as their own segment.

What happens to acronyms?

Acronyms are normalised to a single leading capital, so HTMLParser becomes HtmlParser. If your style guide keeps acronyms fully uppercase, adjust the result after copying.

Is anything sent to a server?

No. All processing happens locally in your browser. Your text is never uploaded or stored.

PascalCase Converter

PascalCase, sometimes called UpperCamelCase, is the conventional way to name classes, types, and components. This converter rewrites any phrase or differently-cased identifier into PascalCase, removing separators and capitalising every word, including the first.

How it works

The input is split into a list of lowercase word tokens, then each token is capitalised and the tokens are concatenated with no separator:

"user profile id"  -> UserProfileId
"user_profile_id"  -> UserProfileId
"userProfileId"    -> UserProfileId
"open-api-spec"    -> OpenApiSpec

Word boundaries come from separators (spaces, underscores, hyphens, dots) as well as case transitions inside existing camelCase or PascalCase input, so the result is stable no matter how the source was formatted.

Tips and notes

Because acronyms are folded to a single capital, parseJSON becomes ParseJson. Restore the exact casing you need after copying if your codebase keeps acronyms uppercase. Letters and digits are also separated during tokenisation, which keeps the output predictable; rejoin a version segment manually if you prefer it glued to the preceding word.