Convert English case: title case, camelCase, snake_case and kebab-case
Paste English text, click once, and get the form you need: upper case, lower case, title case, sentence case, or the programming styles camelCase, snake_case and kebab-case. The naming modes split words first and rejoin them: spaces, underscores and hyphens always separate words, and camelCase and snake_case also split on case boundaries.
What it is actually for
The usual problem is inconsistent naming. A database export gives you user_first_name, the API expects userFirstName, and the URL slug wants user-first-name. Aligning them by hand across dozens of fields is where mistakes creep in.
The other common case is a column of all-caps English headings exported from Excel or an old CMS that needs to go back in as title case, or a normal sentence that has to become an all-caps banner, table header or file name.
- Normalising field names to camelCase or snake_case
- Turning a heading into a kebab-case URL slug or file name
- Fixing a column of all-caps titles imported from a spreadsheet
- Standardising API parameters, query strings or CSS class names
Rules and sharp edges
Upper, lower and sentence case only change letters; they do not reorder words. Title case capitalises the first letter of every space-separated word and lowercases the rest, with no part-of-speech awareness — so the, of and and also get capitalised. English title conventions lowercase articles and short prepositions, and brands get mangled: iPhone becomes Iphone, eBay becomes Ebay.
The three naming modes split words first, then rejoin them, and they lowercase everything before joining. HTTP_SERVER_NAME therefore becomes httpServerName, not HTTPServerName. Han characters have no case and pass through unchanged; punctuation and digits are not split points, so v1.2.3 stays intact. This is plain text substitution with no syntax awareness.
- camelCase for JavaScript variables and JSON fields
- snake_case for database columns and Python identifiers
- kebab-case for URLs, CSS classes and file names
- Fix abbreviations and brand names by hand after converting
Where it will bite you
Do not use it to edit code. Converting a whole selection also rewrites string literals, comments and import paths, because the page does not parse syntax and cannot tell a variable from a quoted message. Rename symbols with your IDE's refactoring tools instead.
It also ignores locale-specific rules. German ß uppercases to SS, Turkish has its own i/İ behaviour, and this tool uses JavaScript's default case mapping. When correctness depends on locale, use Intl or ICU.
- Renaming identifiers: IDE rename/refactor, not find-and-replace
- Locale-aware casing: Intl or ICU
- Bulk headings: export to CSV, transform, re-import into the original column
FAQ
What is the difference between camelCase and PascalCase?
camelCase starts lowercase and capitalises each following word, as in userName. PascalCase, also called UpperCamelCase, capitalises every word including the first, as in UserName. Class and component names usually take PascalCase, while variables and fields take camelCase. This tool produces camelCase; uppercase the first letter for PascalCase.
Why does title case capitalise the and of?
Title case here uppercases the first letter of every space-separated word and lowercases the rest, without checking part of speech. English title conventions lowercase articles, coordinating conjunctions and short prepositions unless they open or close the title, so a quick manual pass is still needed. Checking the small words usually takes a minute.
Why did my acronyms disappear in snake_case?
The naming modes lowercase the whole string before splitting and rejoining, so HTTP_SERVER_NAME becomes http_server_name. That keeps output tidy when the input capitalisation is inconsistent. To preserve acronyms, edit the result by hand or use a naming library with an acronym dictionary.
Related tool：Case Converter