Case Converter

We support 15+ formats including camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, dot.case, path/case, Train-Case, Title Case, and more specialized naming conventions.

Yes, the smart detection system preserves acronyms like XML, HTML, API, and URL during conversion, keeping them recognizable in the output format.

Absolutely. The batch processing feature handles multiple lines simultaneously, applying the same conversion rule across all lines while preserving line structure.

As you type or paste text, all 15+ format conversions are displayed simultaneously in real-time preview panels, letting you compare and select the best format instantly.

Yes, many developers use it to standardize naming conventions across projects - converting snake_case database columns to camelCase for JavaScript, or generating kebab-case API endpoints.

camelCase (JavaScript functions and Java methods), PascalCase (classes in most languages), snake_case (Python and Ruby identifiers), kebab-case (CSS classes, URLs, file names), CONSTANT_CASE (environment variables and enums), and Title Case With Spaces. The converter applies each style's exact rules - camelCase lowercases the first word, PascalCase capitalizes all words.

Input like "parse HTTP2 request" splits into words on case boundaries and digits, so HTTP2 stays one token and becomes http2Request in camelCase or PARSE_HTTP2_REQUEST in constant case. Acronyms are never special-cased mid-conversion - URL becomes Url when Pascal-cased, matching the behavior of standard style guides like Google's Java Style.

Word boundaries come from four signals: spaces, hyphens, underscores, and lower-to-upper case transitions. A string like "XMLHttpRequest" splits at the l-to-H boundary into xml + http + request. If the split looks wrong, check for consecutive capitals - the algorithm treats each new uppercase run after a lowercase letter as a new word, which is the convention codifiers like Expressive Words rely on.