PascalCase Converter
Convert phrases and identifiers to PascalCase — every word capitalized, no separators.
All cases — live preview (click any result to copy it)
Private by design — every conversion runs locally in your browser. Your text is never uploaded, stored or tracked.
PascalCase is a naming convention where every word in a phrase is capitalized and the words are joined with no separator at all: UserProfile, ShoppingCart, HttpRequestHandler. It differs from camelCase in exactly one letter — the first one is a capital — and that single letter carries meaning in most codebases: PascalCase names types, classes, interfaces, enums and React components, while camelCase names variables and functions.
Like the other developer converters on this site, this one splits before it joins. It understands existing camelCase humps, snake_case underscores, kebab-case hyphens, acronym boundaries and numbers, so “user_profile”, “user-profile” and “userProfile” all become the same clean UserProfile — and XMLParser becomes XmlParser rather than a mangled string of capitals.
When to use it
- Naming classes, interfaces, types and enums in C#, Java, TypeScript and Go
- Naming React, Vue and Angular components (UserCard, CheckoutForm)
- Converting database tables or API resources into class names
- Turning headings and phrases into valid type identifiers
- Standardizing names when moving code between languages and conventions
How it works
- The input is split into words using identifier-aware rules: separators, camel humps, acronym boundaries and number boundaries all count.
- Each word is normalized — first letter capitalized, the rest lowercased — so an acronym like ID becomes the word “Id”.
- The words are joined with no separator, including the first word, which is capitalized too.
- Characters that cannot appear in an identifier (spaces, punctuation, underscores, hyphens) are removed as part of the split.
Examples
snake_case input converts directly.
The acronym is treated as one word, then capitalized normally.
Good to know
The name PascalCase comes from the Pascal programming language, whose conventions popularized capitalizing every word in multi-word identifiers. Modern style guides kept the convention and gave it a job: in C#, Java, TypeScript, Go and PHP, a PascalCase name signals “this is a type” — something you instantiate, implement or import — while camelCase signals a value or a function. React enforces the distinction mechanically: a lowercase JSX tag is treated as an HTML element and a capitalized one as a component, so component names must be PascalCase to work at all.
Acronyms are the one place style guides argue. This converter normalizes an acronym to a single capitalized word (XmlParser, UserId), which matches the widely used rule that acronyms of three or more letters are treated as ordinary words, while two-letter acronyms are often kept in full (IOStream in some C# conventions). If your team's guide keeps certain acronyms in full capitals, adjust those few names after converting — the word boundaries this tool produces are the hard part, and they are already correct.
Frequently asked questions
What is the difference between PascalCase and camelCase?
The first letter. PascalCase capitalizes it (UserProfile); camelCase leaves it lowercase (userProfile). By convention PascalCase names types, classes and components, and camelCase names variables, functions and properties.
Why is it called PascalCase?
After the Pascal programming language, whose naming conventions — capitalizing every word in an identifier — were adopted by later languages and style guides, especially in the C# and Java worlds.
How are acronyms like XML or ID handled?
An acronym is treated as one word and capitalized like any other word: XMLParser becomes XmlParser and userID becomes UserId. This matches the common style-guide rule for acronyms of three or more letters.
Can I convert PascalCase back to snake_case or kebab-case?
Yes. The same word splitter works in every direction: paste UserProfilePage into the snake_case or kebab-case converter and you get user_profile_page or user-profile-page.
Is my text uploaded or stored?
No. The conversion runs entirely in your browser. Nothing you type is sent to a server, stored or logged — safe for proprietary code and schemas.