camelCase converter

How camelCase works

camelCase joins multiple words into a single identifier by lowercasing the first word and capitalizing the first letter of every word that follows. There are no separators — no spaces, no underscores, no hyphens. Examples: firstName, getUserId, isLoggedIn, parseJsonPayload.

The name comes from the “humps” the capital letters create inside the word. If the first letter is also capitalized the convention is called PascalCase (FirstName), and the two are almost always used together in the same codebase: camelCase for variables and functions, PascalCase for classes and types.

This tool normalizes the input first — it splits on spaces, underscores, hyphens, dots, slashes, and case transitions — then rejoins with the correct capitalization. That means you can paste first_name, first-name, first.name, First Name, or FirstName and get the same result: firstName.

When to use camelCase

Use camelCase whenever your language or style guide calls for it for identifiers that are not class names:

• JavaScript / TypeScript — variables, functions, method names, object keys in most style guides.
• Java — local variables, instance fields, method names (not classes or constants).
• Swift / Kotlin — variables, functions, property names.
• Go — unexported identifiers (camelCase) vs. exported (PascalCase).
• C# — parameters and local variables; PascalCase is used for public members.
• JSON APIs — most JavaScript-origin APIs use camelCase for field names (Stripe, GitHub, etc.). Many REST APIs from other language ecosystems use snake_case instead.

Need the snake_case or kebab-case version instead? The snake_case converter and kebab-case converter use the same input parsing. For a full breakdown of how the conventions map across languages, see camelCase vs snake_case.