Case Converter
Convert one name into 11 case styles
Enter one name or phrase. Basic shows 7 naming styles; Advanced also shows title, sentence, upper, and lower case.
The entire input becomes one name: line breaks are joined and acronyms such as API change case. Other punctuation is kept. Outputs are not validated as identifiers or URLs. Input stays in this page only.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Convert one name or phrase into 11 naming and text-case styles. Words are split at whitespace, underscores, hyphens, dots, slashes, backslashes, and case boundaries. Acronyms are normalized: HTTPResponseV2Token becomes httpResponseV2Token or http_response_v2_token. Newlines join words in one name, so this is not a per-line batch renamer. Other punctuation and leading digits remain; outputs are not validated as identifiers or URLs. Input is processed in the current page and is not saved as a browser draft.
Scenario Recipes
Convert an API field name
Goal: Turn user_profile_image_url into a frontend-style name.
- Enter user_profile_image_url in the input.
- Read userProfileImageUrl under camelCase and UserProfileImageUrl under PascalCase.
- Copy the required result. Choose Advanced to also see title, sentence, upper, and lower case.
Result: The normalized words are user, profile, image, and url. Acronyms are not kept uppercase in camelCase or PascalCase.
Suggested Workflow
Production Snippets
Acronym and digit boundary
text
Input: HTTPResponseV2Token
camelCase: httpResponseV2Token
PascalCase: HttpResponseV2Token
snake_case: http_response_v2_token
CONSTANT_CASE: HTTP_RESPONSE_V2_TOKENFailure Clinic (Common Pitfalls)
Pasting several names does not batch-convert them
Cause: Whitespace, including newlines, separates words within one input name.
Fix: Convert one name at a time. For example, user_id followed by order_id on the next line produces userIdOrderId in camelCase.
A converted string is not necessarily a valid code identifier
Cause: Separators are normalized, but other punctuation is kept, leading digits are not removed, and there is no transliteration.
Fix: Check the target language or URL rules. For example, 2_user becomes 2User and user@email remains user@email.
Frequently Asked Questions
Does it preserve API or HTTP as uppercase acronyms?
Not in camelCase or PascalCase. HTTPResponse becomes httpResponse or HttpResponse. CONSTANT_CASE produces HTTP_RESPONSE.
What does Title Case mean here?
It capitalizes each detected word and lowercases the remaining letters. It does not apply editorial title rules for articles or prepositions.
Does it translate or transliterate non-English text?
No. Characters are kept and Unicode case conversion is applied where available. For example, 用户_名称 becomes 用户名称 in camelCase. It is not a language-aware word segmenter.
Keep browsing