How to Verify Software Downloads: Checksums, GPG Signatures, and Code Signing for Windows, macOS, and Linux
checksum verificationGPG/PGPcode signingdownload safetyfile integritysoftware downloads

How to Verify Software Downloads: Checksums, GPG Signatures, and Code Signing for Windows, macOS, and Linux

DDownloads.link Editorial Team
2026-11-11
7 min read

A practical Windows, macOS, and Linux checklist for verifying software with SHA-256, GPG signatures, and code signing.

A download can be complete and still be the wrong file, a damaged copy, or a modified installer. This practical checklist shows how to verify a software download with SHA-256 or SHA-512 checksums, how to validate GPG signatures, and how to inspect platform code signing on Windows, macOS, and Linux before opening an executable, archive, portable build, or disk image.

Overview

Download verification answers two related questions: Did the file arrive unchanged? and Did it come from the expected publisher? A checksum is primarily an integrity check. It can show that your copy matches a published digest, but it does not by itself prove that the website publishing the digest is trustworthy. A digital signature adds publisher authentication when the signing key can be trusted. Platform code signing provides another layer for executable applications and installers.

Start with an official download page or a reputable project release page. Confirm the product name, version, operating system, CPU architecture, and file type before downloading. If you use a download mirror, compare its file against the checksum or signature published through the project’s trusted release channel. The guide to choosing a reliable software mirror provides additional context for that step.

For most modern downloads, prefer SHA-256 or SHA-512. MD5 is useful for detecting accidental changes in some legacy workflows, but it is not an appropriate choice for proving authenticity against an intentional attacker. SHA-1 should likewise not be selected for a new verification process unless a legacy project requires it and you understand the limitation.

Checklist by scenario

Any operating system: establish the reference

  1. Record the project name, version, file name, and download URL.
  2. Check that the file matches your system: Windows, macOS, or Linux; Intel or ARM where relevant; installer, archive, portable build, or disk image.
  3. Find the publisher’s checksum file, release notes, signature file, or signed manifest on the official project page.
  4. Calculate the digest locally and compare it character by character with the published value.
  5. If a signature is available, verify it and confirm the signer’s key fingerprint through a separate trusted channel when possible.
  6. Do not install the file if the result is a mismatch, an unknown signature, or an unexpected publisher warning. Download a fresh copy from the official source and investigate before proceeding.

Windows: installers, portable builds, and archives

PowerShell is convenient for a SHA-256 check:

Get-FileHash .\ExampleSetup.exe -Algorithm SHA256

To compare a file with a checksum manifest, use certutil:

certutil -hashfile "C:\Downloads\ExampleSetup.exe" SHA256

For an Authenticode-signed executable or installer, inspect the signature with PowerShell:

Get-AuthenticodeSignature "C:\Downloads\ExampleSetup.exe" | Format-List

Review the status and signer information rather than treating the presence of a signature as an automatic guarantee of safety. A ZIP file or other archive may not have an embedded Windows code signature; verify its checksum, then inspect its contents before extracting or running anything. If the file is a portable build, the same checks apply even though there is no traditional installation step.

macOS: DMG files and applications

Calculate a SHA-256 digest with the built-in shasum command:

shasum -a 256 ~/Downloads/Example.dmg

After mounting a disk image and locating the application, inspect its code signature:

codesign --verify --deep --strict --verbose=2 "/Applications/Example.app"

You can also ask Gatekeeper’s assessment service to assess the application:

spctl --assess --type execute --verbose=4 "/Applications/Example.app"

These commands complement, rather than replace, the checksum from the publisher. A DMG is a container, while the application inside it is the object normally checked for code signing and Gatekeeper assessment. Treat unexpected warnings, an unidentified developer message, or a signature that does not match the expected publisher as a reason to pause. Do not bypass a warning simply to complete an installation.

Linux: packages, archives, and GPG signatures

For a SHA-256 checksum, use:

sha256sum example.tar.gz

If the project provides a checksum file containing the expected digest and file name, use:

sha256sum --check SHA256SUMS

For SHA-512, replace the command with sha512sum. When a project publishes a detached GPG signature, import the project’s public key from a trusted source, inspect its fingerprint, and then verify the signature:

gpg --import project-release-key.asc
gpg --fingerprint KEY_ID
gpg --verify example.tar.gz.asc example.tar.gz

A successful GPG result means the signature matches the file and the imported key. It does not automatically prove that the key belongs to the project. Compare the fingerprint with the project’s official documentation, a release page, or another trusted channel. For distribution packages, prefer the operating system’s package manager and repository trust mechanism when that is the project’s documented installation path.

If you regularly work with GitHub Releases, first identify the correct asset for your platform and architecture; the GitHub Releases download guide can help prevent verification of the wrong file.

Printable one-off verification checklist

  • Source is the official project page or a documented mirror.
  • Version, operating system, architecture, and file type are correct.
  • Published SHA-256 or SHA-512 value was located.
  • Local checksum matches exactly.
  • GPG or platform signature was checked when available.
  • Signer, key fingerprint, or publisher identity was reviewed.
  • Unexpected warnings were investigated rather than bypassed.
  • Only after these checks was the file opened or installed.

What to double-check

A checksum mismatch does not always mean an attack. The download may be incomplete, the publisher may have replaced the release asset, or you may be comparing against a checksum for a different version or architecture. Check the exact file name and release page, download again, and compare from a second official location if one exists. Never “fix” a mismatch by editing the checksum file to match your local result.

Pay attention to file extensions and hidden extensions. A file presented as a PDF, image, or archive may actually be an executable with a misleading name. On Linux and macOS, also confirm that commands are pointing to the intended file rather than a similarly named copy in another directory.

Signatures require more interpretation than a simple digest. A GPG warning about an untrusted key is different from a bad signature, but neither should be ignored. An untrusted key means you have not established enough confidence in the key’s identity; a bad signature means the signature does not validate the file and should be treated as a failed check.

For installers, code signing and notarization checks are useful indicators, but they do not replace careful source selection. A valid signature can identify a signer without proving that the software is suitable for your environment. Review release notes, permissions, dependencies, and compatibility before deployment. For a broader update workflow, see the software upgrade checklist.

Common mistakes

  • Using a search result as proof of origin: Search engines can lead to lookalike sites. Navigate to the project’s known official domain when possible.
  • Comparing only the first few characters: Compare the complete digest. Copying the published value into a script without checking its source defeats the purpose.
  • Using MD5 for security decisions: Use SHA-256 or SHA-512 for current verification work.
  • Checking the archive but not its contents: Verify the archive first, then inspect the files it contains before execution.
  • Assuming a mirror is automatically equivalent to the publisher: A mirror is safer when its file matches an independently obtained official checksum or signature.
  • Ignoring the version: A valid checksum for an older release does not validate a newer download.
  • Bypassing operating-system warnings: Stop and confirm the publisher, source, and signature instead of disabling security controls as a shortcut.

When to revisit

Use this checklist for every major installer, developer tool, creator application, portable build, and mirror download—not only when a file looks suspicious. Revisit the commands when you change operating systems, move from Intel to ARM hardware, adopt a new package manager, or introduce an automated deployment process. Project release practices also change: a publisher may move from plain checksum files to signed manifests, rotate a GPG key, alter its archive layout, or publish different assets for a new platform.

Before a seasonal planning cycle or a large software refresh, test the verification workflow on a non-production download and document where your team obtains keys and reference checksums. Keep a short record of the source URL, version, digest, signature result, and verification date. If a release page, command, or operating-system security prompt behaves differently, consult the project’s current documentation rather than relying on an old screenshot or copied command.

For a final action, download from the official source, record the exact asset, calculate SHA-256 or SHA-512, verify any available GPG or platform signature, investigate every mismatch, and only then install. This process takes little time and creates a repeatable standard for safe software downloads across Windows, macOS, and Linux.

Related Topics

#checksum verification#GPG/PGP#code signing#download safety#file integrity#software downloads
D

Downloads.link Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.