Drop one or many files, or paste text, to compute BLAKE3, SHA-256, SHA-512, SHA-1, MD5, or CRC32 hashes — then paste an expected checksum to verify a download. Everything runs locally — nothing is ever uploaded.
Files never leave your device
Drop files to hash, click to browse, or paste
What This Tool Does
This tool computes cryptographic hashes and checksums for any file or piece of text — drop a file or type a string, pick one or more algorithms, and get back a hex digest you can copy. Select several algorithms at once and each result appears with its own copy button, so you can grab a SHA-256 and a BLAKE3 in a single pass.
Everything happens on your device. There's no upload step and no size limit imposed by a backend — the only ceiling is what your browser's memory can hold, which makes it practical even for large files you'd rather not wait to upload to a website.
Supported Algorithms
Algorithm
Output size
Best for
BLAKE3
256-bit (64 hex chars)
Fastest option here; great default for large files
SHA-256
256-bit (64 hex chars)
Widely published standard, a safe general-purpose default
SHA-512
512-bit (128 hex chars)
Extra margin when you want a longer digest
SHA-1
160-bit (40 hex chars)
Legacy compatibility only — known collision weaknesses
MD5
128-bit (32 hex chars)
Legacy compatibility only — not for security-sensitive checks
CRC32
32-bit (8 hex chars)
Fast non-cryptographic checksum for catching accidental corruption
Tip:For confirming a download arrived intact or that two copies of a file are identical, BLAKE3 or SHA-256 are the right choice. Reach for MD5, SHA-1, or CRC32 only when a tool you don't control still asks for one of those specifically.
Which Algorithm Should I Use?
For anything where integrity or authenticity matters — confirming a download wasn't corrupted or tampered with, fingerprinting a file, or comparing two copies — reach for BLAKE3 or SHA-256. Both are modern and cryptographically secure; BLAKE3 is the fastest option here and a great default for large files, while SHA-256 is the more widely published standard you'll often see listed next to a download.
MD5, SHA-1, and CRC32 are here for legacy compatibility only. Use them when some other tool or system you don't control specifically asks for one of them — for example matching an MD5 that a vendor still publishes. They're fine for a quick "did this file change" check, but their known weaknesses (or, for CRC32, the fact that it isn't cryptographic at all) make them the wrong choice for security-sensitive work.
Verifying a Download
Download pages often publish a checksum (usually SHA-256) next to the file. To confirm your copy arrived intact, drop the file here and paste the published value into the Expected hash field. The tool compares it against every digest it computed — a green badge names the matching algorithm, and the matching row is highlighted. No match means the bytes you received differ from what the publisher hashed: a corrupted download, a truncated file, or tampering.
The comparison ignores case, so checksums copied as uppercase hex work as-is.
Your Files Never Leave Your Device
Hashing runs through a small WebAssembly module loaded into your browser tab. When you drop a file, its bytes are read locally and handed to that module — they're never sent anywhere over the network. Closing the tab discards everything; there's nothing left behind on a server because there was never a server involved in the first place.
If you need to check how strong a password is or generate a secure password hash, see the Password strength & hash generator. If you need to encrypt a file so only someone with the password can open it, see Encrypt & decrypt files — both run on-device the same way this tool does.
Frequently asked questions
Is this hash and checksum tool really free?
Yes. There's no sign-up, no watermark, and no limit on how many files or how much text you can hash. The tool runs entirely in your browser, so there's no server cost to recoup from you.
Do my files get uploaded anywhere to be hashed?
No. Every hash is computed locally using WebAssembly running inside your browser tab. Your files never travel over the network, so nothing ever reaches a server — this matters most for large files you wouldn't want to wait to upload anyway.
What is BLAKE3, and why is it faster than SHA-256?
BLAKE3 is a modern cryptographic hash function designed for speed: it processes data in parallel across CPU cores and uses a tree structure internally, so it can hash a large file several times faster than SHA-256 while remaining just as secure. It isn't built into browsers' native Web Crypto API, which is why this tool runs it through WebAssembly.
What's the actual difference between the hash algorithms offered here?
BLAKE3 and SHA-256/SHA-512 are modern, cryptographically secure choices suitable for checking integrity or authenticity today. SHA-1 and MD5 are older algorithms with known collision weaknesses — still fine for basic "did this file change" checks, but not for security-sensitive work. CRC32 isn't cryptographic at all; it's a fast error-detection checksum meant to catch accidental corruption, not tampering.
What does a checksum actually tell you?
A checksum is a fingerprint of a file's exact bytes. Compute a file's hash here and compare it against the checksum published alongside a download: if the two hex strings match, your copy is byte-for-byte identical to the original; if they differ, the file was corrupted in transit or tampered with. It's how you confirm a download arrived intact before trusting it.
Can I hash plain text as well as files?
Yes. Switch to the text tab and type or paste any string, then click Compute hash — the same set of algorithms runs on it in the browser, with no need to save it as a file first.
Can I generate more than one hash algorithm at once?
Yes. Select as many algorithms as you like before hashing a file or piece of text, and every result appears together with its own copy button, so you can grab a SHA-256 and a BLAKE3 in a single pass.
How do I verify a file I downloaded?
Compute the file's hash here, then paste the checksum published by the download page into the Expected hash field. If one of the computed digests matches, you'll see a green badge naming the algorithm — the file arrived intact. If nothing matches, the file is corrupted or was tampered with; download it again from a trusted source.
Can I hash several files at once?
Yes. Drop as many files as you like — each one is queued and hashed in turn, and every file gets its own result card. The Expected hash field checks against all of them, so you can spot which file in a batch matches a published checksum.