camelCase Converter

The converter first breaks your text into words. It splits on spaces, line breaks, hyphens and underscores, and also where a lowercase letter is directly followed by a capital. Then it lowercases every word, gives each word after the first a capital first letter, and joins them with nothing in between.

Text that is already in camelCase comes back unchanged, so it is safe to paste a mix of styles.

Because each word is lowercased before its first letter is raised, a word typed in capitals loses them. Sometimes that's what you want, sometimes not:

• HTML parser becomes htmlParser and user ID becomes userId.
• XMLHttpRequest becomes xmlhttpRequest, because there is no lowercase letter between the capitals of XML and the H for a split to happen.
• parseHTTPResponse becomes parseHttpresponse and APIKey becomes apikey, for the same reason.

If your style guide keeps acronyms in capitals, as in userID, or wants apiKey, type a space between the acronym and the next word before converting, or fix the result by hand.

Only spaces, hyphens and underscores are removed. Other characters stay where they are, and many of them aren't allowed in a variable name:

• order total ($) becomes orderTotal($).
• Is Active? becomes isActive?.
• it's done becomes it'sDone.
• user.email stays user.email, since a dot doesn't separate words.

Numbers also need a look. page 2 title gives page2Title, which is fine, but 10 Tips for SEO gives 10TipsForSeo, and JavaScript, Java and most other languages don't allow a name to start with a digit. Remove punctuation from your input first, and rename anything that starts with a number.

Line breaks count as word separators, so a pasted list becomes one long name: first name and last name on two lines give firstNameLastName. To convert a list of field names, convert them one at a time. Accented letters are kept, so Über Cool Größe gives überCoolGröße. JavaScript accepts that, but most codebases stick to unaccented letters.