Case Converter

Convert text into camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case, UPPERCASE and lowercase — every variant shown at once.

Runs entirely in your browser — nothing is sent to our servers.

How to use it
  1. Paste or type an identifier or phrase into the input panel.
  2. Every case variant updates live on the right.
  3. Press the copy button beside the variant you need.

Input

Output

camelCase

helloA2zutilDevWorld

PascalCase

HelloA2zutilDevWorld

snake_case

hello_a2zutil_dev_world

CONSTANT_CASE

HELLO_A2ZUTIL_DEV_WORLD

kebab-case

hello-a2zutil-dev-world

Title Case

Hello A2zutil Dev World

UPPERCASE

HELLO A2ZUTIL.DEV WORLD

lowercase

hello a2zutil.dev world

What is case conversion?

Every codebase carries its own naming conventions: JavaScript variables in camelCase, database columns in snake_case, CSS classes and URL slugs in kebab-case, React components in PascalCase, environment variables in CONSTANT_CASE. Moving a single field between layers — a database column becoming a JSON key becoming a frontend prop — means rewriting the same word in a different shape, over and over.

Case conversion automates that rewrite: it splits the input into words (however they were originally separated — spaces, hyphens, underscores, or capital letters) and rejoins them in whichever convention you need.

Why use this tool

This tool shows every variant at once instead of making you pick a target first, so you can copy whichever one you actually needed — useful when you're not sure yet whether the target system wants userId or userID for an acronym, and would rather see both than guess.

Everything runs in your browser. Identifiers and field names occasionally carry internal naming that shouldn't leave your machine, so a converter that posts your input to a backend is a bad habit — this one has no backend to post to.

Case conversion gotchas

Acronyms split heuristically

Consecutive capital letters are treated as one acronym unit, split from the capitalized word that follows it — so parseXMLDocument becomes parse / XML / Document, and userID becomes user / ID. It handles the common cases well, but an unusual acronym boundary (an acronym immediately followed by another acronym, for instance) may need a manual touch-up after conversion.

Digits stay attached to their word

A digit adjacent to letters is treated as part of that word rather than a separate token — item2Name splits into item2 / Name, not item / 2 / Name. A digit surrounded by existing separators, like item-2-name, does become its own word.

Already-separated text works the same way

Spaces, hyphens and underscores are all treated as existing word boundaries, so user-id, user_id and user id all convert identically to whichever case you pick — you don't need to normalize the input first.

Case converter FAQ

No. Case conversion runs entirely locally in your browser.

camelCase, PascalCase, snake_case, CONSTANT_CASE, kebab-case, Title Case, UPPERCASE and lowercase — all shown simultaneously.

Reasonably well: consecutive capital letters are treated as one acronym unit, split from the next capitalized word — e.g. parseXMLDocument becomes parse / XML / Document — though unusual acronym-adjacent-to-acronym cases may need a manual touch-up.

A digit next to letters stays attached to that word (item2 stays item2 rather than splitting into item / 2), but a digit already surrounded by separators becomes its own word.

Yes — spaces, hyphens and underscores are all treated as existing word boundaries, so it converts the same as userId would.