← Back to the tool

PascalCase Converter — Classes, Components & Types Explained

Updated: May 2026

PascalCase is the universal convention for type-level identifiers in object-oriented and component-based codebases. Knowing precisely where PascalCase belongs and where camelCase takes over is one of the most fundamental readability conventions in modern software development.

Convert text to PascalCase →

Free · No upload · Instant results

What is PascalCase?

PascalCase (also called UpperCamelCase) capitalises the first letter of every word in a compound identifier, including the very first word. No spaces, hyphens or underscores are used. The convention is named after the Pascal programming language, which popularised this style in the 1970s.

Examples:

  • UserProfile — a class or React component
  • HttpResponseMessage — a type in .NET
  • PaymentGatewayAdapter — a design-pattern class
  • NavBar — a UI component name
  • DatabaseConnectionPool — a service class

Where PascalCase is used

  • Classes (all OOP languages): Java, C#, Python, TypeScript, Kotlin, Swift — all use PascalCase for class names by convention and by the compiler/linter.
  • React components: JSX requires component names to start with a capital letter to distinguish them from native HTML elements. <NavBar /> is a component; <navbar /> is an unknown HTML element.
  • TypeScript types and interfaces: interface UserProfile, type ApiResponse. TypeScript's own standard library follows PascalCase for all type names.
  • Enumerations: both the enum name and its members are typically PascalCase (enum UserRole { Admin, Editor, Viewer }).
  • C# public members: Microsoft's .NET coding conventions mandate PascalCase for all public properties and methods — even when camelCase is used privately. This is the primary reason C# developers sometimes find cross-language collaboration confusing.
  • File names for components: Angular, React and Vue projects conventionally name component files in PascalCase (UserProfile.tsx, NavBar.vue).

PascalCase vs camelCase — the semantic split

The distinction between PascalCase and camelCase is not aesthetic — it carries meaning. In most codebases, PascalCase signals "this is a type or category you instantiate or import", while camelCase signals "this is a value or action".

  • class UserProfile (PascalCase) vs const userProfile = new UserProfile() (camelCase)
  • function GetUser (wrong in JS/TS — looks like a constructor) vs function getUser (correct camelCase)
  • interface ApiConfig (PascalCase type) vs const apiConfig: ApiConfig = {…} (camelCase variable of that type)

A useful mental model: if the identifier appears after class, interface, type, enum or new, it should be PascalCase. If it appears in an assignment, function call or parameter position, it should be camelCase.

Frequently asked questions

What is PascalCase?

PascalCase capitalises the first letter of every word in a compound identifier, including the very first. Example: UserProfile, GetUserName, HttpResponseMessage.

What is the difference between PascalCase and camelCase?

Both join words without spaces and capitalise each word boundary. PascalCase also capitalises the first word (UserProfile), while camelCase keeps it lowercase (userProfile).

Is PascalCase the same as UpperCamelCase?

Yes. UpperCamelCase is an alias for PascalCase. The terms are completely interchangeable in all style guides and documentation.