Case Style Converter
Convert identifiers between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case, and Train-Case instantly.
Loading tool...
What is Case Style Converter?
The Case Style Converter transforms any identifier between the eight naming conventions used across programming languages and config formats: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case, and Train-Case. Smart word-splitting detects camel humps, acronym edges, and digit boundaries, so names like getHTTPResponse2Code convert cleanly, and every line is processed independently for batch renaming.
Key Benefits
- See all eight conversions at once instead of running one converter per style
- Acronym- and digit-aware splitting matches popular change-case libraries
- Batch conversion for entire column lists or key exports
- Automatic input style detection with live text statistics
Common Use Cases
- •Mapping database snake_case columns to camelCase model properties
- •Converting REST payload keys between kebab-case and camelCase
- •Renaming CSS class names from kebab-case to BEM or constant-case tokens
- •Normalizing config keys between dot.case env style and snake_case YAML
How to Use the Case Style Converter
- Paste your identifiers: Copy a variable, column, or key name into the input box — one identifier per line — or click Load sample to see how it works.
- Check the detected style: The tool automatically detects the naming convention of the first line and shows live line, word, and character counts while you type.
- Pick a target style: All eight conversions appear at once: camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, Title Case, and Train-Case. Acronyms and digits are split intelligently.
- Copy or download the result: Click Copy on the style you need, use Copy all to grab every conversion, or download the full list as a text file for your rename notes.
Key Features
- Eight target styles including camelCase, snake_case, kebab-case, and CONSTANT_CASE
- Smart word boundaries for acronyms like XMLHttpRequest and digits like sha256Sum
- Automatic detection of the input naming convention
- Batch conversion with one identifier per line
- Per-style copy buttons plus copy-all and download
- 100% client-side — your code never leaves the browser
Frequently Asked Questions
How does the converter handle acronyms and numbers?
The smart word-splitting recognizes camel humps, acronym edges, and digit boundaries. For example, getHTTPResponse2Code becomes get HTTP Response 2 Code, which then converts cleanly to get_http_response_2_code or getHttpResponse2Code.
Can I convert a whole list of identifiers at once?
Yes. Paste one identifier per line and every line is converted independently. Blank lines are preserved, which keeps column lists and key exports readable when you copy the result.
Why does XMLHttpRequest become xml_http_request in snake_case?
Because the leading acronym XML is treated as one word. This matches the behavior of popular change-case libraries and keeps the round-trip consistent: converting xml_http_request back to camelCase gives xmlHttpRequest.
Does the tool send my code to a server?
No. All parsing and conversion run locally in your browser with JavaScript. Nothing is uploaded, logged, or stored, so it is safe to paste internal identifiers.