What is the difference between camelCase, snake_case, kebab-case and PascalCase?
They are four ways of joining the words of an identifier: camelCase starts lower and capitalises each following word (userId), PascalCase capitalises every word (UserId), snake_case separates with underscores (user_id) and kebab-case with hyphens (user-id). None is "correct" — each language and format has its convention: JSON and JavaScript lean to camelCase, Python and SQL to snake_case, URLs and CSS to kebab-case, class names to PascalCase. A mismatch between an API contract and its consumer (userId vs user_id) is one of the most common integration defects.
How to use Pascal Case Converter
- Paste names or phrases, one per line.
- Optionally add a suffix for generated class names.
- Copy the PascalCase list.
Pascal Case Converter features
- Converts camelCase, snake_case, kebab-case and sentences to PascalCase
- Optional suffix such as Component, Service or Dto appended to every result
- Acronym normalisation (XMLHttpRequest → XmlHttpRequest)
- Batch conversion with an input/output table
Pascal Case Converter example
React component names
Input:
user_profile_card
order-summary-viewOutput:
UserProfileCard
OrderSummaryViewFrequently asked questions about Pascal Case Converter
What is PascalCase used for?
Class, interface, type, enum and React component names in C#, Java, TypeScript, Go (exported identifiers) and Swift. It is also called UpperCamelCase.
What does the suffix option do?
It appends a word to every result, so "order summary" with suffix "Component" becomes OrderSummaryComponent — handy when generating file or class names in bulk.
How is "XMLHttpRequest" converted?
Acronyms are split into words and re-capitalised: XmlHttpRequest. This matches the .NET and Google style guides.
Can I convert a whole list?
Yes — one identifier per line; the output preserves the order and a table shows each input with its result.