PascalCase Converter
Convert text to PascalCase for class names and React components. Free PascalCase converter online, no signup required.
Three steps to get started
Paste your text
Enter a phrase or identifier in any format - spaces, hyphens, underscores.
Converts to PascalCase
Every word capitalized, all separators removed: HelloWorld.
Copy the identifier
Click Copy and paste into your class definition or component file.
What is PascalCase?
PascalCase is a naming convention in which the first letter of every word - including the first - is capitalised and all separators are removed, producing identifiers such as ShoppingCartItem. It is formally called UpperCamelCase, and it takes its popular name from the Pascal programming language, whose 1970s Wirth-era libraries used the style throughout and whose descendants Delphi and Object Pascal carried it into mainstream Windows development.
In practice PascalCase marks a type rather than a value. That distinction is enforced by tooling more often than people realise. JSX treats a lowercase tag such as <button> as an HTML element string but resolves <Button> to a variable in scope, so a React component that is not PascalCase will silently render as an unknown DOM tag. Microsoft's .NET Framework Design Guidelines go further and specify PascalCase for public members of every kind - classes, interfaces, methods, properties, events, and namespaces - reserving camelCase only for parameters and private fields.
Concrete examples across ecosystems:
- React and Vue components:
UserProfileCard,NavBar,CheckoutSummary - TypeScript types and interfaces:
ApiResponse<T>,OrderStatus,PaginatedResult - Java and C# classes:
HttpClient,DatabaseConnection,StringBuilder - Python classes (PEP 8 calls it CapWords):
class OrderProcessor: - Go exported identifiers: capitalisation is the actual visibility mechanism -
ReadFileis public,readFileis package-private - Swift and Rust types:
URLSession,struct HttpRequest
PascalCase vs camelCase - and the acronym problem
The only structural difference is the first character: OrderService is PascalCase, orderService is camelCase. Everything after the first letter is identical. Use PascalCase for the thing being defined and camelCase for an instance of it, which is why const orderService = new OrderService() reads naturally.
Acronyms are the one place style guides genuinely disagree. .NET recommends treating acronyms of three or more letters as words - HtmlParser, not HTMLParser - while keeping two-letter acronyms fully uppercase, as in IOStream. Apple's Swift APIs take the opposite view with URLSession and JSONDecoder. This converter follows the title-cased approach, so base URL becomes BaseUrl; adjust by hand if your team's linter expects the uppercase form. Word splitting handles spaces, hyphens, underscores, and existing camel boundaries, and every keystroke is processed locally in your browser rather than on a server.