Case Converter
Convert text between camelCase, PascalCase, snake_case, kebab-case, CONSTANT_CASE, Title Case and more — with the convention you started in detected for you.
About this text
Every convention
All conversion happens in your browser. Nothing you paste is uploaded or stored.
What It Does
Every programming language and every style guide has its own opinion about how a name should be written, and moving between them by hand is tedious and error-prone. This tool converts text into fourteen naming conventions at once, so you can pick the one you need rather than typing it out. What makes it more useful than a search-and-replace is that it understands the structure of what you paste. It works out where the word boundaries are — including the awkward ones, like the point where an acronym ends and an ordinary word begins — and it tells you which convention your input was already using before it changes anything. Paste one identifier or a hundred lines of them; each line is converted independently, so renaming a whole set of database columns takes one operation.
When to Use It
- An API returns snake_case keys and your frontend expects camelCase, so you need to translate a list of field names before writing the mapping.
- You are adding a database migration and want the column names in the project's existing convention rather than the one you happen to prefer.
- A list of environment variables needs converting to CONSTANT_CASE before it goes into a deployment configuration.
- You are writing documentation and want a heading converted to proper title case without arguing about which small words get capitalised.
- You need a URL-safe kebab-case version of a page title for a route or a CSS class name.
Worked Examples
userFirstName
A straightforward camelCase identifier. The tool reports that it detected camelCase, then offers the same name in every other convention — snake_case, kebab-case and the rest — so you can take whichever the target system expects.
parseHTTPResponse
The acronym case that breaks naive converters. The HTTP stays intact, giving parse_http_response rather than the letter-by-letter mess a split-on-every-capital implementation produces.
the lord of the rings
Prose rather than an identifier. Title Case gives The Lord of the Rings, correctly leaving the minor words lowercase, while the identifier conventions collapse it into a single joined name.
Features
How to Use
1. Type or paste your text — a single identifier, or one per line for bulk conversion. 2. The tool reports which convention it detected, if it recognises one. 3. Every conversion appears below, each labelled with its convention name and an example. 4. Click the copy button beside whichever result you need. 5. Click Clear to start again.
Common Mistakes
- Splitting on every capital letter. It looks correct until an acronym arrives, at which point HTTPResponse becomes h_t_t_p_response and the output is unusable.
- Confusing camelCase and PascalCase. They differ by a single character but mean different things — one names a variable, the other a class — and linters treat the distinction as significant.
- Capitalising every word in a title. Real title case leaves articles and short prepositions lowercase unless they open or close the title, so The Lord Of The Rings is wrong.
- Using kebab-case for variable names. Most languages read the hyphen as a minus sign, so a kebab-case identifier is a syntax error rather than a style choice — it belongs in URLs and CSS.
- Converting a whole sentence with an identifier convention. Running prose through camelCase produces one enormous unreadable token; sentence and title case are the operations meant for text.