Drop two ZIPs and see exactly what changed: added files, removed files, files with the same name but different content. Powered by per-entry CRC32.
Per-job file size, entry count, and batch caps for Archive Diff. Limits apply to every Archive tool in JAD Apps; upgrade for larger uploads and bigger batches.
| Tier | Max archive size | Max entries / archive | Max files per batch |
|---|---|---|---|
| Free | 47.7 MB | 500 | 1 |
| Pro | 476.8 MB | 50,000 | 20 |
| Developer | 1.86 GB | 50,000 | 20 |
This tool requires the Pro plan or higher.
Drop archive A and archive B
We compare the two by entry name and CRC32
Get a four-bucket report: added, removed, changed, unchanged — plus an HTML diff table
0 bytes uploaded. Archive Diff Tool runs entirely in your browser using fflate, zip.js, and libarchive WASM. Your archive files never leave your device.
By name match and CRC32 mismatch. Same name + different CRC32 = changed. Different name + same CRC32 = the file was renamed (we flag this as a probable rename).
No — this is an archive-level diff. For text-content diffs of changed entries, extract them and run a text diff tool. The Archive Diff tells you which files to look at.
Yes — both inputs are normalised to entry-name + content-hash before comparing. You can compare a ZIP against a TAR.GZ build of the same source tree to confirm they contain identical files.
SHA-256 every entry inside an archive and group identical files. Spot duplicate logos, libraries, or .DS_Store waste. Reports total bytes recoverable.
Open toolCompute SHA-256 (or MD5, SHA-1) for every entry inside a ZIP and export the manifest as CSV or .sha256sums. Tamper-evident, audit-ready, browser-native.
Open toolInspect every entry in a ZIP and see compression ratios per file plus the overall archive ratio. Spot already-compressed files that don't benefit from re-zipping.
Open tool