Skip to content
zspace tools

Developer Tools

File Hash Generator & Checksum Verifier

Generate SHA-256, SHA-384 or SHA-512 checksums for files and text, and check a download against the checksum its publisher lists. Files are hashed in your browser — nothing is uploaded.

Runs in your browser

Features

What you get

  • SHA-256, SHA-384, SHA-512

    The SHA-2 family used by software publishers, plus SHA-1 for checking legacy checksums — clearly labelled as unsuitable for modern security.

  • Files and text

    Hash many files at once, each with its name, size and hash, or hash typed text as UTF-8.

  • Checksum verification

    Paste the expected value — or a whole SHA256SUMS list — and each file shows Match or Does not match. Letter case and spaces are ignored.

  • Large files, low memory

    Files over 64 MB are read in chunks with live progress, up to 4 GB each.

  • Clear validation

    An expected checksum of the wrong length or with invalid characters is flagged — including when it belongs to a different algorithm.

  • Export

    Copy one hash, copy all in sha256sum format, or download a CSV of names, sizes, hashes and results.

How to use

How to use the File Hash Generator & Checksum Verifier

Files up to 64 MB are hashed with the browser's Web Crypto API. Web Crypto needs the whole input in memory and can't stream, so larger files (up to 4 GB) are read in 4 MB chunks and fed to an incremental implementation of the same FIPS 180-4 algorithms; both paths are tested against reference implementations and give identical results. Hashing runs in a background worker, so the page stays responsive and shows progress.

  1. 01

    Add files or text

    Drop one or more files, or switch to Text and type or paste.

  2. 02

    Pick the algorithm

    Choose the same algorithm as the checksum you're checking against — usually SHA-256.

  3. 03

    Compare and export

    Paste the expected checksum to verify it, then copy the hashes or export a CSV.

Examples

Worked examples

  • Empty input

    The SHA-256 of an empty file or empty text is always e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.

  • One letter changes everything

    SHA-256 of “abc” starts ba7816bf…, while “abd” starts a52d159f… — completely different.

  • Checking a download

    Paste the line “<checksum> setup.exe” from the publisher's SHA256SUMS file, drop setup.exe, and the result shows Match or Does not match.

Technical specifications

Algorithms
SHA-256, SHA-384, SHA-512 · SHA-1 (legacy)
Engine
Web Crypto (≤ 64 MB) · incremental FIPS 180-4 (larger files, or no Web Crypto)
Max file size
4 GB per file · 50 files at a time
Expected-value formats
Hex digest, sha256:<hex>, GNU (sha256sum) and BSD checksum lists
Text encoding
UTF-8
Output
Lowercase or uppercase hex · CSV export
Not included
Password hashing, HMAC, MD5
Processing
In your browser (Web Worker)

Privacy

Files and text are hashed on your device. File contents, names and hashes are never uploaded or sent to analytics.

Read the full privacy policy.

FAQ

File Hash Generator & Checksum Verifier questions

A hash (or checksum) is a fixed-length fingerprint calculated from a file's contents: change one byte and the hash changes completely. ZSpace Tools' File Hash Generator & Checksum Verifier calculates SHA-256, SHA-384, SHA-512 or legacy SHA-1 hashes for one or many files or a piece of text, and compares them with an expected checksum. Hashing is not encryption — it can't be reversed to recover the file.

Files up to 64 MB are hashed with the browser's Web Crypto API. Web Crypto needs the whole input in memory and can't stream, so larger files (up to 4 GB) are read in 4 MB chunks and fed to an incremental implementation of the same FIPS 180-4 algorithms; both paths are tested against reference implementations and give identical results. Hashing runs in a background worker, so the page stays responsive and shows progress.

Drop the downloaded file here with SHA-256 selected, then paste the checksum from the publisher's website into “Expected checksum”. A Match means your file is byte-for-byte identical to the one the checksum was made from.

It proves the file wasn't altered or corrupted relative to the checksum you compared. It only proves authenticity if that checksum came from a source you trust — for example the publisher's official HTTPS site, ideally with a signature — because anyone who can swap a file may also swap a checksum published next to it.

No. Encryption can be reversed with a key; a hash is a one-way fingerprint and can't be turned back into the file.

Use whatever the publisher lists — most use SHA-256. SHA-384 and SHA-512 are also secure. SHA-1 is a legacy algorithm and should not be used for modern cryptographic security; use it only to check an existing SHA-1 checksum.

Hashes depend on exact bytes. Text here is UTF-8 with LF (\n) line breaks; a file with CRLF line breaks, a trailing newline (as echo adds) or a BOM gives a different hash. Hash the file itself for an exact comparison.

Up to 4 GB per file. Files up to 64 MB use the browser's built-in Web Crypto; larger files are read in 4 MB chunks so memory use stays low, with a progress bar.

No. Storing passwords needs a slow, salted password-hashing function such as Argon2, scrypt or bcrypt — not a fast checksum like SHA-256. This tool is for file and text integrity checks.