Checksum Calculator
SHA-1 / SHA-256 / SHA-384 / SHA-512 — computed locally in your browser
Examples
Compute SHA-256 of a file
file: contract.pdf (1.2 MB)
algorithms: SHA-256, SHA-512SHA-256: 9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08
SHA-512: ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ffTwo strong SHA-2 digests are computed from the same file digest for cross-checking, version verification, or signature validation.
Verify a downloaded ISO
downloaded file: ubuntu-24.04.iso
published SHA-256: ...a7b4...Match: ✓
SHA-256: <your computed digest>Compute the digest locally and compare it against the publisher's checksum to confirm the download was not corrupted or tampered with.
About this tool
The Checksum Calculator computes SHA-1, SHA-256, SHA-384 and SHA-512 digests of text and files using the browser's native Web Crypto API. SHA-256 and SHA-512 are recommended for any security-sensitive use; SHA-1 is included for legacy compatibility but should not be used where collision resistance matters.
All hashing runs in your browser. Files are streamed through the SubtleCrypto digest() primitive without being uploaded, so it is safe to verify the integrity of internal documents, installers, and large datasets without leaving a trace.
How to use
Enter your input
Type or paste text, or drop in a file. Large files are supported but held in memory for the read.
Read the digests
The tool computes every selected algorithm at once and shows the hexadecimal digests side by side.
Verify a checksum
Copy a digest and compare it against a publisher's published checksum, or save it as a fingerprint of the content.
Use cases
Verifying downloads
Compute the SHA-256 of an installer, ISO, or archive and compare it against the publisher's published checksum before running the file.
Fingerprinting content
Generate a stable hash for a document, build artifact, or dataset so a duplicate or changed version can be detected without storing the full content.
Checking integrity after transfer
Hash a file before and after copying it to a backup, USB drive, or remote server to confirm the copy matches byte-for-byte.
Common mistakes
Mistake:Using SHA-1 for any security-sensitive purpose.
Fix:SHA-1 has known collision attacks. Use SHA-256 or SHA-512 for integrity verification, signatures, and any security-sensitive work.
Mistake:Expecting MD5 to be available.
Fix:The browser's Web Crypto API does not expose MD5. Use a separate tool for MD5 and never rely on it for security — it is broken for collision resistance.
Mistake:Hashing on the server after upload.
Fix:Hashing on the client (in this tool) means the file never has to be uploaded for verification. Pair the local hash with a published checksum to confirm integrity without leaving your machine.
Frequently asked questions
Related guides
References & standards
Related tools
AES Encryption
Encrypt and decrypt text with AES-GCM and a passphrase, fully in your browser. Uses PBKDF2 key derivation and the Web Crypto API — your data and keys never leave your device.
Basic Auth Generator
Generate an HTTP Basic Authentication header from a username and password. Produces the Authorization header and ready-to-use curl and fetch snippets. Runs fully client-side.
Bcrypt Generator & Verifier
Hash passwords with bcrypt and verify hashes — choose your cost factor (rounds 4–15), get a secure hash instantly, and check whether a password matches a hash. Runs entirely in your browser.
BIP39 Mnemonic Generator
Generate and validate BIP39 seed phrases locally for testing
Client-Side File Encryptor
Encrypt any file with AES-256-GCM and PBKDF2 directly in your browser — no uploads, no accounts, wrong passwords fail loudly.
CORS Header Validator
Validate Cross-Origin Resource Sharing headers for security compliance