Checksum Calculator

A checksum is a fixed-length digest produced by a hash function: identical input always yields the identical digest, and a single changed byte produces a completely different one. This checksum calculator computes MD5, SHA-1, SHA-256, SHA-384, SHA-512, and CRC32 digests from any text string or local file entirely in the browser. SHA family hashes run through the Web Crypto API, and MD5 and CRC32 run through pure JavaScript implementations, so nothing is uploaded to a server.

Text is encoded as UTF-8 before hashing, which is why results match standard command-line tools such as sha256sum or md5sum that operate on UTF-8 encoded bytes. File input reads the file's raw bytes directly from the local filesystem, so hashing a very large file can take a moment while the bytes load into memory before a digest appears.

• Any combination of MD5, SHA-1, SHA-256, SHA-384, SHA-512, and CRC32 can run in the same pass, each producing its own hex-encoded digest.
• A pasted hash is compared against every computed digest at once, and the tool reports which algorithm, if any, produced a match, so a mismatch surfaces regardless of which algorithm the published hash used.
• Hex digests display in lowercase by default; an uppercase option is available under Settings for tools or documentation that expect uppercase output.
• Calculation runs automatically a short delay after text input changes, in addition to running on demand.
• Input, algorithm selection, and formatting preferences are retained between visits.

CRC32 is a non-cryptographic checksum designed to catch accidental corruption quickly. MD5, SHA-1, and the SHA-2 family (SHA-256, SHA-384, SHA-512) are cryptographic hash functions built to also resist deliberate tampering, which is why verifying software downloads and evidentiary files calls for SHA-256 or stronger, while CRC32 is suited to casual integrity checks such as a backup archive.

Checksums serve as digital fingerprints that detect corruption, tampering, and duplication across many domains. The scenarios below use a checksum calculator to compute and verify hashes directly in the browser.

• Software Distribution: Verify downloaded installers, firmware images, or archive files against the SHA-256 hash published on the vendor site. A matching digest confirms the file arrived intact before it runs; a mismatch means it was corrupted or replaced in transit.
• Data Transfer Integrity: Confirm that a file copied between drives, cloud storage accounts, or network shares arrived without bit-level corruption. Compute the checksum on the source machine, then recalculate on the destination and compare.
• Digital Forensics: Document the hash of evidence files at the time of collection. Recalculating later proves the file has not been altered, which is critical for chain-of-custody records in legal proceedings.
• Configuration Management: Track whether configuration files, scripts, or templates have changed between deployments. Store the SHA-256 of each file in a manifest and recompute after deployment to detect unintended modifications.
• Content Deduplication: Identify duplicate files in a large collection by computing MD5 or SHA-256 hashes and comparing digests. Identical hashes on two files indicate identical content regardless of filename differences.
• API Development: Generate checksum values for request payloads during development. Hash the JSON body with SHA-256 and compare it against the server-side expectation to debug signature mismatches.
• Backup Verification: After creating a backup archive, compute its CRC32 or SHA-512 hash and store it alongside the archive. Before restoring, recalculate and compare to ensure the backup is not corrupted.
• Education: Explore how different hash algorithms produce different length outputs from the same input. Compare MD5 (128-bit), SHA-1 (160-bit), and SHA-256 (256-bit) digests side by side to understand hash function properties and collision resistance differences.