Enter Input
Verify text or any file up to 20 MB.
Verify that text or file content matches a supplied cryptographic hash.
Confirm that text or file content matches a supplied message digest.
Enter text or choose a file, then provide a hash.
Verify text or any file up to 20 MB.
Use the same algorithm that created the supplied hash.
No verification performed.
——A hash converts data into a fixed-size fingerprint. Any input change produces a different result.
Reviewed by LipiCode Editorial Team
Hash verification recalculates a digest from supplied content and compares it with an expected value. A match indicates the compared bytes are the same under that algorithm; its trust still depends on where the expected digest came from.
Select the algorithm named by the publisher, hash the unchanged file, and compare every digest character. Obtain the expected value from an HTTPS page or signed release controlled by the publisher.
Different line endings, encodings, metadata, or archive repacking change file bytes and therefore the hash. A malicious file and malicious checksum distributed together will still match.
Hex letter case does not change the digest value, though all characters and length must match.
The bytes, selected algorithm, or expected digest differ; do not trust the file until resolved.