Support
If you have a question about JSON Editor, please check the questions below and the User Guide first. If that doesn’t help, send us an email.
Contact: ssemiya.k@gmail.com (SSEM DEV)
It helps a lot if you include your browser and its version (for example Chrome 141 or Firefox 143), the extension version (see chrome://extensions or about:addons), and what you did in which menu.
Please don’t send JSON that contains company data, personal information, API keys or tokens. A small example that reproduces the problem, or an excerpt with sensitive values removed, is plenty.
Frequently asked questions
Where is my JSON stored? Can the developer see it?
The last document you edited and your settings are kept only in this browser’s extension storage. Nothing is sent to us, and we can’t see it. To keep a file, download it with Save › Save to disk. See the Privacy Policy for details.
I get an error when I click “Save online”.
This menu (and Ctrl+S) is left over from the original project, and we don’t run a server for it — so the document isn’t saved and you see an error. We plan to remove the menu in the next update. To keep your work as a file, use Save › Save to disk.
How do I open a JSON file on my computer?
Choose it with Open › Open from disk, or drag the file onto the editor. The file is read only inside your browser.
“Open url” doesn’t load anything.
Please check the following:
- In Chrome, the first time you open a site the extension asks for permission. If you declined, nothing is loaded — try again and click Allow.
- If the address needs a login, or the server returns HTML (a sign-in page or an error page) instead of JSON, loading fails or shows a syntax error. Open the address in a new tab to check that it really returns JSON.
- The Firefox version currently doesn’t request extra site permissions, so opening a URL may not work. Download the file in your browser and open it with Open from disk.
It’s slow with a very large JSON file.
Everything runs inside your browser, so files of tens of megabytes or more can get slow, especially in the tree view. Look at big files in the code view first and send only the part you need to the tree. Compact JSON also makes the code view lighter.
I see an error like “Parse error”.
That’s a JSON syntax error. Look near the line number in the message. JSON doesn’t allow a trailing comma after the last item, single quotes ('), unquoted keys, or comments (//).
How do I turn on dark mode?
Click the moon (☾) button in the top-right corner of the editor. Click it again (now a sun ☼) to go back to light. Your choice is remembered.
What’s the difference between the Chrome and Firefox versions?
The editor and its features are the same. The Firefox version doesn’t use extra site permissions, so Open url and loading a schema by URL may not work. To use it in a private window in Firefox, allow Run in Private Windows in JSON Editor’s settings in about:addons.
Can I use it in an Incognito (private) window?
In Chrome, go to chrome://extensions › JSON Editor › Details and turn on Allow in Incognito. An editor opened in Incognito uses storage separate from your normal windows, so what you edit there doesn’t show up in a normal window.
How do I uninstall the extension?
Right-click the toolbar icon and choose Remove from Chrome (in Firefox, Remove Extension). This also deletes the document and settings stored in your browser, so download anything you need first. See the User Guide for details.
Version history
2025.11.19 — November 19, 2025
- Moved to Manifest V3 for current versions of Chrome; also available for Firefox
- Dark mode: switch with the button in the top-right corner (your choice is remembered), dark theme for the code editor, better colors, indent guides and selection contrast on dark backgrounds
- The toolbar icon now opens the editor in a new tab instead of a popup
- Works in Chrome Incognito windows (kept separate from normal windows)
- Removed the Help menu and some unneeded text; better alignment of the header logo
JSON Editor is based on the open-source JSON Editor Online 3.7.5 (October 2016) by Jos de Jong. See the Terms of Use for the open-source components and their licenses.