What this tool does
This converter rewrites a batch of identifiers into a different convention: camelCase, PascalCase, snake_case, kebab-case or CONSTANT_CASE. One identifier per line — paste a whole column of field names and get the same column back in another style, which is what you need when aligning API payloads with database columns or CSS classes with design tokens.
Besides re-joining words it also handles four plain case styles: upper, lower, title case and sentence case. Those deliberately leave word order and punctuation alone, so they suit prose rather than identifiers.
How to use
- Step 1: paste the source One name or sentence per line. You do not have to declare the input style: word boundaries are detected automatically, whether the source uses camel humps (helloWorld), underscores, hyphens, dots or acronym runs such as HTTPServer.
- Step 2: pick a target style Choose the target style and the result recomputes immediately. The first five styles re-split and re-join words; when the original sentence structure must survive, use upper, lower, title or sentence case instead.
- Step 3: copy or download Use Copy to put the converted column on your clipboard, or Download to save it as a text file and replace the block in your code.
Limits
This is a text-level conversion only — it does not parse code, so it cannot tell whether a name is a variable or a class, and it will not warn about language keywords. The four plain case styles operate per line without sentence-level grammar analysis. A single file is capped at 10MB, and exceeding that reports a clear error.
FAQ
Can it handle a mixed-style list?
Yes. Each line is split independently, so a list mixing user_id, user-id, user.id, userId and userID all convert to the same target style.
How are acronyms such as HTTP or API treated?
A run of capitals counts as one word, so HTTP_SERVER_PORT becomes httpServerPort in camelCase. Keeping an acronym upper-case in the output (HTTPServerPort) requires a manual tweak — there is no acronym allow-list.
What happens to Chinese text?
Non-ASCII characters pass through unchanged: 用户 name becomes 用户Name in camelCase and 用户_name in snake_case.
Do numbers get separated?
No. Letters and digits stay together, so utf8Decoder splits into utf8 + Decoder and v2Api into v2 + Api, which avoids mangling version numbers and encoding names.
Does Title Case capitalise small words like the or of?
Yes — every word is capitalised (Hello The World). If you need strict title conventions that keep articles and prepositions lower-case, adjust those words by hand.
Is the input uploaded?
No. Conversion runs in the page and no request carries your text, so field and class names with commercial meaning never leave the device.