Skip to content
Media

File Hash Calculator

Compute SHA-1, SHA-256, SHA-384, SHA-512 hashes of any file.

filehashsha256sha512checksum
Loading tool…

About the File Hash Calculator

The File Hash Calculator computes SHA-1, SHA-256, SHA-384, and SHA-512 digests for any file using the browser's native Web Crypto API, so nothing ever leaves your machine. Drag a file onto the drop zone or pick one with the file chooser, and all four hashes appear as copyable hex strings alongside per-algorithm compute times in milliseconds. A file info card shows the name, exact byte size, a readable size, and the MIME type the browser detected. Recompute re-runs the hashes against the same file, and Download report exports a text file with the file metadata, timestamps, and every digest — handy for attaching to release artifacts. Files over 500 MB are blocked to protect browser memory, and anything above 10 MB triggers a warning that the UI may pause briefly. The tool is candid about its crypto guidance: SHA-1 is marked broken and should never be used for security, and hashes cover raw bytes only, excluding names and dates. For verifying downloads, integrity-checking backups, or generating a release checksum file, this local SHA-256 hash calculator delivers trustworthy output without uploading sensitive files to a web service.

File Hash Calculator examples

Input
A 4.7 GB ISO image dragged onto the drop zone.
Output
Four hex digests with compute times of several seconds each, plus a file info card showing the byte count and MIME type.
Note: An amber warning appears for files over 10 MB, noting the single-pass hashing may pause the UI.
Input
A 2 KB text file, then clicking "Recompute" after editing it on disk.
Output
The digest changes across all four algorithms the moment the updated file is re-selected or recomputed.
Note: Recompute re-reads the stored File object; re-pick the file if its contents changed on disk.
Input
Clicking "Download report" after hashing release.zip.
Output
A release.zip-hashes.txt listing file name, size, type, last modified date, and all four hashes under per-algorithm headers.
Note: The report is formatted for easy pasting into release notes or a CHECKSUMS file.

How to use the File Hash Calculator

  1. 1

    Drag a file onto the dashed drop zone, or click "Choose a file" and pick one.

  2. 2

    Wait for the "Hashing…" state to finish — all four algorithms run in sequence.

  3. 3

    Read each hash row under the Hashes card and click "Copy" to grab any digest.

  4. 4

    Click "Recompute" to re-run hashes on the same file, or "Download report" to export everything.

  5. 5

    Check the File info card for the detected type and readable size.

Common use cases

  • Verifying that a downloaded installer matches the publisher's published SHA-256.
  • Integrity-checking backups before migrating them to cold storage.
  • Generating a checksums file to ship alongside open-source release binaries.
  • Confirming two copies of a file are identical by comparing digests.
  • Auditing which files changed between two exports without opening them.
  • Hashing sensitive documents locally when company policy forbids uploads.

Best practices

  • Rely on SHA-256 or SHA-512 for integrity; treat SHA-1 results as reference-only.
  • Use the Download report option so file metadata travels with the hashes.
  • Keep files under the 500 MB limit and expect brief UI pauses above 10 MB.
  • Compare against hashes from an independent source, not just a second copy you made.
  • Remember the hash covers raw bytes only — renaming a file does not change it.

Tips

  • Copy any digest with one click — each row has its own Copy button.
  • Watch the ms badges to compare algorithm speed on your hardware.
  • The report file name follows the pattern <filename>-hashes.txt.
  • Hash the same release from two machines and diff the SHA-256 rows.

Frequently asked questions

SHA-1, SHA-256, SHA-384, and SHA-512, all via the Web Crypto API. Every algorithm runs on the same file in one pass, with per-algorithm timing shown in milliseconds.

No. The file is read into an ArrayBuffer in memory and hashed locally with crypto.subtle.digest. The browser never sends the content anywhere.

Files over 500 MB are rejected with a toast to protect browser memory. Files above 10 MB still hash, but show a warning that the UI may pause during computation.

Collision attacks make SHA-1 unsuitable for security purposes. The tool's notes recommend SHA-256 or stronger for integrity verification while still computing SHA-1 for legacy comparisons.

It re-runs all four hashes over the currently loaded file. If you edited the file on disk, pick it again first — recompute hashes the in-memory copy from when it was loaded.

A plain-text file with the file name, byte size, readable size, MIME type, last modified timestamp, generation timestamp, and each algorithm's hash and compute time under its own header.

Explore more media tools

Browse the full collection of media tools on the hub, or jump back to all categories.

Related tools

Did this tool help?

Anonymous — one tap, no sign-up.