We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Calculate file SHA hash values, verify integrity and security, support SHA-1/256/512 algorithms
Choose filesClick to upload file
Or drag and drop files here
Max 100 MB
Upload file to start calculation
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A SHA checksum is a fixed-length digest computed from the file’s bytes. This file SHA checksum tool can calculate SHA-1, SHA-256, SHA-384, and SHA-512. All four are selected initially; deselect any algorithms you do not need, then choose one file. The result area shows the file name, size, progress, and a lowercase hexadecimal digest for each selected algorithm, with a copy control for each value.
The filename is not part of the digest input: the bytes are. Two files with identical bytes produce the same digest for a given algorithm even if their names differ. Changing file content changes the digest in normal use. The output lengths are 40 hexadecimal characters for SHA-1, 64 for SHA-256, 96 for SHA-384, and 128 for SHA-512.
NIST’s Secure Hash Standard specifies SHA-1 and SHA-2 family algorithms, including SHA-256, SHA-384, and SHA-512, for message digests used to detect changes. For a modern published software checksum, select the same algorithm named by the publisher—often SHA-256—and compare the full result with the value obtained from a trusted release source.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Choose the algorithm or algorithms to calculate. Keep the publisher’s algorithm in mind: SHA-256 output cannot be compared with a SHA-512 reference.
Select the file whose bytes you want to check. The tool processes one selected file and shows progress while reading it.
Copy the result for the matching algorithm and compare every character with a digest published through a trusted source. This page calculates digests; it does not provide a reference value or automatically report match/mismatch.
If values differ, confirm you have the intended file version and algorithm, then obtain the expected digest from the software publisher’s trusted release channel before drawing a conclusion.
Use cases
See how the tool fits into real work and everyday tasks.
Calculate the algorithm named by the publisher and compare it with the independently obtained release checksum to spot a changed or incomplete download.
Calculate the same algorithm for each copy in turn. Matching digests are a compact way to check whether the bytes match, even when filenames differ.
Copy a digest into a project note or handoff record when another person needs to compare a file against the same byte-level reference later.
Q&A
Find concise answers to common questions and confusing cases.
No. It computes digest values from a selected file. Copy the result and compare it yourself with a trusted expected value.
Use the same algorithm specified by the file publisher or the workflow you are following. SHA-256 is a common modern checksum choice; SHA-1 is included for compatibility with older references.
No. A digest comparison can detect a mismatch with a reference, but does not establish who published the file or whether the file is safe. Trust in the source and stronger authenticity mechanisms still matter.
The contents may differ even when filenames match. The digest is computed from file bytes, not the displayed name.
Notes
Review scope, result limitations, and important precautions before use.
A hash is not encryption and does not hide file contents. A checksum match only has meaning in relation to the expected digest and the trustworthiness of its source. Do not treat this calculator as malware scanning, signature verification, or proof of publisher identity. NIST has deprecated SHA-1 for many security uses; retain it only where a legacy reference requires it, and follow current organizational cryptographic policy for security-sensitive work.
Related
Discover related tools, collections, and available API capabilities.