Case Converter

Every programming language and ecosystem picked its own way to spell compound names. JavaScript and Java write variables and functions in camelCase (myVariableName), classes and React components in PascalCase (MyComponent), and constants in SCREAMING_SNAKE_CASE (MAX_RETRY_COUNT). Python and Ruby prefer snake_case (my_variable_name). CSS classes and URL slugs use kebab-case (my-variable-name). When you port code between languages, generate an environment-variable key, or build a URL slug, you end up converting between these by hand — fiddly, and easy to get wrong when a name has many words.

This tool does that conversion for you. You paste an identifier, a phrase, or a whole list of names, and it splits the text into its component words and shows you every common format at once: lowercase, UPPERCASE, Title Case, Sentence case, camelCase, PascalCase, snake_case, SCREAMING_SNAKE_CASE, kebab-case, SCREAMING-KEBAB-CASE, dot.case and path/case. Everything updates live as you type, so you read the format you want off the grid and copy it with one click — no conversion button, no re-running.

Because identifiers cannot contain spaces, converting them means first guessing where the words begin and end. This is genuinely hard: an input like HTTPServerError could read as HTTP Server Error or Http Server Error, and J2SEProjectTypeProfiler only splits correctly if you know J2SE is a single unit. This tool uses a documented heuristic — it recognises camelCase humps and treats consecutive capitals like HTTP as one token — and it is honest that no rule set is perfect for every ambiguous name. All of it runs locally in your browser; nothing you type is uploaded.

Conversion happens in two steps: split the input into word tokens, then rejoin those tokens in the target case.

Splitting: the input is broken into runs of letters and digits, then each run is further split on delimiters (space, underscore, hyphen, dot, slash) and on camelCase boundaries. A hump is a lowercase or digit directly followed by an uppercase (myVariable → my | Variable). Consecutive capitals are treated as an acronym unit when an uppercase is followed by uppercase-then-lowercase (HTTPServerError → HTTP | Server | Error). This mirrors how editors and linters split identifiers; it is a heuristic, not an oracle, and remains ambiguous for inputs with no case transitions or unusual acronyms.

Rejoining: tokens are lowercased or capitalised per target case and joined with the right separator — lowercase/Title/Sentence join with a space, camelCase and PascalCase join with nothing, snake_case with an underscore, kebab-case with a hyphen, dot.case with a dot, path/case with a slash. Uppercased variants (SCREAMING_SNAKE_CASE, SCREAMING-KEBAB-CASE) simply uppercase the joined tokens.