ZeroServer.tools is built and maintained by Meet Shah. Every message below reaches the same person — there is no support queue and no bot.
The most direct route, and the right one for anything that does not fit the categories below — corrections, press, privacy questions, or legal notices:
Expect a reply within a few working days. This is a project maintained alongside other work, not a staffed helpdesk, so please allow for that — but genuine bug reports get looked at fast.
The most useful message you can send. Include the tool name, exactly what you put in, what it returned, and what you expected instead — a wrong output with a reproducible input gets fixed quickly.
Open a bug report on GitHub →Sponsor placements are a static image and link served from our own CDN — no cookies and no third-party scripts. Rates and placements are on the advertise page.
See advertising options →Need a private or self-hosted version of a tool here, or something similar built from scratch? The project form collects the detail needed to reply usefully.
Start a project enquiry →Two things worth knowing, because they answer most incoming mail:
Email you send is used only to reply to you. It is not added to a mailing list and is not shared. See the Privacy Policy for how data is handled across the site.
The most useful thing to include is the exact input that produced the problem, along with what you expected and what you actually got. A tool giving a plausible but wrong answer is the hardest category to find and the most valuable to hear about — a conversion off in the third decimal, or a validator accepting something it should reject, looks entirely normal until somebody says otherwise.
If the input is sensitive, a reduced version that still reproduces the behaviour is better than the real thing. Please do not paste live credentials, private keys or customer data into an email; nothing here ever needs them, and a bug can almost always be demonstrated with substituted values.
Naming the browser and operating system helps for anything visual or file-related. A surprising share of image and clipboard issues turn out to be specific to one browser's implementation rather than to the tool itself.
This is a one-person project, so replies usually take a few days rather than the same hour, and there is no support queue behind the address. Bug reports are prioritised over feature requests, because a tool giving a wrong answer is doing active harm while a missing feature is only an absence.
Requests for a new tool are welcome and are answered honestly — many turn out to be covered by an existing tool under a different name, and some are genuinely better served by something that already exists elsewhere. Being told so is a more useful answer than a place in a queue.