Word & Character Counter
Words, characters, sentences and reading time, live as you type.
Text & Writing
Twelve cases: title, sentence, camel, snake, kebab, constant and more.
Naming conventions are not arbitrary style preferences — most ecosystems enforce one, and mixing them is how you get an import that resolves on macOS and fails on Linux.
| Case | Example | Standard use |
|---|---|---|
| camelCase | userAccountId | JavaScript and Java variables, JSON keys |
| PascalCase | UserAccountId | Class names, React components, C# everything |
| snake_case | user_account_id | Python variables, SQL columns, Ruby methods |
| CONSTANT_CASE | USER_ACCOUNT_ID | Environment variables, compile-time constants |
| kebab-case | user-account-id | URLs, CSS classes, HTML attributes, npm packages |
| dot.case | user.account.id | Config keys, Java packages, i18n message paths |
| Title Case | User Account ID | Headlines, page titles, button labels |
| Sentence case | User account id | Body copy, form labels, UI microcopy |
Title case capitalizes the first letter of every significant word. Sentence case capitalizes only the first word plus proper nouns. Which one you use is a house-style decision, and the two dominant style guides disagree.
AP style — the default across US and Canadian news — uses title case for headlines and lowercases conjunctions, articles and prepositions under four letters. Chicago style raises that threshold and lowercases all prepositions regardless of length. The Guardian and the BBC both use sentence case for headlines, which is why British news reads differently at a glance.
For interface copy, sentence case has won. Apple, Google, GOV.UK and Shopify all specify it in their design systems, on the evidence that it scans faster and handles product names more gracefully. If you are writing buttons and form labels, use sentence case.
This tool implements AP-style title case rather than naive per-word capitalization. Articles (a, an, the), coordinating conjunctions (and, but, or, nor, for, yet, so) and prepositions of three letters or fewer (of, in, on, at, to, by, up) stay lowercase — unless they are the first or last word, which always capitalize.
So "the state of the art in web design" becomes "The State of the Art in Web Design", not "The State Of The Art In Web Design". Hyphenated compounds capitalize both halves: "state-of-the-art" becomes "State-of-the-Art" under AP rules.
By design. camelCase, snake_case, kebab-case and their relatives are identifier formats, and identifiers in every mainstream language are restricted to letters, digits and one separator character.
The converter strips punctuation, collapses runs of whitespace, transliterates accented characters to their ASCII base (café becomes cafe), and joins what remains. "Order #42 — shipped!" becomes order42Shipped. That is the correct result, because the alternative would produce an identifier your compiler rejects.
If you need to preserve punctuation, use Title Case or Sentence case, which are display formats rather than identifier formats.
Yes, with one caveat worth knowing about. Case conversion uses locale-aware Unicode mapping, which handles German ß, Greek final sigma, and accented Latin correctly.
The caveat is Turkish. Turkish has a dotted and a dotless i, and uppercasing "i" gives "İ" in Turkish but "I" everywhere else. Getting this wrong is a well-documented source of bugs in international software. This tool uses your browser locale, so if you need the Turkish mapping specifically, set your browser language to Turkish first.
Paste the text and copy the Title Case row. The converter applies AP style, keeping short articles, conjunctions and prepositions lowercase unless they open or close the title.
Only the first character. camelCase starts lowercase (userName), PascalCase starts uppercase (UserName). PascalCase is sometimes called UpperCamelCase. Most languages use PascalCase for types and camelCase for values.
Yes. There is no length limit beyond your device memory, and conversion runs on every keystroke without lag on documents of tens of thousands of words.
Display cases (upper, lower, title, sentence, alternating, inverse) preserve line breaks and paragraph structure exactly. Identifier cases (camel, snake, kebab, constant, dot) collapse all whitespace by definition.
It should. The converter lowercases first, then applies capitalization rules, so "HELLO WORLD" becomes "Hello World" rather than staying uppercase. Tools that skip the lowercase step leave all-caps input unchanged.
Mostly for the mocking-tone internet meme. It is included because people search for it. It has no legitimate typographic use.
No. Conversion is a pure string operation running in this page. Check the Network tab in developer tools while you type — nothing is sent.