Hash Generator & Checksum Checker

Choose Text or File, select a hash algorithm and press Generate hash. Text mode converts what you type to UTF-8 bytes. File mode reads the contents of the selected file, up to 100 MiB, without uploading it. The digest is shown as hexadecimal text and can be copied or downloaded as a checksum line.

SHA-256 is selected initially because it is commonly used to publish download checksums. If a software publisher provides a checksum under a different algorithm, select that exact algorithm before generating yours.

Select the downloaded file and the algorithm named by its publisher, then generate its digest. Open Verify a checksum and paste the expected hexadecimal value, a complete checksum line or a checksum list. The checker reports whether the values match, or explains when the algorithm, filename or supplied format prevents a valid comparison.

For lists containing filenames, the selected file must match an entry. A checksum copied for a different operating system, release or archive should not be treated as interchangeable. Obtain the expected value from the publisher's trusted channel, not merely from the same unverified download source.

The tool supports four SHA-2 variants, four SHA-3 variants, and three compatibility algorithms: MD5, SHA-1 and RIPEMD-160. SHA-2 and SHA-3 are different hash families. SHA-256 and SHA3-256 both produce 64 hexadecimal characters, but they do not produce the same digest for the same input.

MD5 and SHA-1 remain useful for comparing checksums that already exist, but their collision weaknesses rule them out for security-sensitive integrity checks. RIPEMD-160 is provided where an existing workflow requires it. For verification, the important choice is the algorithm used to create the published checksum—not whichever produces the longest output.

A checksum may be published as plain hexadecimal text or with an algorithm name and filename. GNU-style lines place the digest before a filename; BSD-style lines include the algorithm name. The checker also accepts supported labeled digests and multi-line lists.

A raw digest or GNU-style line does not identify its algorithm. Digest length can narrow the possibilities, but it cannot distinguish SHA-256 from SHA3-256, for example. The checker uses your selected algorithm and respects any explicit algorithm label rather than guessing.

Hash functions operate on bytes, not how content looks on screen. An added space, a trailing newline, different line endings or a change in Unicode characters changes the input bytes and generally produces a different digest. This tool does not trim text or deliberately normalize it before UTF-8 encoding.

A file hash covers the file's contents, not its name, folder, download date or modification time. Renaming an unchanged file does not change the digest, although filenames in published checksum lists still matter when the checker selects the correct entry. Choosing Uppercase changes only how the hexadecimal digest is displayed, copied and downloaded.

A match means that the generated digest agrees with the expected value under the selected algorithm. If that value came from a trusted publisher, a modern collision-resistant algorithm provides strong evidence that the file bytes agree with the expected release.

A matching checksum cannot establish who published a file when the expected digest itself is untrusted. It is not a malware scan or a digital signature. This tool also does not provide password hashing: passwords should be stored with a dedicated salted, deliberately expensive algorithm rather than a single fast digest.

The file limit is 100 MiB (104,857,600 bytes). The selected file is loaded into browser memory before hashing, so memory use can be higher than the file size and performance depends on the device. Browser Web Crypto does not offer a streaming digest API.

For larger files, use a trusted local command-line or desktop checksum utility. The page does not need your file to be sent to a remote service to perform the calculation.