The hash differs from another tool - text is passed to the hash function exactly as entered, so leading spaces, trailing spaces, line endings, and Unicode differences change the digest.
SHA generation is unavailable - SHA-1 and SHA-2 variants need crypto.subtle.digest; the tool reports that a modern browser or HTTPS context may be required.
A file takes a long time or the page becomes unresponsive - file hashing reads the entire selected file with file.arrayBuffer before digesting it, and there is no configured file-size cap.
MD5 is unavailable after switching to File mode - the tool automatically selects SHA-256 because the current blueimp-md5 string library is deliberately not used for binary-file checksums.
The expected hash does not match - the comparison only trims surrounding whitespace and ignores letter case; it cannot repair a hash from a different file, algorithm, or text encoding.
MD5 or SHA-1 was selected for a security-sensitive integrity decision - both are legacy algorithms and should not be used for that purpose; choose a stronger SHA-2 option when the receiving requirement permits it.
A matching value seems to prove who made the file - a digest only becomes meaningful for authenticity when the expected value comes from a trusted source.
Copy hash does nothing - navigator.clipboard.writeText can fail because clipboard access is unavailable in the browser context.
You need a checksum file download - the implementation can copy the hexadecimal result but has no hash-file download control.