Feedback & Contact
“This tool is broken” tells us there is a problem. Five extra details can tell us where it is.
For a tool or editor bug
- Tool URL: copy the exact Kaazo page address.
- Browser and device: for example Chrome on Windows 11 or Safari on iPhone.
- Source type: PDF, JPG, CSV, DOCX and so on. Do not post a confidential source file publicly.
- Expected result: what you thought the tool would do.
- Actual result: error text, wrong page order, damaged formatting, blank export, UI problem—whatever you saw.
A screenshot is useful when the problem is visual. For repeatable output bugs, a small non-sensitive sample file can be even more useful.
For content or SEO feedback
Send the page URL and the specific statement that looks wrong, unclear or outdated. We would rather correct one precise claim than pad a page with vague language.
Where to reach Kaazo
You can contact the project through its official social profiles:
Please do not send passwords, private keys, financial credentials or sensitive personal documents through social messages.
What happens after a report?
Reproducible problems are the easiest to fix. When a bug is confirmed, we aim to turn the failure into a regression check where the tool architecture allows it. That way the same mistake is less likely to return in a later release.