Turn labels and headers into camelCase identifiers
camelCase list items when you need code-ready identifiers from human text: column headers into object keys, form labels into variable names, or a spec list into property names. Each line is split into words, then joined with the first word lowercase and each following word capitalised.
Words are detected on spaces, hyphens, underscores, and existing case boundaries, so first name, first-name, and FirstName all resolve to firstName. Acronyms like HTTP request collapse to httpRequest rather than keeping stray capitals, matching how camelCase identifiers are usually written.
The Style selector reuses the same word-splitting for the other common programmer cases: snake_case, kebab-case, PascalCase, and CONSTANT_CASE. For sentence-style casing instead, see Title Case or Proper Case.
How to use camelCase list items
- 1Paste your list into the input panel, one label per line.
- 2Leave Style on camelCase, or pick snake, kebab, Pascal, or constant.
- 3Watch each line convert as you type or edit the input.
- 4Check acronyms and numbers read the way you expect for your codebase.
- 5Copy the result, or hit Download to save it as a plain text file.
Keyboard shortcuts
Drive ListShift without touching the mouse.
What the camelCase converter does
Five concrete behaviours behind the case conversion.
Words split on separators and case boundaries
Spaces, hyphens, underscores, and any other non-alphanumeric character split words, and a lowercase-to-uppercase boundary does too. So first-name, first_name, and firstName all tokenise to the same two words.
First word lowercase, rest capitalised
camelCase lowercases the first word and capitalises the first letter of each word after it, then joins with no separator. first name becomes firstName; shopping cart total becomes shoppingCartTotal.
Acronyms are folded, not preserved
A run of capitals like HTTP is treated as one word and cased normally, so HTTP request becomes httpRequest and user ID becomes userId. This matches the usual camelCase convention rather than keeping HTTPRequest.
Style covers the other programmer cases
The same tokens are rejoined differently per Style: snake_case with underscores, kebab-case with hyphens, PascalCase with every word capitalised, and CONSTANT_CASE in all caps with underscores.
Blank lines stay blank
A line with no letters or digits produces an empty line rather than a stray separator, so the output count matches the input.
Worked example
Spaces and an embedded acronym resolved to clean camelCase identifiers.
first name user ID HTTP request shopping cart total
firstName userId httpRequest shoppingCartTotal
Settings reference
How each Style changes the output, using the sample list above as the input.
| Setting | What it does | Effect on the sample |
|---|---|---|
| Style: camelCase (default) | First word lowercase, later words capitalised, no separator | first name gives firstName |
| Style: PascalCase | Every word capitalised, no separator | first name gives FirstName |
| Style: snake_case | All lowercase, words joined with underscores | first name gives first_name |
| Style: kebab-case | All lowercase, words joined with hyphens | first name gives first-name |
| Style: CONSTANT_CASE | All uppercase, words joined with underscores | first name gives FIRST_NAME |
| Blank lines (automatic) | Preserved as empty lines | An empty input line stays empty |