File Checksum Calculator
Hash a whole batch of files in one go. Drop or choose files, tick the algorithms you need, from MD5 and SHA-1 to SHA-256, SHA-512 and CRC32, and get a table of checksums. Files are streamed and hashed on your device, never uploaded. Export the results as a standard checksum file such as SHA256SUMS, or as CSV.
- Runs in your browser
- No sign-up
- Free to use
How to use File Checksum Calculator
- Tick the algorithms you need.
- Choose or drop one or more files.
- Wait while the files are hashed; progress is shown.
- Download a checksum file or CSV, or copy the list.
File Checksum Calculator features
Five algorithms
MD5, SHA-1, SHA-256, SHA-512 and CRC32, several at once.
Many files
Hash a whole folder’s worth of files in one batch.
Streaming
Files of any size, read in slices with progress.
Checksum file
sha256sum-style output that standard tools can verify.
CSV export
All hashes with file names and sizes.
Local only
Nothing is uploaded.
When to use File Checksum Calculator
- Publishing checksums for software releases.
- Recording file fingerprints before archiving or transferring.
- Checking that backups match the originals.
- Creating CRC32 values for ZIP or legacy systems.
File Checksum Calculator FAQ
Which algorithm should I use?
SHA-256 for integrity and anything security-related. MD5 and SHA-1 only where a system requires them. CRC32 detects accidental errors but offers no security.
Are my files uploaded?
No. They are read and hashed by your browser.
What is a checksum file?
A text file with one line per file: the hash, two spaces and the file name. Tools such as sha256sum -c can check all files against it.
Can I hash a folder?
Select all the files in the folder in the file dialog, or drop them at once. Folder structure is not recorded, only file names.
Is there a size limit?
No fixed limit. Files are streamed, so large files take time but not much memory.
Do I get the same results as command-line tools?
Yes. The implementations follow the standards and match sha256sum, shasum, md5sum and similar tools.
Fingerprinting files in bulk
Checksums are the simplest way to know whether files are exactly what they should be. Record them when files are created, published or archived, and you can later prove that copies, backups or downloads are identical, bit for bit.
Different algorithms serve different needs. CRC32 is a fast error-detecting code used inside ZIP files and network protocols. MD5 and SHA-1 were long the standard for file fingerprints and remain common in older systems, though both are broken for security. SHA-256 and SHA-512 are today’s choice whenever integrity matters against deliberate tampering.
This calculator hashes each file with every selected algorithm in a single pass, reading the file once in slices and updating all hashes together. That keeps large batches fast and memory use low, and everything stays on your device.
The exported checksum file follows the format of the GNU coreutils tools, so recipients can verify files with sha256sum -c on Linux or with this site’s Checksum Verifier. Publish it alongside the files, ideally on a different, trusted channel or with a signature.