Text Case Converter
Convert text to UPPER CASE, lower case, Title Case, camelCase, PascalCase, kebab-case, and snake_case instantly. Free online tool.
- Runs in your browser
- Tool input is not uploaded to ZeroTool servers
- Free · No Sign-Up
Scan with WeChat to share this tool
Examples, details and FAQ Worked examples, how it compares with other tools, and answers to common questions.
Case Formats Reference
| Name | Example | Common Use |
|---|---|---|
| UPPER CASE | HELLO WORLD | Headings, constants (informal) |
| lower case | hello world | General text normalization |
| Title Case | Hello World | Titles, proper nouns |
| Sentence case | Hello world | Normal prose |
| camelCase | helloWorld | JS variables, JSON keys |
| PascalCase | HelloWorld | Classes, components |
| kebab-case | hello-world | CSS classes, URL slugs |
| snake_case | hello_world | Python, SQL columns |
| CONSTANT_CASE | HELLO_WORLD | Env vars, constants |
Examples
Each row is the tool's output for the same input. The input getHTTPResponseCode v2 mixes an acronym, camel humps and a version number:
| Format | Output |
|---|---|
| camelCase | getHttpResponseCodeV2 |
| PascalCase | GetHttpResponseCodeV2 |
| kebab-case | get-http-response-code-v-2 |
| snake_case | get_http_response_code_v_2 |
| CONSTANT_CASE | GET_HTTP_RESPONSE_CODE_V_2 |
| Title Case | Gethttpresponsecode V2 |
The digit splits from the letter, so v2 becomes v-2 in kebab-case. In camelCase and PascalCase the two parts are joined again, which is why V2 looks unchanged there. If you need v2 as one word, rename it in the result.
A second input, OAuth2 token expires_in, shows how a mixed-case brand name is split: camelCase gives oAuth2TokenExpiresIn, snake_case gives o_auth_2_token_expires_in. The split happens at the lowercase-to-uppercase change in "OAuth". Write oauth2 in lower case first if you want oauth_2_token_expires_in.
A list of SQL columns such as user_id, created_at becomes userIdCreatedAt in camelCase: the comma and space are separators like any other punctuation, so all words end up in one identifier.
How Words Are Split
camelCase, PascalCase, kebab-case, snake_case and CONSTANT_CASE first split the input into words, with the same rules as the change-case library's split with separateNumbers:
- At a lowercase letter or digit followed by an uppercase letter:
userLoginCount→ user, Login, Count. - Before the last capital of an acronym that starts a new word:
XMLHttpRequest→ XML, Http, Request. - Between letters and digits:
base64Encode→ base, 64, Encode. - At any run of spaces, punctuation or symbols:
user-login_count→ user, login, count.
Apostrophes are removed before splitting (as lodash does), so don't stop → dontStop. Letters from any script and their accents are kept: café au lait → caféAuLait, Привет мир → приветМир.
Limitations
- Title Case and Sentence case keep your spacing and punctuation and do not split identifiers:
userLoginCount→Userlogincount. Title Case capitalizes every word, including short words such as "of" and "the". - Sentence case capitalizes only the first letter of the whole input and lowercases the rest:
first. second sentence! THIRD→First. second sentence! third. Proper nouns and later sentences need manual fixes. - Spaces, quotes, brackets and symbols before that first letter are skipped. A Chinese, Japanese or Korean character also counts as a letter, so a Latin word after it stays lowercase. If the first letter or digit is a digit, nothing is capitalized:
2FA CODE→2fa code(see the examples below). - The identifier formats treat line breaks as separators too, so a multi-line list becomes one long identifier. Convert one name at a time, or use Line Tools to clean up a list first. For URL slugs with transliteration of accented letters, use Slugify.
- Acronyms are not kept in capitals in camelCase or PascalCase:
parseHTML→parseHtml. - Case changes use the browser's default Unicode rules, not a language-specific locale:
ßbecomesSSin CONSTANT_CASE, and Turkish dotted/dotless i is not handled. - Scripts without letter case (Chinese, Japanese, Korean) pass through unchanged; only spaces and punctuation between them become separators. A capital letter directly after a Chinese, Japanese or Korean character does not start a new word, so
用户IDstays one word (用户idin kebab-case); put a space before the Latin part to split it. - Emoji and other symbols are separators in the identifier formats, so they are removed there; UPPER CASE, lower case, Title Case and Sentence case keep them.
- Full-width letters typed with a Chinese, Japanese or Korean input method stay full-width in every format. Convert them to normal-width letters first if the result must be ASCII.
Example: "hello" she said becomes "Hello" she said in Sentence case: the quotation mark is skipped and the first letter after it is capitalized. Title Case gives "Hello" She Said.
Example: 2FA CODE gives 2fa code in Sentence case because the input starts with a digit.
Example: 🚀 launch day gives launchDay in camelCase and LAUNCH_DAY in CONSTANT_CASE (the emoji is dropped), but 🚀 Launch Day in Title Case.
FAQ
What is camelCase, and how is it different from PascalCase?
camelCase joins words with no separator, keeps the first word lowercase and capitalizes each word after it: 'hello world' → 'helloWorld'. It is common for JavaScript variable names. PascalCase also capitalizes the first word: 'HelloWorld', common for class and component names.
What are snake_case and kebab-case?
Both join lowercase words. snake_case uses underscores ('Hello World' → 'hello_world'), common in Python and database column names. kebab-case uses hyphens ('hello-world'), common for CSS class names. Accented letters stay as they are ('café au lait' → 'café-au-lait'); for an ASCII-only URL slug, use the Slugify tool.
Can I convert an existing identifier such as userLoginCount?
Yes. The tool splits words at case changes, so 'userLoginCount' gives 'user_login_count' and 'XMLHttpRequest' gives 'xml-http-request'. Digits become their own word: 'base64Encode' gives 'base-64-encode'. Paste one name at a time: spaces, commas and line breaks are separators, so a list of names becomes one long identifier.
Why does parseHTML become parseHtml?
The tool splits 'parseHTML' into 'parse' and 'HTML', then writes every word after the first as one capital letter followed by lowercase letters. Style guides do not agree on acronyms (some keep 'HTTP', others write 'Http'), and the tool cannot know which one your project follows. If you need 'parseHTML', change the acronym in the result.
Does Title Case follow a headline style such as AP or Chicago?
No. Title Case capitalizes the first letter of every word, including short words: 'the lord of the rings' becomes 'The Lord Of The Rings'. It also lowercases the rest of each word, so 'iPhone' becomes 'Iphone'. If your style keeps some short words in lowercase, edit them in the result.
Is my text sent anywhere?
No. The conversions run in your browser tab with JavaScript; the text is not sent, and the tool does not save it in browser storage. Page analytics record only the tool name and which Copy button you clicked (for example copy_camel), not the text.