Contact
Bug reports, feature requests, "this tool corrupted my JSON" stories, and "this conversion is wrong" reports are all welcome. The fastest way to get my attention is email with a small sample document attached (one I can use to reproduce — preferably one I can keep, but not required).
Reporting a bug
A useful bug report has three things: (1) the URL of the tool you used, (2) what you expected vs. what happened, and ideally (3) a sample document that triggers it. The third one is the most valuable — without a reproducer, I'm guessing.
Files attached to email reports are deleted once the bug is fixed (or once I confirm I can't reproduce it). If your file contains anything sensitive, please redact or synthesise an equivalent; the privacy policy on the site only covers what happens in the browser, not what you choose to send me.
Requesting a tool
Before suggesting a new JSON tool, check the homepage and the footer to make sure it's not already there in slightly different form. For JSON Lines / JSONL workflows specifically (line-mode editing, split, slice, count), use the sister site jsonlkit.com — it's more capable for that format.
What this site doesn't do
It does not fetch JSON from arbitrary URLs (CORS rules block this for most APIs), does not
dereference external $refs over the network (same reason — paste the referenced
schema instead), and does not import JSON straight into a database (that needs a backend).
Each of those is a deliberate gap, not an oversight — they would break the browser-only
promise.
Other sites
Sister tools for adjacent file formats: jsonlkit.com (JSON Lines / NDJSON), csvkit.org (CSV), tomlkit.org (TOML), geojsonkit.org (GeoJSON), pngtoolskit.org (PNG / images). Same browser-only philosophy.