Contact

The fastest way to reach us is email:

[email protected]

We read everything — bug reports, feature requests, tool suggestions, and corrections to documentation are all welcome. Replies usually within a few days.

Found a bug?

Source code is on GitHub. Open an issue with the page URL, what you entered, what you expected, and what you got. Screenshots help, but please don't paste secrets — JWTs, API tokens, and credentials should be redacted.

Looking for a tool we don't have?

Email or open a GitHub issue. We prioritize tools that get high search volume and have clear, well-defined behavior we can implement client-side.

What to include

For a formatter, encoder, or validation bug, include the page URL, a minimal input sample, your expected output, and the browser you used. If the problem is related to JSON parsing, include whether the input should be valid JSON, JSON-like logs, or another data format.

For a new developer utility request, describe the exact input, the output, and any edge cases that should be handled. We prefer small browser-only tools where the behavior can be tested and explained clearly.

Privacy note

Please redact API tokens, JWTs, private keys, passwords, hostnames, customer records, and production logs before sending examples. A minimal fake payload is usually safer and easier to debug than a real production sample.