Case Converter

Type once, get every case at once — each with its own copy button. Title Case keeps minor words like “a”, “of”, and “the” lowercase mid-title, and the programmatic cases (camelCase, snake_case, kebab-case, CONSTANT_CASE) understand existing camelCase boundaries, so identifiers convert cleanly.

Common uses

• Rename variables between camelCase and snake_case conventions
• Fix a headline typed in all caps
• Generate a CONSTANT_CASE key from a label

Example

parseJSONResponse

snake_case: parse_json_response · kebab-case: parse-json-response

Is my text stored anywhere after I convert its case?

No. The conversions run in your browser as you type and nothing is sent to a server or saved, so code identifiers and unpublished copy stay on your machine.

What's the difference between camelCase and PascalCase?

Both remove separators and capitalize word boundaries; camelCase starts with a lowercase letter (parseJsonResponse) while PascalCase capitalizes the first word too (ParseJsonResponse). Convention usually puts camelCase on variables and functions and PascalCase on class and type names.

Why doesn't Title Case capitalize every word?

Standard title style keeps short articles, conjunctions, and prepositions — a, an, the, of, in, to, and similar — lowercase in the middle of a title. The first and last words are always capitalized, which is why "of" stays small mid-title but not at the start.

How does the converter split a name that's already camelCase?

It detects boundaries where a lowercase letter or digit meets an uppercase letter, and where an acronym ends, so parseJSONResponse splits into parse, JSON, and response. That's why converting to snake_case gives parse_json_response instead of mangling the acronym.