Which hash should I use to verify a downloaded file?

Use the exact algorithm published by its distributor. If you are establishing a new verification workflow, SHA-256, SHA-384, SHA-512 or SHA3-256 is preferable; MD5 and SHA-1 remain for legacy matching, and CRC32 is non-cryptographic.

Does the text mode ignore capitalization or whitespace?

No. It hashes the exact UTF-8 representation, including letter case, spaces, tabs and line breaks. Even an intentionally empty string has a defined hash and can be calculated.

Can one calculation produce several algorithms for several files?

Yes. Every file chunk is read once and fed to all selected algorithms during the same worker job. Each file keeps separate progress, results and optional expected-checksum verification.

How does an imported checksum manifest match files?

Parsed entries are associated with uploaded filenames, including common leading ./ notation. Unmatched or malformed entries are reported rather than silently applied to the wrong file.

Back to Developer & Data Tools

File Hash & Checksum Calculator

Create and verify cryptographic or legacy fingerprints for multiple files and exact UTF-8 text without uploading the source data.

Algorithms

SHA-1 and MD5 are provided for legacy compatibility. CRC32 is non-cryptographic. Use a modern cryptographic hash such as SHA-256, SHA-512, SHA-384 or SHA3-256 for security-sensitive workflows.

Add files

Any file type · multiple files supported · processed locally

Checksum Manifest

Import .sha256, .sha512, .sha384, .sha1, .md5 or a standard checksum list.

Files and text are processed locally. A matching checksum confirms agreement with the supplied reference, not whether that reference is trustworthy.

How to use File Hash & Checksum Calculator

1
Choose File Hashing or Text Hashing, then select any combination of SHA-256, SHA-512, SHA-384, SHA-1, MD5, CRC32 and SHA3-256.
2
For files, add one or more items of any type and click Calculate Hashes. For text, enter the exact content—including intended spaces and line breaks—before calculating.
3
Copy individual digests or all completed results. A pasted expected checksum can be auto-detected or assigned an algorithm for per-file verification.
4
Optionally import a .sha256, .sha512, .sha384, .sha1, .md5 or standard text manifest to match checksum entries with uploaded filenames.

Frequently asked questions

About File Hash & Checksum Calculator

Checksums provide a compact way to confirm that data arrived unchanged, compare against a software publisher's digest or document a known file version. This calculator covers modern SHA-2 and SHA3-256 options as well as MD5, SHA-1 and CRC32 for existing ecosystems that still publish those values. Legacy algorithms are clearly labeled rather than presented as current security choices.

File mode accepts batches and performs incremental reads in a worker. When several algorithms are active, one chunk feeds every selected hasher, avoiding repeated full passes over storage. Text mode uses the exact UTF-8 input, making it suitable for configuration values and reproducible strings where a single invisible character matters.

Verification can be entered beside an individual file or imported from common checksum-list formats. Digest length helps with algorithm detection, while explicit validation catches malformed values and unmatched manifest names. Results remain complete and copyable, and all source bytes stay on the device.