A file hash is a fixed-length digest calculated from the file's bytes. Comparing a calculated digest with a trusted published value can help detect accidental corruption or an unexpected file change. This checker reads a selected file and computes SHA-1, SHA-256, SHA-384, and SHA-512 through a browser helper. You may optionally provide an expected hash; the result reports a match if that text equals one of the computed values. A hash comparison does not scan for malware or prove that the file publisher is trustworthy. The expected digest must come from an independent, authenticated source.
Choose a file using Select a file, optionally paste a digest into Hash to verify, and press Generate Hashes. The output includes the filename, file size in KB, and all four algorithm results. If an expected value matches one result after case and surrounding whitespace are normalized, the report adds a match message; otherwise it says no algorithm matched. Clear clears the component's stored file selection, output, and comparison value; the browser picker may still display the previous filename. The action is disabled when no file is selected or while computation is in progress.
For example, select a small text file containing exactly `hello` and enter the known SHA-256 digest `2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824`. The report will list four digests and mark the expected value as matching SHA-256. A newline added to the file changes each digest, even if a text editor visually makes the content look the same. To avoid a false mismatch, copy the complete expected hex string and make sure it corresponds to the same file version and algorithm.
The output presents multiple algorithms in one report rather than asking you to select only one. SHA-1 remains available for legacy comparisons, but it is not recommended for new collision-resistant security decisions; SHA-256 is a common general-purpose choice. The expected-hash input accepts one string and checks it against the results, so it does not force a selected algorithm or validate a publisher signature. Output is available as plain text, which can be saved as file-hashes.txt for a local record.
Use the checker when comparing a downloaded installer to a release digest, checking whether an archive changed during transfer, or documenting hashes of test artifacts. Checksum Generator handles either text or one selected algorithm for a file; Hash Generator is convenient for text-only digests. HMAC Generator is appropriate when a shared secret must authenticate data, whereas a public checksum by itself has no secret and can be replaced alongside the file by an attacker.
File reading and hashing occur in the browser: the component calls `file.arrayBuffer()` and passes the bytes to the Web Crypto digest helper. The selected file is therefore loaded fully into memory, and very large files may be slow or exceed device capacity. The component does not stream chunks or expose a progress percentage. It processes no file contents through a dedicated hashing server, but browser extensions, local access, and broader site behavior are outside the component's guarantee; do not use it as a substitute for a vetted offline workflow when policy requires one.
For reliable verification, obtain the reference digest through a signed release manifest or another trusted channel, verify the signature if provided, and compare the correct algorithm and full digest. A match only establishes byte equality relative to the expected hash. It cannot prove who created the artifact, whether it contains malicious code, or whether the checksum itself was tampered with. If an expected hash does not match, confirm file version, algorithm, copy completeness, and line-ending transformations before taking action.
The calculation reads the entire selected file into memory before calling the digest operation. This is straightforward for ordinary documents and small installers, but large disk images can use substantial memory and may cause the browser tab to slow down. If the file is too large, use a trusted command-line or dedicated verification tool that supports streaming, and compare its output with an independently authenticated manifest. The interface does not split large files into chunks or keep a progress log.
The file name and reported size help you identify which local item was selected, but neither participates in the digest. If the browser returns the same bytes under a different name, the hash remains identical. Conversely, two files with the same name can contain different bytes and produce different digests. Record version and source information alongside the result, and avoid relying on a filename alone when reviewing multiple downloads.
The optional comparison ignores letter case and trims outer whitespace, which is convenient for standard hex strings. It does not interpret a pasted algorithm label or prefix, and it checks against each supported result rather than validating only the algorithm you intended. If no match is shown, compare the actual hex characters and the expected digest's origin. A checksum mismatch is a prompt to investigate, not automatic proof of attack; transfer error, wrong version, and incorrect reference are possible explanations.
A browser file picker can continue displaying a chosen filename after its component state is cleared; confirm selection before another check.
The tool reports the file's displayed name and size in kilobytes for context, but the comparison itself is solely on digest text. If you check several versions with identical names, save the output next to an unambiguous version label or release number. Do not infer the result from the filename. A correct digest can still belong to an unintended version if the expected value was copied from the wrong release page.