File Integrity Checker

Generate a checksum (hash) of any file to confirm it wasn't corrupted during download or transfer, or tampered with along the way. If the hash you calculate matches the hash published by the file's source, the file is identical, byte for byte, to the original.

Drop a file into the tool above or click to browse for one. Large files are streamed in chunks, so there's no file size limit and nothing is ever uploaded anywhere.

How to Check File Integrity

• Drop in or browse for your file:
  Drag and drop the file directly or click to select it from your machine.
• Pick the algorithm:
  Choose SHA-256, SHA-512, or MD5 to match the hash you were given.
• Wait for the hash to generate:
  Large files are streamed in chunks, so even multi-gigabyte files can be checked without running out of memory.
• Verify against a known hash:
  Paste the published hash into the verify field to confirm it matches.

SHA-256 vs SHA-512 vs MD5

SHA-256 is the most common choice today for verifying downloads and software packages. SHA-512 offers a longer digest for the same family. MD5 is faster and still widely used for detecting accidental corruption, though it's not considered cryptographically secure against deliberate tampering.

Why Use a File Integrity Checker?

• Catch corrupted downloads:
  A hash mismatch tells you immediately if a download was interrupted or damaged in transit.
• Detect tampering:
  Comparing against a publisher-provided hash confirms a file wasn't altered before it reached you.
• Works on any file size:
  Chunked streaming means multi-gigabyte files are checked without loading the whole file into memory.

FAQs

• Is this tool safe for large or sensitive files?
  Yes. Everything runs locally in your browser — files are never uploaded anywhere.
• Which algorithm should I use?
  Use whichever algorithm matches the hash published by the file's source — SHA-256, SHA-512, or MD5.
• Is there a file size limit?
  No. Files are read and hashed in chunks, so even very large files can be checked.
• Is my file sent to a server?
  No. All hashing happens locally in your browser. Your file never leaves your machine.