When to use camelCase
camelCase keeps the first token lowercase and capitalizes later tokens. It commonly represents values or behavior such as userProfile or fetchUserProfile.
Naming convention guide
camelCase vs PascalCase
camelCase and PascalCase both remove separators and capitalize internal word boundaries. camelCase starts lowercase, while PascalCase starts uppercase; that difference often signals different roles in code.
Quick comparison
| Difference | camelCase | PascalCase |
|---|---|---|
| Example | userProfileImage | UserProfileImage |
| Common use | Variables, properties, parameters, functions, and object fields | Classes, types, components, constructors, records, and models |
| First character | Lowercase | Uppercase |
| Word separator | None | None |
| Later words | Capitalized | Capitalized |
| Typical role | Value or behavior | Type or component |
When to use PascalCase
PascalCase, also called UpperCamelCase, capitalizes the first token too. Many ecosystems use it for types, classes, components, and constructors.
Decision matrix
| Context | Recommended convention | Why |
|---|---|---|
| Variables, parameters, and ordinary functions | camelCase | Lower camel case visually identifies values and behavior in many JavaScript and Java-style codebases. |
| Classes, types, components, and constructors | PascalCase | Upper camel case helps distinguish type-like names from ordinary values. |
| Generated SDK or schema code | Follow the generator or schema convention | Manual recasing can break generated references and makes regeneration harder to compare. |
| Public package or framework API | Follow the ecosystem convention | Users benefit more from familiar naming than from a project-specific preference. |
Which naming style should you choose?
Choose based on the identifier's semantic role. If a project uses camelCase for values and PascalCase for types, preserve that distinction and follow local acronym rules.
Common mistakes to avoid
- Do not treat PascalCase as only 'capitalize the first character'; acronym and token boundaries still matter.
- Do not use case alone to imply semantics if the surrounding ecosystem uses a different convention.
- Do not silently change generated or external identifiers when exact names are part of a public contract.
Convert between naming styles
Paste an identifier below to see the target format and every supported developer naming style. Conversion runs locally in your browser.
Detected: snake_case
PascalCase output
UserProfileImageUrl
All naming formats
camelCase
userProfileImageUrlPascalCase
UserProfileImageUrlsnake_case
user_profile_image_urlkebab-case
user-profile-image-urlCONSTANT_CASE
USER_PROFILE_IMAGE_URLdot.case
user.profile.image.urlpath/case
user/profile/image/urlConversion happens locally in your browser. Your input is not sent to a conversion server.