About TitleCasePro
TitleCasePro is a free, browser-based title capitalization tool built for writers, editors, students, journalists, researchers, and anyone who needs accurate, consistent title case fast.
What TitleCasePro Does
TitleCasePro converts any title or heading into the correct capitalization for 9 major style guides — APA, Chicago, AP, MLA, Bluebook, AMA, NY Times, Wikipedia, and Email. Conversion happens in real time as you type, with no server round-trip and no delay. Every word-level decision is explained: click "Explain" after converting a title to see exactly which rule was applied to each word.
Beyond title case, TitleCasePro includes a full-featured case converter with 13 output modes — including camelCase, PascalCase, snake_case, kebab-case, and CONSTANT_CASE — useful for developers as well as writers. The Batch Capitalizer converts hundreds of titles at once from a CSV or TXT import.
Our Mission
Title capitalization is deceptively difficult. The same title can be formatted differently depending on whether it is published in a journal, a newspaper, a book, or a Wikipedia article. Getting it right requires knowing the specific rules of the relevant style guide — and those rules differ in subtle but important ways between APA, Chicago, AP, MLA, and others.
Our mission is simple: make it fast and easy to get title case exactly right, for any style guide, with a clean and honest tool — no ads inside the tool area, no registration walls, no premium tiers hiding basic features.
Who Uses TitleCasePro
- Students and academics formatting essay and paper titles in APA or MLA style
- Journalists and editors applying AP Stylebook or NY Times house style to headlines
- Book authors and publishers following Chicago title case for chapter headings
- Medical and health writers formatting titles in AMA style for journal submissions
- Legal writers applying Bluebook citation title case to referenced works
- Content strategists and SEO professionals maintaining consistent title formatting across large content sets
- Email marketers writing professional email subject lines in sentence case
- Developers converting between programming naming conventions like camelCase, snake_case, and kebab-case
How It Works
All of TitleCasePro's tools run entirely in your browser. No text you enter is sent to a server. The capitalization engine is written in TypeScript and runs locally, which means results are instantaneous and your content stays private. There are no accounts, no logins, and no stored data beyond your own browser's localStorage for theme and history preferences.
Supported Style Guides
- APA — American Psychological Association, 7th Edition
- Chicago — Chicago Manual of Style, 17th Edition
- AP — Associated Press Stylebook
- MLA — MLA Handbook, 9th Edition
- Bluebook — The Bluebook, 21st Edition
- AMA — AMA Manual of Style, 11th Edition
- NY Times — New York Times house style
- Wikipedia — Wikipedia editorial guidelines (sentence case)
- Email — Professional email subject line convention (sentence case)
Who Runs TitleCasePro
TitleCasePro is built and maintained by Aditya Singh, who publishes as scortier. It is an independently run site, not a company — one named person writes the code, researches the style rules, writes the explanations on every style guide page, and answers the email.
He wrote the capitalization engine that powers every tool here. It is not a wrapper around someone else's library: each of the nine styles has its own hand-implemented rule module in TypeScript, built by reading the capitalization section of that style's source manual and turning it into an explicit, executable rule set. The engine is covered by a unit test suite that pins the expected output of known-difficult titles, so a change to one style's rules cannot silently break another's.
Every style guide page carries a byline and a "last reviewed" date, and prints the manual and edition its rules are drawn from. If you want to see exactly how the rules were derived, how the engine decides hyphenated compounds, acronyms and words after a colon, and how the results are tested, read the methodology page. The rule sets and their explanations were last reviewed end to end on .
Why This Site Exists
Free title case tools are easy to find and hard to trust. Most of them apply one loose rule to every style, none of them show their working, and almost none tell you which edition of which manual they are supposed to be following. If the output is wrong, you have no way to know, because there is nothing to check it against.
TitleCasePro was built to be the opposite: one page per style, the source manual named in the open, the rule applied to each individual word shown on demand via the "Explain" panel, and a public methodology describing every judgment call the engine makes where the manuals are silent. You should be able to disagree with a result and point to the exact rule you think we got wrong — and there is a documented way to report it.
How It Is Maintained and Funded
Corrections are the main input to this site. When a reader reports a result that does not match a style manual, the report is checked against the cited section; if it is confirmed, the rule module is fixed, a test case is added so the same error cannot return, and the affected style guide pages are updated with a new review date. Style guide pages are also re-checked as a set on the review date shown above.
TitleCasePro is free and has no accounts, no paid tier, and no feature held back behind a signup. Running costs are low by design — the site is static, hosted on a free-tier CDN, and does no server-side processing — and the intended funding model is advertising displayed around the content, never inside the tool area or in a way that interferes with using it. There are no sponsored style recommendations and no affiliate links in the style guides: nothing you read here is influenced by who pays for the page.
On privacy, the arrangement is simple: the tools run entirely in your browser, so the text you paste is never transmitted anywhere. Details are in the Privacy Policy.
Contact
Questions, corrections, or feature requests? Email Aditya Singh directly at workwithscortier@gmail.com, or see the contact page for what to include so a reply is useful.