Text & Config Diff
Find exactly what changed between two versions of a file, a config or a JSON document. Changed words are highlighted, and you can download the changes as a standard patch.
- Files stay in your browser
- JSON-aware comparison
- .diff and .patch download
Original
Changed
Comparing config files
- Ignore changes in spacing treats
listen 80andlisten 80as the same. Ignore all whitespace goes further, likediff -w. Leave both off for YAML and Python, where indentation matters. - Compare as JSON reads both sides, sorts every object's keys and lays them out the same way, so a reordered or reformatted file only shows real changes.
- We warn you when one file has Windows line endings (CRLF) and the other Unix (LF). That alone can break shell scripts and some config files.
- Remove passwords, API keys and other secrets before sharing a diff with anyone.
Using the patch file
- The download is a standard unified diff with 3 lines of context, the format of
diff -uandgit diff. - Apply it on Linux with
patch -p1 < changes.diff, or in a Git repository withgit apply changes.diff. Rename the files in the patch header if your paths differ. - If you used an ignore option, lines that differ only in the ignored way aren't in the patch, so it may not recreate the changed file exactly.
- Comparing happens in your browser. Your text and files are never uploaded.