Cryptographic Hash & Checksum Calculator
Compute SHA-1, SHA-256, SHA-384, and SHA-512 hashes for text or a file, and compare against an expected checksum — entirely in your browser.
Drop a file here, or click to choose one.
No file chosen.
| Algorithm | Hash | Copy |
|---|---|---|
| SHA-1 | 943a702d06f34599aee1f8da8ef9f7296031d699 | |
| SHA-256 | 315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894edd3 | |
| SHA-384 | 55bc556b0d2fe0fce582ba5fe07baafff035653638c7ac0d5494c2a64c0bea1cc57331c7c12a45cdbca7f4c34a089eeb | |
| SHA-512 | c1527cd893c124773d811911970c8fe6e857d6df5dc9226bd8a160614c0cd963a4ddea2b94bb7d36021ef9d865d5cea294a82dd49a0bb269f51f6e7a57f79421 |
About this tool
How to use it
- Switch to the Text tab and type or paste text, or switch to File and drop a file (or click to choose one).
- SHA-1, SHA-256, SHA-384, and SHA-512 hashes compute automatically — click Calculate Hashes to re-run manually at any point.
- Copy any individual hash with its Copy button.
- To verify a download, paste the checksum the publisher gave you into the Compare field — it's checked case-insensitively against every hash in the table above and tells you which algorithm (if any) matches.
Why it matters
A checksum only proves anything if you actually compare it against a hash computed from the exact same bytes — a file that was corrupted, tampered with, or downloaded incompletely will hash differently even if it looks fine and opens normally. Computing all four common algorithms at once means you don't need to know in advance which one a publisher used.
When to use it
Verifying a downloaded file matches the checksum a publisher (or a package registry) published for it. Checking that two files are byte-for-byte identical without doing a full diff. Generating a quick fingerprint of a piece of text or config for comparison later.
Good to know
Uses the browser's native Web Crypto API (SubtleCrypto) for SHA-1/256/384/512 — the same implementation your browser already trusts for TLS — not a hand-written hash function. MD5 is deliberately not offered: it isn't in the Web Crypto API, and a hand-rolled MD5 implementation is exactly the kind of thing this project won't ship without being able to verify it as rigorously as a native, browser-audited implementation. SHA-1 is included for compatibility with older published checksums, but is not considered cryptographically secure for tamper-resistance — SHA-256 or better is the current standard recommendation.
Common questions
Is my file or text uploaded anywhere?
No. Hashing runs entirely in your browser using the Web Crypto API — nothing you type or drop is sent to a server, which is also why very large files are read fully into memory locally rather than streamed.
Why isn't MD5 offered?
MD5 isn't part of the browser's native Web Crypto API, and this project doesn't ship a hand-written cryptographic primitive it can't verify as rigorously as a browser-audited one. If you need MD5 specifically for compatibility with an older checksum, a command-line tool (md5sum, certutil, etc.) is the safer choice.
Which algorithm should I use to verify a download?
Whichever one the publisher actually provided — that's exactly why this tool computes all four at once instead of making you guess. Paste their checksum into the Compare field and it tells you which algorithm (if any) it matches.
Why do I get a completely different hash for what looks like the same file?
Cryptographic hashes are designed so that even a single changed byte — including a different line-ending style, a trailing newline, or a different text encoding — produces a completely unrelated hash. This is a feature (it's what makes hashes useful for detecting corruption or tampering), not a bug in the tool.
Is SHA-1 safe to use?
SHA-1 is included because some older published checksums still use it, but it's no longer considered secure against a deliberate attacker trying to forge a matching hash (a "collision"). For verifying accidental corruption it's still fine; for security-sensitive integrity checks, prefer SHA-256 or SHA-512.