Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
A .patch file is functionally identical to a .diff file — it contains unified diff output showing what lines to add, remove, and change in source files. The distinction is conventional: .diff emphasises "these are the differences," while .patch emphasises "apply these changes."
Before Git, patches were how open-source software was developed. Developers generated patches with `diff -u`, emailed them to mailing lists, maintainers reviewed and applied them with `patch` or `git am`. The Linux kernel was developed this way for years. The workflow still exists — `git format-patch` generates email-ready patches.
Applying a patch: `git apply fix.patch` or `patch -p1 < fix.patch`. The `-p1` strips one directory level from paths — a convention from how patches are typically generated. Always review patches before applying, especially from untrusted sources, since they modify your source code.