中文

File Hash Checker

Drag & drop a file here, or click to select
Any file · hashed locally, never uploaded
Hash result
Select a file to compute its hash automatically

Online file hash calculator for SHA-1 / SHA-256 / SHA-512. Files are hashed locally in the browser and never uploaded.

How to Use & FAQ5 steps · 8 Q&A

File Hash Checker

Online file hash calculator for SHA-1 / SHA-256 / SHA-512. Files are hashed locally in the browser and never uploaded.

How to Use

  1. Choose algorithmsSelect SHA-1 / SHA-256 / SHA-512; prefer SHA-256 for security checks.
  2. Drop in a fileDrag & drop or click to select a file; hashing starts automatically. Wait for large files.
  3. Copy the hashCopy with one click after computing and compare segment by segment with the official hash.
  4. Text can be hashed tooPaste text below to hash it, useful for comparing config snippets or short tokens.
  5. Comparison tipsCopy the official hash first, then paste it into a compare box to avoid manual typos; watch for leading/trailing spaces.

Related tools

Base64 Encoder/DecoderURL Encoder/DecoderSymmetric EncryptionAsymmetric Encryption

Related reading

Local LLM vs Cloud API: Privacy, Cost and Capability Trade-offsHow to Verify File Integrity with SHA-256Local vs Server Processing: Why Browser-Only Tools Are SaferThe 3-2-1 Backup Rule and Restore Drills

FAQ

Why verify a file hash?

Comparing against an officially published hash lets you confirm a downloaded file is intact and has not been tampered with. A poisoned mirror, a dropped connection or a bad sector can all leave a file "looking the same" yet with a different hash.

Why is there no MD5?

The browser’s native Web Crypto API does not provide MD5, and MD5 is no longer suitable for security (collisions can be engineered). This tool offers the safer SHA family; for local de-duplication, use SHA-256.

Will the file be uploaded?

No. The file is read locally and hashed within the browser — it is never uploaded to a server, so you can safely verify files containing private content.

Will large files be slow to hash?

Hashing uses the browser Web Crypto API, so larger files take longer. Please wait for large files and avoid refreshing or closing the page, or you will have to recompute.

Why does the hash differ from the officially published one?

The file may be tampered with or incompletely downloaded, or the official value may use a different algorithm or encoding (case, trailing newline). Confirm the algorithm matches and the file is not re-packaged before comparing.

Should I choose SHA-1 or SHA-256?

Always choose SHA-256 or stronger for security; SHA-1 has collision risks and should be used only to match legacy checksums (e.g. old system signatures). For everyday file checks, prefer SHA-256.

Does an identical hash mean the file is absolutely safe?

No. A matching hash only proves the file is byte-for-byte identical to the official one, not that the official one is harmless. A trusted source plus a matching hash together make a credible check.

Will hashing the same file twice give different results?

No. Hashing is deterministic: the same bytes always yield the same digest, no matter how many times. If two runs differ, the bytes you read actually differed (file changed, disk error, etc.).