“one-on-one meeting” — Uppercase, Lowercase, Title Case and Sentence Case
Enter this string in the converter and these are the four outputs it returns. Nothing here is stored or guessed: the same regular expressions that run in your browser were run at build time, so the page and the tool agree character for character.
Where each form belongs
| Form | Result | Typical use |
|---|---|---|
| UPPERCASE | ONE-ON-ONE MEETING | Loud labels, ticker codes, shouting about a deadline |
| lowercase | one-on-one meeting | Email addresses, URL slugs, file names |
| Title Case | One-on-one Meeting | Headlines, button labels, menu items |
| Sentence case | One-on-one meeting | Body copy, descriptions, help text |
How the rules behave on this string
Every conversion starts from the same tidy-up: runs of spaces collapse to one and the ends are trimmed, while line breaks are preserved. Uppercase and lowercase then apply directly. Sentence case lowercases everything and re-capitalises the first letter after a full stop, question mark, exclamation mark or line break. Title case lowercases everything and re-capitalises the letter that follows the start of a line, a space, a quote, a bracket or an apostrophe.
The hyphen counts as a word boundary in this implementation, so 2 hyphens in the input produce 2 extra capital in Title Case. That matches the converter exactly; copy editors differ on whether the second half of a compound should be capitalised.
Counted rather than eyeballed, the string runs 18 characters across 2 words, of which 15 are letters and 3 are punctuation, digits or spaces. Average word length works out to 7.5 letters, the longest word is “one-on-one” at 10 characters and the shortest is “meeting” at 7. Title Case puts in 2 capitals, 13% of the letter count. This is entry 51 of 76 in the reference.
Similar strings
Frequently asked questions
What does each of the four results mean?
They are four separate passes over the same 18-character string. UPPERCASE and lowercase are the obvious ones. Title Case capitalises the first letter of every word, and Sentence case capitalises only the first letter of each sentence while forcing everything else down. The converter on the homepage builds them with the identical rules.
Which one should I paste into my document?
For interface strings, Sentence case is the safer default: it reads like a sentence, translates more cleanly and avoids the question of which words count as important enough to capitalise.
Converting a whole paragraph, a JSON key list or a batch of headlines? The CaseLabNow case converter takes free text up to several thousand characters, and the case reference library has a page for every string listed here.