Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.
Select the file you want to generate a checksum for.
Select MD5, SHA-1, SHA-256, or another hash algorithm.
Click copy to grab the checksum value for verification.
Choose a file to calculate four hexadecimal fingerprints of its exact byte content: MD5, SHA-1, SHA-256, and SHA-512. The calculation happens in the browser, so the selected file is not uploaded. The result can be compared with a checksum supplied by a publisher, sender, backup system, or other trusted source. A frequent mistake is treating a checksum as proof that a file is safe. It establishes a byte-level comparison only; it does not scan for malware or prove who created the file.
A concrete input and expected output from the current implementation.
Input
A file named abc.txt containing exactly the three ASCII bytes abc, with no byte-order mark and no trailing newline.
Expected output
MD5: 900150983cd24fb0d6963f7d28e17f72 SHA-1: a9993e364706816aba3e25717850c26c9cd0d89d SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad SHA-512: ddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a2192992a274fc1a836ba3c23a3feebbd454d4423643ce80e2a9ac94fa54ca49f
Each value is the defined digest of the byte sequence 0x61 0x62 0x63. Adding a newline or byte-order mark would create a different sequence and therefore different checksums.
The calculator applies each hash function to the selected file's raw bytes. MD5 produces 32 hexadecimal characters, SHA-1 produces 40, SHA-256 produces 64, and SHA-512 produces 128. The file name and folder location do not affect these content checksums. Even a one-byte content change normally produces a substantially different result.
Compare the complete calculated value with an expected checksum for the same algorithm. Hexadecimal letter case is only presentation, so uppercase and lowercase letters represent the same value, but every digit and leading zero matters. A match means both inputs produced the same digest; its evidentiary strength depends on the algorithm and whether the expected checksum came from a trustworthy source.
No. A checksum does not classify malware, inspect behavior, or identify the author. It can show that a file matches a checksum obtained from a trusted, independent source. If an attacker can replace both the file and the published checksum, matching values do not establish authenticity. A digital signature addresses a different question.
Hash functions process bytes rather than visible meaning. Saving a document can alter line endings, encoding, compression, embedded metadata, timestamps stored within the format, or other nonvisible content. Any such byte change produces a new checksum. Recalculating the original file unchanged should produce the same value for the same algorithm.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Encrypt and decrypt text using AES-256, RSA, or other ciphers with password-based key derivation.