Skip to content
Aback ZIP

ZIP Checksum

Compute checksums for a ZIP and for every file inside it without extracting anything to disk: SHA-256, SHA-1, MD5 and CRC-32. Export a sha256sum-style manifest, CSV or JSON, or check a value you were given.

ZIP Checksum

Hash the archive and every file inside it. Nothing is extracted to disk.

Processed locally

Drop a ZIP (or any file)

Checksums for the file itself and every file inside a ZIP

Files stay on your device. Nothing is uploaded.

How to use ZIP Checksum

  1. 1

    Add a file

    Drop a ZIP, or any other file if you only need its own checksum.

  2. 2

    Choose algorithms and scope

    Pick any combination of SHA-256, SHA-1, MD5 and CRC-32, for the archive file, every file inside it, or both.

  3. 3

    Compute

    Files inside the archive are decompressed and hashed as a stream in a background worker. Nothing is written to disk.

  4. 4

    Verify or export

    Paste an expected value to check for a match, or export a sha256sum-style manifest, CSV or JSON.

Why use Aback ZIP's ZIP Checksum?

Four algorithms

SHA-256 for verification you can rely on, SHA-1 and MD5 for matching older published checksums, and CRC-32 for quick corruption checks.

Hashes for every file inside

Get a checksum for each file in the archive without extracting anything, so you can compare contents across different archives or against files on disk.

Paste to verify

Paste the value from a download page or an email and see at a glance whether it matches. No more comparing 64 hex characters by eye.

Export a manifest

Save results as a sha256sum-style text manifest, CSV or JSON. Hashing runs locally in your browser and nothing is uploaded.

Common use cases

Verify a download

A project publishes a SHA-256 next to its ZIP. Paste it in and confirm the file you downloaded is exactly the one they released.

Release manifests

Publish a SHA256SUMS file for every file in a release archive so users and package maintainers can verify what they extract.

Backup integrity records

Export per-file hashes when you create a backup, then hash it again a year later to confirm nothing changed.

Proof of what was delivered

Keep a manifest of every file you sent a client, with hashes, as a record of exactly what the delivery contained.

Confirm a round trip

Per-file hashes from two different archives of the same files should match, even if the archives themselves differ. For a side-by-side view, use Compare ZIP.

Any file, not just ZIPs

Need the SHA-256 of an installer, an ISO or a PDF? Drop it in and get the file's own checksum.

About ZIP Checksum

Which algorithm to use

AlgorithmLengthUse it for
SHA-25664 hex charactersVerifying downloads and releases; the default choice
SHA-140 hex charactersMatching older published checksums; no longer collision-resistant
MD532 hex charactersLegacy checksums and accidental-corruption checks; not safe against tampering
CRC-328 hex charactersFast corruption checks; the same value ZIP stores for each file

Archive hash vs file hashes

The checksum of the ZIP file changes whenever anything about the archive changes: compression level, file order, timestamps, comment. Two archives with identical contents can therefore have different archive hashes. Per-file hashes depend only on each file's contents, which makes them the right thing to compare across different archives of the same files.

The manifest uses the familiar format of a hash, two spaces and the path, one file per line. For example, the SHA-256 of an empty file:

e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  notes/empty.txt

Limitations

  • Per-file hashes require decompressing each file, so entries using Deflate64 or PPMd can't be hashed individually. The archive-level hash always works.
  • For files that aren't ZIP archives, including TAR, only the file's own checksum is computed.
  • MD5 and SHA-1 are offered for compatibility with older published values. They are not reliable protection against deliberate tampering; prefer SHA-256.
  • Hashing is streamed, but very large archives still take time, and phones and low-memory devices may struggle with multi-gigabyte files.

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

ZIP Checksum: frequently asked questions

No. Hashes are computed in a Web Worker in your browser, on your device. Neither the file nor the checksums are uploaded, and no account is needed.