What JSON Editor does
JSON Editor keeps an editable document in the page and offers two explicit transformations. Validate and format parses the current text and writes two-space JSON; Minify parses the same document and removes insignificant whitespace.
Typing alone does not continuously parse the document: the status changes to validation pending until one of the actions runs. The copy and download result reflects the current editor text, including unvalidated edits if you have not run an action.
How to use JSON Editor
- Edit or replace the sample JSON document in the text area.
- Select Validate and format to check syntax and apply two-space indentation, or Minify for compact output.
- Correct any parser error before treating the document as valid JSON.
- Copy or download the current document and test it in the application that will consume it.
Important details
Action-based validation
After manual editing, the interface explicitly says validation is pending. A successful formatting or minifying action confirms JSON syntax at that moment.
No schema or semantic model
The editor recognizes JSON syntax only. It does not know required properties, API contracts, data types beyond parsed JSON values, duplicate-key policy, or application-specific constraints.
Practical uses
- Correct a small JSON configuration or request body.
- Switch between readable two-space and compact representations.
- Prepare a validated fixture for a local development test.
Privacy and limitations
The document stays in browser state and is not uploaded to PagesTools. Save the result deliberately; refreshing or closing the page can discard unsaved edits.
There is no autosave, revision history, syntax highlighting, multi-file workspace, collaborative editing, schema validation, key sorting, or recovery after page state is lost. Input is capped at two million characters.