Get in touch
A bug to report, a tool to suggest, or a question about how something works. Either channel below reaches us, and we usually reply within a working day or two.
Reporting a bug
Most reports are solved by one small example. The more precisely we can reproduce what you saw, the sooner it is fixed, so the useful things to include are:
- — Which tool, by the name in its heading, and the settings you had on.
- — What you expected, and what happened instead.
- — A small sample input that brings the problem back. Ten lines beat ten thousand.
- — Your browser and version, and whether it happens in another browser.
Nothing you paste into a tool ever reaches us on its own, so a sample only exists if you deliberately attach it. Please replace anything confidential with made-up values first — a bug that depends on real customer data can almost always be reproduced with invented data of the same shape.
Suggesting a tool or a change
Tell us what you were trying to do rather than only what to build. The use case decides the design, and it also decides whether a tool can exist here at all: everything on MyJson runs inside your browser, so anything needing a server, an account or a paid API is out of scope by construction.
Changes to an existing tool are usually quicker than new ones. If a tool nearly does what you need, saying which one and what is missing is the fastest route to it happening.
Common questions
Can you recover something I pasted and lost?
No, and that is by design. Nothing you paste reaches us or is written to storage — it lives in the tab and goes when the tab does. There is nothing on our side to look up.
Is there an API or a command-line version?
No. Every tool is JavaScript running in your browser, so there is no server to call. For scripting, the underlying libraries are worth using directly: js-yaml for YAML, Ajv for JSON Schema, jsonpath-plus and JMESPath for queries.
Can I use MyJson on confidential data at work?
The data never leaves your browser, so nothing is transmitted to us or to anyone else. Whether that satisfies your employer is their call, and the page source is on GitHub if someone needs to check what it does.
A tool gave me the wrong answer. What should I send?
The smallest input that still shows the problem, the tool you used and its settings, and what you expected instead. Please strip anything confidential first — a sample you send us is a sample you have chosen to share.
Can I suggest a tool that is not here?
Yes. Say what you would use it for rather than just naming it, since the use case is what decides whether it can be built to run entirely in the browser.