Contact Localcraft
Email [email protected] for bug reports, privacy questions and tool requests. Every message is read by the person who maintains the site.
The fastest way to reach Localcraft is email: [email protected]. Every message is read by the person who builds and maintains this site.
What to write about
- Bug reports. The most useful reports name the tool, your browser and version, your device, and what happened — for example "the PDF compressor, Chrome on Windows, a 40 MB scanned PDF, the download came out blank". You never need to send the file itself; if an example file would genuinely help, we will ask first, and a small synthetic file with the same problem is better than a real document.
- Privacy and data questions. How a tool handles files, what the site records, or anything on the privacy page you want explained.
- Corrections. A limit, size or rule on a tool page or in a guide that is out of date or wrong. These are especially welcome: accuracy is the point of those pages.
- Tool requests and suggestions. A small, specific job you keep doing by hand is exactly what this site collects. Describe the job, the files involved and what "done" looks like.
- Sponsorship and partnerships. Start with the sponsorship page so you can see the placements on offer, then write to the same address.
What happens after you write
Messages are read in the order they arrive, with bug reports and privacy questions answered first because they can affect other visitors. We do not operate a support desk or a ticket system, and we deliberately do not promise a response time: most messages do get a reply, but feature requests and suggestions may be answered in batches, or may show up as changes to the site rather than as individual replies. If a bug you reported is fixed, the fix ships with the site update rather than as a separate notification — re-checking the tool is the quickest way to see it.
What not to send
Please do not email files containing personal, client or confidential material — the tools on this site process files locally in your browser precisely so that those files never need to travel. For the same reason, never send passwords or API keys; no legitimate reply from us will ever ask for them.