Get in touch
Need help, found a bug, or have an idea for a tool we should build next? Drop us a line.
What we can help with
Questions about how a specific tool works internally, reports of a tool producing a wrong result, requests for a tool we do not have yet, and anything about privacy or how the site handles data. If you hit a file that will not load or a conversion that looks wrong, telling us what the file was — the format, roughly how large, which browser — is usually enough for us to reproduce it.
Please do not send us your files
We cannot process documents on your behalf, and we would rather not receive them. If a tool is failing on a particular file, describe it instead: the format, the approximate size, and the exact error or wrong output you saw. That is enough to diagnose almost everything, and it keeps your document where it belongs.
Before you write about a broken tool
Two quick checks solve most reports. First, try the tool in a different browser — a content blocker preventing first-party scripts is the single most common cause of a tool that appears dead. Second, for large files, check whether a smaller one works; if it does, you have hit a memory limit rather than a bug, and every tool page documents where those limits sit.
What happens to your message
The form sends what you typed through Web3Forms, which forwards it to our email inbox. We use it only to reply to you and delete it on request. This is the only part of KitYards that transmits anything you write — the tools themselves never do.
Suggesting a tool
These are welcome and several of the existing tools started as somebody's suggestion. The one hard constraint is that it has to run entirely in a browser: if it needs a server to do the work, it does not fit here, however useful it would be.