How to use the JSON viewer and diff tool

1. Paste JSON into the editor
Insert API responses, config files, or event payloads. The viewer parses JSON and renders a collapsible tree for easier navigation than raw text.
2. Explore keys and copy JSONPath
Expand nested objects and arrays, then click a key to copy its JSONPath. This speeds up writing queries in observability or test tools.
3. Switch to diff mode
Provide before and after JSON documents to highlight added, removed, and changed lines side by side.
4. Share findings safely
Because parsing is local, you can inspect production-shaped payloads in the browser without uploading them to a third-party formatter.

Common use cases

API response inspection
Quickly locate fields in large nested responses returned by GraphQL, REST, or webhook deliveries.
Configuration reviews
Compare JSON config exports from staging and production to spot unintended drift before deploys.
Test failure analysis
Diff expected versus actual fixture JSON in failing integration tests without leaving your browser.
Event-driven debugging
Collapse noisy metadata in message bus payloads to focus on business-critical attributes.
Documentation examples
Pretty-print sample payloads when writing API guides or internal playbooks.

Is there a file size limit?: Very large documents may slow your browser because parsing happens locally. Split huge payloads when possible.
Does diff mode ignore key order?: Diff compares textual JSON structure line by line. Reordered keys may appear as changes even when values are identical.
Can I format minified JSON?: Yes. Paste minified JSON and the tree view expands it into a readable hierarchy automatically when parsing succeeds.
Is my JSON uploaded?: No. Parsing and diffing remain entirely client-side.