Hash Generator & Checksum Checker

Choose Text or File and select SHA-256, SHA-384, or SHA-512.

Text mode hashes the exact UTF-8 bytes represented by the text box. File mode hashes the complete contents of the selected local file.

Select Generate hash, then copy the hexadecimal digest or download a checksum file.

Generate a digest using the algorithm named by the publisher.

Paste the expected hexadecimal value, the complete checksum line, or the relevant checksum-list contents.

The checker reports a match, mismatch, wrong algorithm, filename mismatch, ambiguous list, or unsupported format.

Obtain the expected checksum from a trusted source rather than an unrelated mirror or repost.

SHA-256, SHA-384, and SHA-512 belong to the SHA-2 family standardized by NIST.

Their hexadecimal digest lengths differ, which allows the checker to detect many cases where the selected algorithm does not match the pasted value.

For verification, use the algorithm specified by the publisher rather than choosing a different algorithm because it appears stronger.

A checksum may be published as a bare hexadecimal value or together with an algorithm name and filename.

GNU-style output places the digest before the filename. BSD-style output places the filename inside parentheses.

When a list contains named entries, the checker compares only the entry matching the selected local file. It does not silently use a line for another filename.

A file digest is calculated from file contents.

The filename, folder, creation time, modification time, and download location are not hashed.

Renaming or moving an unchanged file therefore leaves its digest unchanged, while changing even one byte normally changes the digest.

Hash functions operate on bytes rather than visual appearance.

A trailing newline, additional space, different capitalization, Windows versus Unix line endings, or another Unicode sequence can produce a different digest.

The tool does not trim whitespace or normalize Unicode before hashing.

A match means the generated digest equals the expected digest selected by the checker.

When the expected digest came from a trusted source, this provides strong evidence that the local bytes agree with the described file.

It does not prove who created the file. Digital signatures and trusted signing keys serve a different purpose.

The selected file may be a different version, operating-system build, architecture, archive, or extracted file.

The wrong hash algorithm may be selected, the download may be incomplete, or the expected checksum may have been copied from another entry.

For text, invisible whitespace and line-ending changes are common causes.

The browser's native digest API requires the complete input buffer and does not provide streaming progress.

A 100 MB cap keeps memory use more predictable on phones and lower-memory computers.

Use an operating-system checksum command or a trusted streaming desktop utility for larger files.

A single fast SHA-256, SHA-384, or SHA-512 digest is not an appropriate way to store user passwords.

Password-storage systems require a unique salt and an intentionally expensive password-hashing design.

Follow current application-security guidance for password storage rather than using this checksum tool.

The selected file, entered text, generated digest, and expected checksum remain in the browser.

Nothing is uploaded, added to a public URL, or permanently stored by the tool.