Case Converter
Convert text between ten naming conventions.
Processed locally in your browser. Nothing you type here is sent to our servers.
What does this tool do?
It converts text into every common naming convention at once, so you can copy the one you need rather than retyping. All eleven results update as you type.
The useful part is that conversion goes through a single tokenizer, so every output
agrees on where the word boundaries are. Paste XMLHttpRequest and every
result splits it as xml · http · request, which is what you want and
what a naive split on capital letters gets wrong.
How to use it
- Type or paste your text into the input.
- Every conversion appears below and updates as you type.
- Press Copy beside the one you want.
- Leave Convert each line separately ticked when pasting a list.
The conventions, and where they are used
- camelCase — variables and functions in JavaScript, Java, Swift.
- PascalCase — classes, types and components almost everywhere.
- snake_case — Python, Ruby, and SQL column names.
- kebab-case — URLs, CSS classes, HTML attributes, CLI flags.
- SCREAMING_SNAKE_CASE — constants and environment variables.
- dot.case — config keys and namespaced identifiers.
- path/case — file paths and route segments.
- Title Case — headings, with minor words correctly left lowercase.
- Sentence case — body copy, UI labels and commit messages.
How word boundaries are detected
The tokenizer splits on all of the following:
- Existing separators: spaces, underscores, hyphens, dots, slashes.
- A lowercase letter followed by an uppercase one —
fooBar→foo · bar. - The end of an acronym run —
XMLHttp→xml · http. - Boundaries between letters and digits —
oauth2Token→oauth · 2 · token.
Convert each line separately is on by default, so pasting a list of field names converts each one independently rather than joining them into a single identifier.
Common use cases
- Turning a list of column names into a set of properties for a model.
- Producing a URL slug from an article title.
- Converting API field names between a snake_case backend and a camelCase client.
- Generating environment variable names from a config key.
Limitations
- Title case follows a common English convention for minor words. Style guides disagree with each other, so check the result against yours.
- Acronym handling is heuristic.
IOErrorbecomesio · error, which is usually right — but a deliberately unusual identifier may not split as you intend. - Existing capitalisation inside a word is not preserved.
iPhonebecomesi · phone, and no tokenizer can know it should not. - Non-Latin scripts have no case distinction to convert; they pass through unchanged.