KordFree diff tool
Compare two JSON files
Diff two JSON files in your browser, free, no account: compare two revisions of a config or export as structured JSON, with a raw text view when you want the lines. Built by Kord; opens with a sample config pair loaded.
Free, no account. Opens with a two-revision configuration file loaded.
Instrument configs, controller exports, calibration files, API payloads - a lot of engineering state serializes to JSON, and two revisions of it raise the usual question in an unusual format: what changed, and does it matter?
Drop both files here and read the comparison in the browser - structured, so you see what changed where in the document, with the raw text a click away when you want the exact lines. Free, no account.
What the comparison shows
What you get on screen once both files are in, and why each piece is there:
- Structure first. The comparison follows the JSON, so a changed value reads as the key that changed, not as line 4,081.
- Text when you want it. The raw view is there for the times the exact bytes are the point.
- For files no one hand-edits. Machine-written JSON - exports, configs, state dumps - is exactly the JSON humans end up having to compare.
How to compare two JSON files
Three steps, none of which is signing up:
- Open the diff tool - it loads with a two-revision configuration file already compared, so you see the result shape before committing your own files.
- Drop your two JSON files into the Before and After slots - up to 25 MB each.
- Read the comparison. If someone else needs to see it, Share turns it into a link.
FAQ
The questions people ask before dropping real files on a free tool, answered plainly:
Is it free?
Yes. No account, no trial clock, no watermark. The tool exists because we build Kord, version control for engineering document sets, and a diff you can run in ten seconds explains the product faster than any brochure.
Do my files get stored?
Files are kept only as long as it takes to draw the comparison. Most formats render in your browser; Word and PowerPoint are converted to a preview by our servers in memory, and a file too big to ride a request travels through a short-lived upload that is deleted automatically. There is no account, so there is no history to attach anything to. The longer answer is at work.withkord.com/security.
Why not just use a code diff?
If you live in a terminal, do - git diff and jq get far. This is for the times the JSON arrived by email, the machine is not yours, or the person who needs to see the change would not thank you for a patch file.
When two files aren't the real problem
A one-off diff answers a one-off question. If your team compares JSON files every revision cycle - and the revision that matters sits next to drawings, specs, and calc sheets that have to agree with it - that is the job Kord exists for: version control on the whole document set, this same visual comparison between any two revisions, and review sessions with sign-off before anything is issued. The longer argument is in Git for documents.
Compare other formats
The same tool reads eleven formats - the full list is on the compare index. Nearby: Compare two Rockwell PLC exports · Compare two SVG files · Compare two Excel files.