Contact Us
Bug reports, feature requests, feedback, or just hello — we read everything.
Email
Email
The best way to reach us is by email:
We try to respond to all messages within a few business days. Replies sometimes get delayed during high-volume periods — we apologize in advance.
What to include
What to include
To help us help you faster, include:
- Bug reports: the tool you were using, the steps to reproduce, and the actual vs expected result. If possible, include a sanitized JSON sample that triggers the bug.
- Feature requests: what you're trying to accomplish, and why the current tools don't solve it. The "why" helps us understand the underlying need, not just the surface request.
- Browser issues: your browser name and version, plus the operating system. JSON tools should work on all modern browsers, so anything that doesn't is a real bug we want to know about.
- Feedback: just say what's on your mind. We genuinely read everything and use it to prioritize improvements.
What we're working on
What we're working on
Active focus areas, in rough order of priority:
- JSON5 and JSONC support in the formatter and validator
- JSONL (newline-delimited JSON) support across all tools
- Custom format extensions for the JSON Schema validator
- JSON Patch (RFC 6902) export from the diff tool
- More blog content covering JSON in specific languages and frameworks
If any of these would help you specifically, let us know — vocal users move features up the queue.
Partnerships and link exchange
Partnerships and link exchange
If you run a developer-focused tools site and want to discuss cross-linking or content collaboration, email us at the address above. We do not accept paid links, paid placements, or paid reviews — we are very strict about this.
Related
Where to go next
- FAQ — most questions are answered there
- How it works — why nothing you paste is uploaded
- Error registry — if you arrived from a parser message