File Hash

How to use it

1. Click Choose files (or drag files onto the page) and pick one or more files.
2. Each file gets its own card in the list; hashes are computed one file at a time.
3. For every file you get SHA-1, SHA-256, SHA-384 and SHA-512 in hexadecimal form.
4. Click Copy next to any hash line to copy that single digest.
5. Use Clear to empty the results and hash a new batch.

Common use cases

• Verifying downloads - compare the SHA-256 of an installer with the value its vendor publishes.
• Checking duplicates - identical files produce identical digests, so one comparison settles it.
• Integrity after transfer - hash a file before and after copying or uploading to spot corruption.
• Build artifacts - attach checksums to release files so recipients can verify them.

Why it stays private

Files are read into browser memory and hashed with the native Web Crypto API. They are never uploaded, logged or stored, so hashing confidential documents, keys or personal archives leaks nothing.

FAQ

Q: Which algorithm should I use to verify a download? A: SHA-256 is the common default. SHA-384 and SHA-512 are equally fine for integrity checking; SHA-1 is included because some older vendors still publish SHA-1 digests, but treat it as legacy only.

Q: How large a file can I hash? A: The file is read fully into memory before hashing. Files up to a few hundred megabytes are fine on a typical machine; for multi-gigabyte images you may hit browser memory limits.

Q: Why do two files with the same content in different formats hash differently? A: Hashing operates on raw bytes. A re-saved document may differ in metadata or compression even when it looks identical, so only byte-identical files share a digest.