Contact Us
Have a question about TitleCasePro, a style guide rule you think is incorrect, a bug to report, or a suggestion for a new feature? We would love to hear from you.
Who You Are Writing To
TitleCasePro is run by one person: Aditya Singh, who publishes as scortier and who wrote the capitalization engine, the style guide pages, and the methodology. There is no support desk, no ticket queue, and no autoresponder — your email goes to him and he replies himself. You can read more about who runs the site and how it is funded on the About page.
The fastest way to reach us is by email:
We read every message and aim to respond within 2–3 business days.
What to Expect
Because one person handles everything, it helps to know what happens after you hit send:
- Replies usually arrive within 2–3 business days. Messages sent over a weekend are answered the following week.
- Rule corrections that cite a section number move fastest, because they can be checked against the source manual immediately and turned straight into a fix and a test.
- Confirmed rule errors are fixed in the rule module, locked in with a new unit test so the same mistake cannot come back, and reflected on the affected style guide page — which then shows a new "last reviewed" date.
- Feature requests get an honest yes, no, or "not soon". This is a free site maintained by one person, so not everything can be built, and we would rather say so than leave you waiting.
- What we cannot do: proofread or format your document for you, advise on which style your institution requires, or reproduce copyrighted style manual text. For those, go to the manual or to your editor.
What to Include
To help us respond quickly, please include:
- For style rule corrections: the exact title you entered (copied and pasted, not retyped), the style you selected, the output you received, the output you expected, and the manual, edition, and section or rule number that supports your expectation — for example CMOS §8.157, APA §6.17, MLA §1.2, or Bluebook Rule 10.2. A citation is what turns a disagreement into a fix.
- For bug reports: the page URL, what you did, what happened, and what you expected instead — plus your browser and device if the problem looks visual. If a tool produced wrong output, paste the input and the output verbatim; whitespace and punctuation matter.
- For feature requests: what you are trying to get done and where the current tools fall short. Describing the workflow is more useful than describing the feature, because there may already be a way to do it.
- For new style guide support: which style, which manual and edition defines it, and roughly how many titles a month you would run through it. Adding a style means implementing and testing a full rule set, so the source matters.
- For accessibility issues: the page, the assistive technology and browser you are using, and what blocked you. These are treated as bugs, not requests.
- For press, licensing, or partnership enquiries: who you are, what you want to use or discuss, and your deadline.
Common Topics
- Style guide accuracy — If you believe a capitalization result does not match the official style guide, please let us know the specific word, the title, and the edition of the guide you are referencing. We update our rules regularly. The methodology page explains where each style's rules come from and which edge cases the engine decides on your behalf, which may answer the question before you write in.
- New style guide support — If you need a style guide that is not currently supported, tell us which one and we will consider adding it.
- Accessibility — If you encounter any accessibility issues using TitleCasePro, please report them so we can fix them promptly.
- Privacy questions — Nothing you type into the tools is sent to a server; conversion happens entirely in your browser. The Privacy Policy has the full detail, and questions about it are welcome.
Before You Write
Two pages answer most incoming email. The FAQ covers how the tools work, which style to use in common situations, and what happens to your text. The methodology page covers the harder questions: which manual and edition each style is derived from, how hyphenated compounds, acronyms, first and last words, and words after a colon are handled, and how the rules are tested. If neither answers your question, please write — an unanswered question usually means a page needs improving.
About This Site
TitleCasePro is a free, browser-based title capitalization tool. For more information, visit our About page. For legal information, see our Privacy Policy and Terms and Conditions.