Camel Case Converter

How to use the camel case converter

1. Type or paste your text into Your text, one name per line. Click Example to load four sample lines.
2. Under Style, keep camelCase for variables and functions, or choose PascalCase for classes, types and components.
3. The Result box updates as you type. Click Copy or Download .txt.
4. To turn the result into another format, use the links under the tool to send it on to snake_case, kebab-case or a URL slug.

The example input shows the common starting points, all converted with the real code:

How the converter splits words

Every conversion first breaks each line into words, then rebuilds it. The rules:

• Separators. Anything that is not a letter or a digit separates words: spaces, tabs, underscores, hyphens, dots, slashes, commas, brackets, @ and so on. The separators themselves are dropped, so path/to/file becomes pathToFile and order total (USD) becomes orderTotalUsd.
• Existing capitals. A lowercase letter or digit followed by a capital starts a new word (parseHTML splits into parse and HTML). In a run of capitals, the last capital before a lowercase letter starts a new word, so XMLHttpRequest splits into XML, Http and Request. Two exceptions keep common technical terms whole: a capital plus one lowercase letter followed by a digit is not split (IPv6), and a single lowercase letter followed only by capitals is one word (iOS, mRNA).
• Case. Each word is lowercased, then the first letter of every word except the first is capitalized. In PascalCase the first word is capitalized as well. Acronyms are treated as ordinary words.
• Lines. Each line is converted separately and empty lines are kept. Spaces at the start and end of a line disappear, and Windows line endings become plain line breaks.

Because existing capitals mark word boundaries, the tool works in both directions: FirstName and first_name both give firstName, and you can paste camelCase back in to switch it to PascalCase.

Numbers, accents, apostrophes and emoji

• Digits stay attached to the letters they touch: base64 encode becomes base64Encode, page-2-title becomes page2Title and item2Price stays item2Price. A number standing alone joins the next word directly, so version 2 0 becomes version20. A letter right after a leading digit is never capitalized, in either style: 3d model gives 3dModel and 2fast 2furious gives 2fast2furious. Most languages do not allow a name to start with a digit, so add a letter in front if you need a valid identifier.
• Accented letters count as letters and are kept: café au lait becomes caféAuLait. Many languages and databases only accept ASCII names, so run the text through remove accents first if you need cafeAuLait.
• Apostrophes inside a word (straight ' or curly ’) are removed before splitting, as the Google Java Style Guide recommends: don't stop gives dontStop and Customer's name gives customersName.
• Emoji and symbols are removed: 😀 smile face becomes smileFace.
• Chinese and Japanese text is kept as it is, without spaces, because these scripts have no upper and lower case.
• Mixed-case brand names are handled by the splitting rules above. iOS app becomes iosApp and supports IPv6 on iOS? becomes supportsIpv6OnIos, the Google Java Style Guide’s own example. Words such as iPhone and eBay still split at their capital, because identifiers like xAxis have the same shape: iPhone 15 Pro becomes iPhone15Pro in camelCase and IPhone15Pro in PascalCase, and eBay stays eBay. Check names like these by hand.

When people need it

• Turning spreadsheet headers into field names. Paste a column of headers such as Order ID, Shipping address line 1 and Customer email, one per line, and you get orderId, shippingAddressLine1 and customerEmail for a JSON payload or a TypeScript interface. A header row copied as one line with commas becomes a single long name, so put each header on its own line first. The text splitter can do that.
• Moving data between back end and front end. APIs written in Python or SQL often return snake_case keys (created_at, is_active), while JavaScript code usually expects createdAt and isActive.
• Naming React or Vue components and classes. Switch to PascalCase to turn user profile card into UserProfileCard.
• Renaming CSS or config keys. A custom property such as --main-bg-color becomes mainBgColor for use in a JavaScript style object.

Order ID

shipping-address line 1
CUSTOMER_EMAIL
  billing  zip code

becomes

orderId

shippingAddressLine1
customerEmail
billingZipCode

camelCase, PascalCase and snake_case: which to use

The name comes from the capital letters in the middle of a word, which look like a camel’s humps. MDN calls camel case the most popular convention in JavaScript and Java. In practice, each language’s style guide decides:

Acronyms are where the guides disagree. The Google Java Style Guide lowercases everything before capitalizing, so “XML HTTP request” becomes XmlHttpRequest and “new customer ID” becomes newCustomerId. This converter follows that rule and gives the same two results. PEP 8 asks for the opposite in class names: HTTPServerError, not HttpServerError. The browser’s own XMLHttpRequest mixes both styles. If your codebase keeps acronyms in capitals, convert first and then restore the acronyms by hand.

For a longer comparison with kebab-case and when each one fits, read camelCase vs snake_case vs kebab-case.

Questions