There is no contact form here, because a form would need a server and the whole point of this site is that it does not have one. Email works instead:
Reporting a rule that is wrong
This is the most useful message you can send, and the one most likely to change the site. The rules encoded here come from the published manuals and their publishers' own online guidance, and where the guides are ambiguous the tool follows the wording the manual's publisher and the most consistent secondary reproductions give — two of the four sections are paywalled, which is stated on the about page, and which means a genuine misreading is possible.
To make a correction actionable, include three things: the guide and edition, the wording in the manual that establishes the rule, and an example headline that this tool gets wrong. With those, the rule can be re-encoded, covered by a test that asserts the corrected output, and shipped. Without a citation it cannot be, for the same reason nothing on the site is asserted without one.
Requesting a case format
Twelve conversions are offered because those are the ones with real, documented use. If you need another — a different title-case guide, or an identifier convention with a specification behind it — say which and where it is defined.
The bar for adding a title-case guide is the same as for the four already here: the rules have to be published somewhere citable, they have to be reducible to a decision that can be made from the words alone, and the points where they cannot be must be identifiable so the tool can flag them instead of guessing. AMA and the Bluebook are the two most-requested candidates and both meet that bar in principle; what they need is a reading of the text itself rather than a plausible summary of it, and for a manual sold by subscription that is slower and more expensive than it sounds.
For identifier conventions the bar is a first-party source — a language specification, an official style guide, or the documentation of the system that consumes the name. "Everyone does it this way" does not get an unmarked row: where a convention is genuinely universal but no first-party document mandates it, the naming table says so in its Basis column and borrows no authority it does not have.
Reporting a bug
A conversion that produces the wrong output is worth a message even if you are not sure which rule it breaks. The useful details are the exact input text (paste it, do not retype it, since invisible characters and curly apostrophes matter), the button you pressed, the style guide selected if it was Title Case, and what you expected instead.
Two behaviours get reported as bugs regularly and are not: a lowercase word at the end of an APA-styled title, which is what APA's rule list produces because it has no last-word clause, and a lowercase particle in a phrasal verb like "backing up", which the tool flags in an amber panel rather than resolving. Both are explained on the title case page. If something else looks wrong, it probably is.
Embedding the converter
The main page has a copy-paste iframe snippet. It is free to use on any site, commercial or not, with no attribution requirement beyond the small credit line the embed already carries. It loads no tracking and transmits no text. If it does not fit your layout, adjust the height in the snippet — the tool is responsive down to phone width.
Privacy questions
Anything you type into the converter stays in your browser and is never received by us, so there is no stored text to ask about, export or delete. The full detail is on the privacy page.
What this address is not for
It is not a copy-editing service, and it cannot tell you which style guide your publisher wants — ask them, and the title case page explains which fields conventionally use which guide if you have to make the call yourself.
CaseConv is an independent project. Replies are usually within a few days.