Skip to content
Aback ZIP

Compare ZIP

Compare two ZIP archives file by file: added, removed, changed and identical entries, matched by path. A quick comparison uses stored sizes and CRC-32 values; a deep comparison decompresses both and compares SHA-256 hashes.

Compare ZIP

Match files by path and see what was added, removed or changed between two archives.

Processed locally

Archive A

Drop archive a

ZIP archive

Files stay on your device. Nothing is uploaded.

Archive B

Drop archive b

ZIP archive

Files stay on your device. Nothing is uploaded.

How to use Compare ZIP

  1. 1

    Add two ZIPs

    Drop the older archive as A and the newer one as B, or pick them with the file picker.

  2. 2

    Choose quick or deep

    Quick compares stored sizes and CRC-32 values from each archive's index. Deep decompresses both sides and compares SHA-256 hashes.

  3. 3

    Review the differences

    Every path is marked identical, changed, only in A, only in B or unknown. Filter to see just what changed.

  4. 4

    Export

    Save the comparison as CSV for a changelog, a ticket or a spreadsheet.

Why use Aback ZIP's Compare ZIP?

Quick mode reads only the index

Sizes and CRC-32 values are already stored in every ZIP's index, so a quick comparison needs no decompression and finishes fast even for large archives.

Deep mode with SHA-256

For maximum confidence, both archives are decompressed and every file hashed with SHA-256. This also works for AES-encrypted entries when you provide the passwords.

Focus on what changed

Filter by status to hide the thousands of identical files and see only what was added, removed or modified.

Processed locally

Both archives are read in your browser and nothing is uploaded, which matters when you are comparing unreleased builds or private backups.

Common use cases

Release diffs

Compare app-1.4.zip with app-1.5.zip to confirm only the expected files changed and nothing unexpected slipped into the release.

Backup verification

Compare yesterday's backup with today's to see which files were added, deleted or modified in between.

Client revisions

A client sends back an edited version of your delivery. See exactly which files they changed before you merge their edits.

“Works on my machine” builds

Compare a CI artifact with a local build to find the file that differs and explains the bug.

Check a processed archive

After Clean ZIP or Merge ZIP, compare the result with the source to confirm only the intended entries were removed or added.

Resubmitted work

See which files a student or contributor changed between two submissions, without extracting either one.

About Compare ZIP

Quick vs deep comparison

QuickDeep
What is comparedStored size and CRC-32 from each archive's indexSHA-256 of each file's decompressed contents
SpeedFast; nothing is decompressedSlower; every file on both sides is decompressed
Encrypted filesWorks when entries store a CRC-32; AE-2 AES entries don'tWorks with the passwords
Best forEveryday checksAE-2 entries and maximum confidence

Both modes compare the uncompressed contents. The same file compressed at different levels, or stored in one archive and deflated in the other, still counts as identical.

What the statuses mean

  • Identical: same path, same contents.
  • Changed: same path, different contents.
  • Only in A: the path exists only in the first archive (removed in B).
  • Only in B: the path exists only in the second archive (added in B).
  • Unknown: there isn't enough information to decide, typically AES AE-2 entries that store no CRC-32. Run a deep comparison with the passwords.

Files are matched by their exact path. A file that was renamed or moved appears once as “only in A” and once as “only in B”.

Limitations

  • Files are matched by path, so renamed or moved files show up as one removal and one addition.
  • The comparison is about file contents. A file whose only change is its modification date or permissions counts as identical.
  • It tells you which files differ, not what changed inside them; there is no line-by-line diff.
  • CRC-32 is excellent at catching accidental changes but is not designed to resist deliberate tampering. Use deep mode when that matters.
  • Deep mode decompresses both archives in browser memory and may struggle with multi-gigabyte archives on phones and low-memory devices.

Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.

Compare ZIP: frequently asked questions

No. Both archives are read in your browser on your device, and the comparison is computed locally. Nothing is sent to a server and no account is needed.