Paste or upload the first JSON here
Paste or upload the second JSON here
This JSON diff tool is designed for developers, QA engineers, and data analysts who need to quickly spot differences between two JSON datasets. It is straightforward to use: paste the "original" JSON into the left input box, paste the "compare" JSON into the right input box, and click the Compare button.
Format: If your JSON is a single compressed line, click the Format button to automatically add indentation for easier reading and editing. The formatting preserves the original data structure — only whitespace is adjusted.
File Upload: You can upload local .json or .txt files directly. The tool reads the file content and populates the corresponding input box automatically. Drag-and-drop is also supported for quick uploads.
Reading Results: The comparison result is displayed as a tree. Green means added (present in the right JSON but not the left), red means removed (present in the left JSON but not the right), yellow means modified (same key but different value). Click the arrow next to each node to expand or collapse child nodes.
Export: After comparison, click the Export Diff button to save the results as a JSON file containing the full diff path, type, and comparison values — perfect for archiving or sharing with your team.
The JSON diff tool is widely used in software development and data analysis. Here are some typical scenarios:
API Response Comparison: When upgrading or refactoring an API endpoint, compare the old and new response payloads to ensure field compatibility and data consistency. Verify that newly added fields do not break client parsing, and confirm that deprecated fields are properly removed.
Config Change Review: Before deployment, compare configuration files between production and testing environments to quickly spot configuration drift. This is especially valuable in microservices architectures where many services have their own configs.
Database Snapshot Comparison: Compare JSON exports from different time periods to analyze data change trends. For example, compare user behavior log JSON snapshots to track changes in registrations, active users, and churn over time.
How JSON Diff Works: The tool uses a recursive depth-first traversal algorithm to compare two JSON objects. For objects, it compares keys one by one. For arrays, it compares elements by index. When types differ (e.g., string vs. number), the field is marked as modified. The algorithm runs in O(n) time, where n is the total number of nodes.
JSON Diff vs. Git Diff: Git diff operates on a line-by-line text basis, which is great for code files. JSON diff operates on a structural basis, catching semantic differences that text diffs miss. For example, changing the order of object keys is flagged by Git but is usually semantically irrelevant in JSON — this tool ignores key-order differences.
Related Tools: In addition to this online tool, you can use command-line utilities like jq (a lightweight JSON processor), the json-diff npm package, or delta (a syntax-highlighting diff viewer). For automated CI/CD pipelines, jq combined with shell scripts is the most common approach for automated diff detection.
The tool runs entirely in your browser and supports JSON files up to several megabytes. For extremely large files (over 10MB), consider splitting them into smaller chunks or using command-line tools like jq or json-diff. In practice, the tool handles files under 5MB smoothly on most modern computers.
By default, the tool compares array elements by index — the first element is compared with the first, the second with the second, and so on. This means array order affects the comparison result. If you need to compare arrays ignoring order, consider converting the array into an object keyed by a unique identifier before comparison.
Green means added (exists in the right JSON but not the left), red means removed (exists in the left JSON but not the right), yellow means modified (key exists but value differs), and gray means unchanged. The color scheme follows the convention used by Git and other version control systems for quick visual scanning.
No. This tool runs entirely in your browser. All processing happens locally on your device — no data is uploaded to any server. You can safely compare JSON containing sensitive information without worrying about data leakage.
Yes. You can paste JSON text into the input boxes, or click the upload button to select a local .json or .txt file. The tool reads the file automatically and populates the corresponding input. Drag-and-drop is also supported for quick file uploads.
Yes. After comparing, click the Export button to save the diff results as a JSON file. The exported file contains the full diff path, type, and comparison values, making it easy to archive or share with your team.