File Hash Checker

How it works in FileLume

• The browser reads each selected file and calculates cryptographic digest values locally.
• FileLume writes the per-file hash results into hashes.txt.

Best for

• Comparing a downloaded file with a checksum published by a trusted source.
• Checking whether two copies have identical bytes.
• Recording integrity values before or after transfer.

Format and quality guidance

• A matching hash indicates matching bytes for the selected algorithm; it does not prove who created the file.
• SHA-256 is the stronger general integrity choice; SHA-1 remains useful only when a source publishes SHA-1.

Trade-offs to expect

• Large files take longer because every byte must be read.
• A hash verifies byte equality, not safety, authenticity, or absence of malware.

Limitations

• The tool does not scan files for viruses or validate a digital signature.
• You must obtain the expected checksum from a trustworthy independent source.

Common errors and fixes

The hash does not match.

Download the file again and verify that the expected checksum and algorithm are correct.

Two visually identical files have different hashes.

Metadata or any byte-level difference changes the digest.

Hashing is slow.

Allow the browser to finish reading the file or process fewer large files at once.

File Hash Checker FAQ