Skip to main content
ZMakeMyZip
job card · 11 of 19 · peek

Checksum Archive.

Compute SHA-256 and SHA-1 of a ZIP archive and every file inside. Verify integrity, compare two copies, or publish a manifest alongside a download.

routeclient-local
upload0 B
formatsZIP

1. Select a ZIP file

Drop a ZIP file here or click to browse

Select a file

Up to 2 GB per file.

2. Compute hashes

Hashing runs locally via the Web Crypto API. The archive file and every entry are digested with SHA-256 and SHA-1. Nothing is uploaded.

instructions · step by step

How to use this tool

Hash a ZIP archive and every file inside with SHA-256 and SHA-1, locally in your browser.

  1. Open the Checksum Archive tool

    Visit makemyzip.com/checksum-archive. Hashing uses the browser’s built-in Web Crypto API; no extra libraries needed.

  2. Drop a ZIP file

    Drag the archive onto the dropzone or click to pick it. The file is read into memory for hashing — nothing is uploaded.

  3. Compute the hashes

    Click Hash archive + entries. The tool first digests the whole archive, then iterates every entry and computes SHA-256 and SHA-1 for each.

  4. Copy or download the manifest

    Copy individual hashes with the per-row buttons, or download a plain-text SHA-256 manifest matching the standard sha256sum format.

questions · from the clerk's desk

Frequently asked questions

What are these hashes useful for?

Integrity checks and deduplication. If two archives share the same SHA-256, they are identical. If a single file inside matches a published hash, it has not been modified or corrupted in transit.

Why SHA-256 and SHA-1?

SHA-256 is the modern integrity standard and the one Linux distros, GitHub Releases, and package managers publish. SHA-1 is still common for legacy verification and matches Git’s object hash. Both are free via the Web Crypto API.

Why not MD5?

MD5 is not available in the browser’s Web Crypto API. Adding it would require shipping extra code for an algorithm that is no longer considered secure. SHA-1 plus SHA-256 covers the real use cases.

Is my archive uploaded?

No. The archive is read into the browser tab and hashed there. The hashes are the only thing you see — and the only thing that could ever leave the page, and only if you copy them yourself.

3 picks