ZIP Content Compare
Compare exact file paths and decoded SHA-256 content inside two ZIPs, with added, removed, changed and unchanged files in a downloadable report.
This tool processes its input contents in your browser instead of sending them to a processing service. Page, asset and fixed usage-measurement requests are described on the Privacy page.
Compare exact file paths and decoded content inside two bounded ZIP archives, with a complete added/removed/changed/unchanged JSON report.
How to use it
- 1Select the before and after classic ZIP archives, at most 10 MiB each.
- 2Compare their validated decoded member content locally.
- 3Inspect file statuses and download the complete JSON report.
What happens to your data
Both archives are checked and hashed in a local worker. Member bytes and paths are not uploaded; the downloaded report contains filenames and fingerprints.
Last updated November 2026
Two ZIP archives can contain the same files while their binary bytes differ because of compression, timestamps or entry order. ZIP Content Compare opens each bounded archive locally and compares the exact member path plus a SHA-256 fingerprint of its decoded bytes. You receive an added, removed, changed or unchanged classification for each file, rather than an unexplained difference between two archive blobs.
How it works
Choose the before and after archives, then compare. File paths are case-sensitive and include directories: docs/readme.txt is different from README.txt. Two same-path members with identical decoded content are unchanged even if compressed differently. A renamed file appears as a removal and addition; there is no similarity-based rename guess. A same-path content difference is changed. Directory-only entries, timestamps, permissions, archive order and ZIP comments do not form part of the comparison.
Before hashing, the ZIP reader checks the classic central directory and member bounds, rejects ambiguous or unsafe names, and verifies decoded member sizes and CRC-32. The reader does not trust a filename sanitized by another library: parent traversal, conflicting case-normalized names and inconsistent local metadata cause an error. CRC-32 checks archive integrity; SHA-256 is used for the content comparison. Neither is a malware scan or a signature authenticity check.
Each input is at most 10 MiB, with up to 100 entries and 20 MiB expanded content per archive. STORE and DEFLATE are supported. ZIP64, encryption, split archives, unsupported flags and other compression methods fail rather than appearing to compare successfully. The entire comparison runs in a separate local worker, which you can cancel and which stops after 20 seconds. This is intentionally a bounded tool for small release bundles, document packages and project exports, not a multi-gigabyte backup auditor.
The report contains every compared path, status, decoded byte size and the before/after SHA-256 values. The preview includes every accepted file, and the JSON download retains the complete report. Files inside the archives are not opened, previewed, executed or uploaded. A result of unchanged means the decoded bytes at that exact path have the same fingerprint; it does not establish that a document is safe or factually correct.
Changing either selected archive invalidates the previous report. Clear stops the current worker and removes the current result, while a late worker response cannot replace newer input. The tool does not remember your archives after the page is closed. Downloaded reports can reveal project filenames, so review them before sharing. For a simple comparison of the archive bytes themselves, use Binary File Compare instead; this tool answers the different question of what changed inside.
Common use cases
- Review which assets changed between two small application bundles.
- Compare two document packages without differences caused only by compression.
- Check a ZIP export before replacing an earlier version.
Frequently asked questions
Why are two different ZIP files shown as unchanged inside?+
ZIP metadata and compression can differ while each decoded file remains identical. This comparison deliberately ignores those archive-level differences.
Does it detect renamed files?+
No. Matching uses exact case-sensitive paths. A rename is an added path plus a removed path, even when their hashes match.
Is every ZIP variant supported?+
No. The declared classic STORE/DEFLATE subset and explicit resource limits apply. Unsupported or corrupt archives fail the full comparison.
Standards and limitations
Related tools
JSONC to JSON
Convert commented JSON to strict JSON while preserving quoted strings and exact numeric tokens locally.
vCard Generator
Create a UTF-8 vCard 4 contact file with safe folding and download it locally.
Subtitle Converter
Convert plain SRT and WebVTT locally, with cue previews and no silent metadata loss.
ZIP Creator
Create a ZIP locally with editable archive paths, Store or Deflate compression, and exact file bytes.