Convert to Title Case by style guide
AP and Chicago styles correctly lowercase articles, conjunctions, and short prepositions — first and last words always capitalized.
The Quick Brown Fox Jumps Over the Lazy Dog
How to Title Case correctly
Title Case isn't just capitalizing every word. Style guides (AP, Chicago) keep articles, conjunctions, and short prepositions lowercase — but always capitalize the first and last words.
- 01
Paste your title
Headlines, book titles, headings.
Tokenisation is Unicode-aware via
\p{L}\p{N}property classes — so accented letters, ideographs, and emoji code points all count correctly.titleUTF-8Unicodecode pointsliveinput · textraw · UTF-8the quick brown fox
loaded · UTF-8UTF-8 · ready - 02
Pick a style
AP (newsroom, blogs), Chicago (books), or All Words (capitalize everything).
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
APChicagolivememoisedoptionsstyle · optionsAP · liveThe Quick Brown Fox
options applied · livelive - 03
Stop words
AP/Chicago keep small connector words (a, an, the, and, in) lowercase — except first/last position.
Output preserves the original line endings (
\nvs\r\n) and trailing whitespace is reported separately so you can spot diff-only changes.stop wordsline endingswhitespacediff-cleanreproduciblerules · countedapplied · readyQuick Brown Fox in Forest
counted · livecounted - 04
Copy or download
One click.
Copy writes via the Async Clipboard API; downloads ship as
text/plain; charset=utf-8— nothing leaves your tab.copyclipboardtext/plainblobclient-sideexport · copiedready · done✓ Copied
shipped · ready to shipsuccess
Text-processing fundamentals worth knowing
Tokenise with Unicode classes
Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.
Normalise line endings
Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.
Mind invisible characters
Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.
Stream don’t slurp
For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.
Choose collation deliberately
Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.
Re-run after normalisation
NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.
When to Title Case
Headlines, headings, titles — anywhere editorial style matters.
Blog headlines
AP style for blog headlines and SEO. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.
Unicode-correctBook titles
Chicago style is standard for books. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.
diff-cleanSection headings
Documentation H2s and H3s in correct case. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.
instant countsSlide titles
Decks and presentations. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.
platform-awareEmail subjects
Marketing emails often use Title Case for subject lines. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.
code-point-accurateCitations
Academic article titles often want strict Chicago. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.
losslessFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.