Case Converter

What this tool does

A developer names a database column customer_shipping_address and then needs camelCase for the JavaScript object, PascalCase for the TypeScript type, kebab-case for the CSS class and a plain sentence for the label shown to a user. Retyping the same words four times invites typos, and a typo in an identifier is a bug that surfaces much later. This tool takes one phrase and returns ten common conventions at once, including camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE and sentence and title case, so the one you need is a single copy away. It is equally useful for writers who need a headline in title case and a URL slug in lower case from the same source, and for anyone standardising a batch of field names before committing code.

How to use it in three steps

1. Type or paste the phrase once, for example user profile name. All ten formats appear immediately without pressing anything.
2. Scan the list for the convention your target expects. Programming identifiers usually want camelCase or snake_case, while CSS classes and URLs generally want kebab-case.
3. Copy the single value you need, or use Copy all to take the whole set into a note or a code comment for later reference. Compare the generated identifier against your project's naming convention before pasting it into source code.

Questions people ask

Which case should I use for a CSS class name?

Kebab-case is the conventional choice, such as user-profile-card, because CSS is case-sensitive in some contexts and hyphens read clearly. CamelCase is more common in JavaScript variables and object keys.

What happens to punctuation and accents in my phrase?

Punctuation is treated as a word boundary and removed from programming-style outputs, while accented letters are normalised so the result is safe to paste into an identifier or a URL. Check the preview before using it in production code.

Does it change the meaning of acronyms?

It segments words rather than understanding them, so an acronym such as API may be split as three letters in some formats. For identifiers that must match an existing codebase, copy the value and adjust that one token manually.

What about a phrase that already contains an underscore or a hyphen?

Existing separators are treated as word boundaries, so a phrase such as user_profile-name is split into its component words before being rebuilt in each convention. That makes it safe to paste a mixed-format identifier in and take one consistent style out.

Privacy: The phrase you type is transformed locally in this browser tab; internal field names, unpublished product titles and draft headings are never sent to a server or recorded anywhere.