Contact
FormatMyJSON is run by one person, Luiz Torres, and email is the fastest way to reach him. There is no support ticket system and no chatbot — every message lands in a real inbox and gets a real reply.
Replies usually go out within 2 business days. Bug reports get priority.
Reporting a bug in a tool
If the formatter, a converter, or the Base64 tools produce wrong output, the single most useful thing you can send is the smallest input that reproduces the problem. A three-line JSON snippet that converts incorrectly is worth far more than a screenshot of a 5 MB file. Include which tool you used, what you expected, and what you got instead. Browser and OS help too, since everything here runs client-side.
One caveat: never email API keys, tokens, or production data. Strip your sample down to dummy values first — the structure is what matters for reproducing a parser or converter bug, not the real contents.
Corrections to a guide
Spotted a technical error in one of the guides? Point to the article and the sentence, and ideally to the spec section or documentation that contradicts it (RFC 8259, MDN, json.org). Confirmed corrections are fixed in the article itself and the updated date changes — see the editorial standards for how that works.
Feature requests
Suggestions are welcome, with one constraint: every tool on this site runs entirely in the browser, so anything that would require a server to store or process your data will not be built. Within that boundary — a new conversion, an editor option, a keyboard shortcut — go ahead and ask.