Contact us
We would love to hear from you—whether you have feedback, found a bug, or want to suggest a new tool for DevToolsHub. Detailed messages get faster answers than a single line saying something is broken, because we can reproduce the issue and prioritize a fix.
What to include in bug reports
- The exact tool URL (for example the JSON formatter or JWT decoder page).
- Your browser and operating system version if the problem is visual or performance-related.
- Steps to reproduce, using redacted or synthetic sample data—never production secrets.
Feature suggestions
We prioritize additions that many developers use weekly: encoders, formatters, decoders, and comparators that stay useful without a backend account. If you propose a niche corporate integration, we might decline—but we still appreciate hearing what workflows teams are trying to streamline.
Response time
We read every message when we can. This is an independent project, so during busy periods a reply may take several days. For security issues, please avoid sharing sensitive tokens or private keys in email; describe the vulnerability and affected component instead.