Contact
Bug reports, corrections and tool suggestions are all welcome.
Questions, bug reports and tool suggestions are all welcome. The fastest way to reach the site is by email.
Email: ktgseo14@gmail.com
Site owner: replace the address above in
assets/js/config.js (contactEmail) with a real inbox you monitor, then run the build again. If you prefer a contact form, add one here — but note that a form sends data to a third-party service, which the privacy policy would need to describe.
What to include in a bug report
Text tools fail in specific ways, and a good report usually needs three things:
- The tool you were using and what you expected to happen.
- A short sample of input that shows the problem. Please do not send confidential text — a trimmed-down example works better anyway.
- Your browser and whether you were on a phone or a computer.
Suggesting a tool
If a text job keeps coming up in your work and there is no tool for it here, describe the job rather than the feature. "I get exports where every second line is blank" tells us more than "add a regex mode".
Corrections
If a page describes a counting rule incorrectly, or a style guide summary on the Title Case Converter does not match the current edition, tell us which rule and which edition. Corrections like that are applied quickly.