About Title Case
Title Case capitalises each word in a block of text, which is the quickest way to turn a heading written in sentence case into one written in headline style. The words are first separated on spaces and on the boundaries that appear in identifiers — a run of lower-case characters followed by a capital, or an underscore, hyphen, slash or dot — so a term written in camel case comes out as separate capitalised words.
Capitalisation works per word: the first character is raised and the remaining characters are lowercased. That second half is the detail to be aware of, because it means existing internal capitals are not preserved. A brand name with a lower-case first letter, an acronym, or any mixed-case identifier will come back normalised rather than intact.
Titles also have their own convention about small words, and this tool does not implement one. Every word is capitalised, including the articles and short prepositions that many style guides leave in lower case. If you need a specific house style, treat the output as a first pass and adjust the small words by hand.
How to use Title Case
- 1 Paste the heading or phrase you want capitalised.
- 2 Read the output, where every word starts with a capital letter.
- 3 Fix the short words that your style guide wants left in lower case.
- 4 Check any acronyms or brand names, since their internal capitals are normalised.
Frequently asked questions
Why did my acronym come back as an ordinary word?
Because capitalisation lowercases the remainder of each word after raising the first letter. An all-capitals acronym or a mixed-case brand name therefore loses its original shape, and those are worth correcting by hand in the output.
Does it skip small words like and or of?
No. Every word is capitalised, which is one legitimate title convention but not the only one. Style guides that lowercase articles and short prepositions need a manual pass over the output.
How are hyphens and underscores treated?
They are treated as word separators, so both halves are capitalised and the separator itself is preserved in a title conversion. That is convenient for identifiers but means a hyphenated compound is capitalised on both sides, which some styles prefer not to do.
Will it handle a heading that is already partly capitalised?
Yes, and it will normalise it. Whatever casing was there before is replaced by the rule above, which is what makes the result predictable; the trade-off is that any deliberate casing in the original is not preserved.
Free, online, and private
Free to use
Title Case is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Title Case behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Word splitting | whitespace, camelCase boundaries, and the four separators - _ . / which are replaced by a space |
| Capitalisation rule | first character of each word upper, remainder of the same word lower, applied to every word without exception |
| Stopword handling | none — the, of, a, and and in are capitalised exactly like any other word |
| Output separator | a single space; the original hyphen, underscore, dot and slash characters are not written back |
| Whitespace | runs collapse to one space and both ends of the block are trimmed |
| Update mode | live — recomputed on every keystroke |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Title Case does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Hyphens, slashes, underscores and dots are consumed as word separators and come back as spaces, so "state-of-the-art" is returned as "State Of The Art" and a file path or URL loses its punctuation entirely — the original punctuation cannot be reconstructed from the result.
- A lower-to-upper change is treated as a word boundary, so camelCase and proper nouns are taken apart: "iPhone" becomes "I Phone", "eBay" becomes "E Bay" and "McDonald" becomes "Mc Donald" with no way to switch that splitting off.
- Apostrophes are not boundaries and are not capitalised around, so "o'brien" returns as "O'brien" rather than "O'Brien", and because no stopword list exists the output does not follow the title conventions used by most style guides.
Tested and documented by itoolnet, the team that builds and maintains this site.