Contact

Corrections and bug reports are read and acted on. Tool suggestions are welcome.

Email

The fastest way to reach me is hello@anaitool.com. There is no contact form here, because a form would mean collecting and storing your message on a server, and the whole point of this site is not doing that.

Reporting a problem with a tool

If a tool gives a wrong result, the most useful report includes the input that caused it. Specifically:

Please do not send real credentials. If a token, key or password triggered the bug, replace the sensitive parts with dummy values of the same shape before sending. A JWT with a fabricated payload reproduces a decoding bug just as well as a real one.

Suggesting a tool

Suggestions are genuinely welcome, and the ones that come up repeatedly get built. What helps most is describing the task rather than the tool — what you were trying to do when you went looking for something and could not find it. That usually points at a better tool than a feature request would.

Tools that fit here share a shape: they do one thing, they can run entirely in the browser, and there is a real explanation to write alongside them. Anything requiring an account, a server-side API key, or storing your data does not fit, however useful it might be.

Corrections

The written sections on every tool page make factual claims, and some of them will be wrong or will go out of date. If you spot something, please point it out — a correction with a source attached is the most valuable message this site receives, and it gets fixed the same day where I can.

What I cannot help with

I cannot debug your codebase, recover data you have lost, or decrypt or reverse anything. On that last point in particular: several tools here are one-way by design, and a hash cannot be turned back into its input by me or by anyone.

Response time

This is a one-person project run alongside other work, so replies take a few days. Corrections and bug reports get answered first.