How do Title Case, Capitalized Case, and Sentence case differ?
Title Case follows editorial style rules by keeping 29 minor articles, conjunctions, and short prepositions lowercase mid-headline, whereas Capitalized Case capitalizes every word without exception. Sentence case lowercases the entire block and capitalizes only the first letter of each sentence and standalone I.
| Mode button | Example input (the quick-fox don't) |
Output | Best use case |
|---|---|---|---|
| Sentence case | HELLO WORLD. i AM HERE. |
Hello world. I am here. |
Fixing Caps Lock paragraphs |
| Title Case | a guide to the api |
A Guide to the Api |
Article headlines and titles |
| Capitalized Case | a guide to the api |
A Guide To The Api |
Every-word-capitalized headings |
| camelCase | user_first_name |
userFirstName |
JavaScript and JSON properties |
| snake_case | userFirstName |
user_first_name |
Python variables and SQL columns |
| kebab-case | User First Name |
user-first-name |
CSS classes and URL slugs |
How Title Case handles 29 minor words, hyphens, and contractions
The Title Case engine checks each word against a 29-word minor list (a, an, and, as, at, but, by, for, from, in, into, nor, of, on, onto, or, over, per, so, the, to, up, upon, via, vs, with, yet) and keeps them lowercase unless they open or close the line or follow a colon, hyphen, en dash, or em dash.
Hyphenated compounds like quick-fox capitalize each segment, while mid-word apostrophes like don't keep the trailing t lowercase. Once your headlines are formatted, you can check word and character counts on your formatted draft to verify title length limits.
Fixing accidental Caps Lock text with Sentence case and iNVERSE
Accidental Caps Lock paragraphs are easiest to repair with Sentence case, which lowercases the text and restores capitals at line starts and sentence boundaries defined similarly to Unicode Standard Annex #29 Text Segmentation (UAX #29). It also restores standalone lowercase i to I automatically.
If only a mixed-case block was inverted (hELLO wORLD), click iNVERSE to flip every uppercase letter to lowercase and vice versa without losing your original capitalization pattern.
Developer naming modes: camelCase, snake_case, and kebab-case
Five programming modes convert plain phrases or existing code identifiers line by line into camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE. Each line is tokenized independently so pasting a whole list of database columns or environment variables converts every identifier at once across all 12 case modes in the toolbar.
Tip: Click Use as input after converting a list of identifiers to chain a second pass without selecting and copying text manually.
Splitting camelCase and acronym boundaries per line
Before joining words with underscores, hyphens, or uppercase boundaries, codeWords() splits transitions between lowercase letters or digits and uppercase letters (userID2Name), as well as consecutive uppercase acronyms followed by lowercase (XMLHttpRequest). Non-alphanumeric separators such as spaces, dots, slashes, and underscores are stripped cleanly.
If you are cleaning up documentation snippets before converting headings or variable lists, you can remove Markdown markup before converting variable lists first so formatting symbols do not enter your identifiers.
Why code identifiers use locale-invariant ASCII casing
Prose modes like UPPER CASE and lower case call toLocaleUpperCase() and toLocaleLowerCase() as documented in the MDN String.prototype.toLocaleUpperCase Reference so language-specific rules work naturally.
However, locale-sensitive casing in Turkish locales turns lowercase i into dotted İ (U+0130), which breaks programming keywords and JSON keys. To protect code identifiers, camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE use locale-invariant ASCII casing instead.
Unicode normalization, accented characters, and multilingual casing rules
Real-world text often mixes precomposed accented characters (é as U+00E9) with decomposed combining sequences (e + U+0301) copied from PDFs or macOS filenames. Normalizing text before changing case prevents stray accents from breaking word boundaries.
Composing combining marks with NFC normalization
Every case mode except raw UPPER CASE, lower case, aLtErNaTiNg, and iNVERSE runs .normalize("NFC") first, following Unicode Standard Annex #15 Normalization Forms (UAX #15). Canonical composition merges base letters with their 1 to 4 bytes of combining marks so accented words capitalize cleanly at the first character.
When you want to verify exactly which characters changed between an original draft and a normalized, recased version, you can compare two text versions line by line side by side.
Handling non-Latin sentence punctuation and standalone pronouns
Sentence case recognizes sentence endings beyond ASCII periods, including …, । (Devanagari danda), ؟ (Arabic question mark), and CJK 。!?, capitalizing the next Unicode letter (\p{L}). Empty lines in multi-line code blocks stay blank rather than collapsing, preserving paragraph spacing in long documents.
When converting accented European languages, toLocaleUpperCase() and toLocaleLowerCase() follow your browser’s active BCP 47 (RFC 5646) locale rules rather than stripping diacritics. That keeps accents intact across French, Spanish, and German prose.
Chaining edits, exporting .txt files, and keeping drafts private
Changing text case in the browser eliminates round-trips to remote servers for sensitive emails, legal clauses, or proprietary source code. Everything updates instantaneously in local memory as you type, with 100% client-side execution and zero sign-up barriers.
- Keyboard-accessible mode switching: Focus the 12-button radiogroup and press
ArrowLeft,ArrowRight,Home, orEndto jump between Sentence case, Title Case, UPPER CASE, and code modes without reaching for a mouse. - One-click chaining and export: Use Copy to place the Converted box on your clipboard, Save .txt to download
converted.txt, Use as input to chain transforms, or Clear to reset the workspace. - Zero network transmission: No text is logged, stored, or sent over the network at any point during conversion.
- Proofreading by ear: After fixing capitalization and sentence starts on a long draft, you can listen to your cleaned draft read aloud locally to catch awkward phrasing.