1. Identify the exact file and release
Record the product, release version, platform or architecture, and filename before choosing a checksum. Two packages for the same product may contain different bytes even when their names look similar. Compare the file you actually downloaded, not an extracted folder or an installer that has already modified itself.
Keep the file unopened while performing this check. Hash calculation does not require running the downloaded software. If the intended file is unclear or several duplicate downloads exist, resolve that uncertainty first; otherwise a correct comparison may concern a different file from the one you later use.
2. Obtain the publisher’s checksum and method
Use the publisher’s verified official release page or documentation and note the algorithm associated with the checksum. Preserve the exact URL and which filename its value belongs to. Do not use an unrelated search snippet or a checksum supplied only by an untrusted message as your source of authority.
Canonical’s Ubuntu verification tutorial separates checksum-based integrity checking from signature-based authenticity verification. Follow the publisher’s current signature instructions when authenticity verification is part of its process. This guide does not reproduce signing keys from a dated example or claim that a checksum alone establishes who supplied the file.
Sources: [2]
3. Calculate the file’s digest locally
Choose a trusted tool documented for your environment and explicitly use the algorithm the publisher specifies. Microsoft documents PowerShell’s Get-FileHash command, including its LiteralPath option for an exact path and its default SHA256 algorithm. A different publisher algorithm requires a matching supported setting rather than relying on the default.
For a publisher-supplied SHA256 value, a PowerShell example is Get-FileHash -LiteralPath 'C:\Downloads\example.zip' -Algorithm SHA256. Replace only the example path with the intended local file. This is a documented calculation example, not a command that was run or a recommendation to execute the downloaded archive.
Sources: [1]
4. Compare the complete values
Check the algorithm, full calculated digest, and full official digest together. Do not compare only the first or last few characters or confuse a filename printed beside the value with part of the digest. If using a comparison tool, verify that it is comparing the intended values rather than two copies of the same text.
On a mismatch, leave the download unused and check the release, variant, selected file, and completeness of the download. A mismatch needs investigation; it does not by itself identify whether the cause was corruption, the wrong version, or malicious alteration. Follow the publisher’s supported recovery or verification instructions.
5. Record the result and its limits
Save the filename, release, algorithm, official source, check date, and match or mismatch result. Keep the verification record close to the file so a later replacement is not assumed to inherit the earlier result. Recalculate if the file being assessed changes.
A matching digest is one piece of evidence about the compared content. It is not a malware scan, a privacy assessment, or proof that installing the software is appropriate. If the publisher provides no supported checksum, record that limitation instead of inventing one or treating an unknown source as authoritative.
Your quick checklist
- The exact release, variant, and file are identified.
- The checksum comes from a verified official source.
- The calculation uses the stated algorithm without running the download.
- The complete values are compared and mismatches investigated.
- The record distinguishes integrity from authenticity and safety.
Sources & scope
Microsoft supports the PowerShell command example; Canonical supports the integrity/authenticity distinction. The selection and recordkeeping sequence is ATN editorial guidance. No download was inspected, executed, or certified safe.
- Microsoft PowerShell: Get-FileHash (opens in a new tab)Source checked October 10, 2026
- Canonical: Verify an Ubuntu download (opens in a new tab)Source checked October 10, 2026
Published October 10, 2026. No affiliate links or paid placements in this guide.
