Two APK files can have the same name and different contents. A SHA-256 checksum helps compare the bytes rather than the label. Use the complete digest for that release and check where the expected value came from. A match is useful evidence about the file; it cannot tell you everything the app will do after installation.

One file, one digest
A cryptographic digest represents the bytes of a file. A different file will normally have a different digest. A checksum comparison is meaningful only when the expected value comes from a trustworthy source and the downloaded file is the one being evaluated.
A matching digest
A matching SHA-256 value means the downloaded bytes agree with the expected file identity. You still need to trust the source of that expected value. The match does not inspect the app’s behaviour, authorize its publisher or establish game fairness. Those are separate questions even when all sixty-four characters agree.
A mismatched digest
Check that both sides refer to the same version and that the download completed. A publisher update legitimately changes file identity. Do not reuse a checksum from an earlier release or shorten it to a few characters. Stop until the difference is explained.
Read the identity fields together
The original filename, byte size, package name, version and minimum SDK describe different aspects of a package. Keep these fields together in a support question. None replaces a verified publisher statement or a full review of the app’s behavior.
Compare all sixty-four hexadecimal characters
A SHA-256 digest is commonly written as 64 hexadecimal characters. Compare the complete value, not just the first or last few characters. Make sure the file finished downloading and that the expected digest refers to the same release. Spaces used for presentation can be removed, but missing or changed characters must not be ignored.
Swipe sideways to read the full table →
| Observation | Interpretation |
|---|---|
| Full digest matches | File is consistent with the stated byte identity |
| Digest differs | Different bytes or a comparison error need explaining |
| Filename matches | Name alone does not establish byte identity |
| New release has a new digest | A legitimate update normally changes the bytes |
Choose the expected value independently
If an untrusted sender supplies both a file and its digest, a match only shows that their two items agree. The expected value should come from a verified release source. Pair the digest with package, version, size and date. A file can match a malicious sender’s digest perfectly; trust in the source is a different question from the hash calculation.
Frequently asked questions
Can two files with the same name have different hashes?
Yes. The filename is separate from the file contents.
Is a partial hash enough?
Use the complete SHA-256 value to compare the recorded identity.
Why is a new version’s checksum different?
Changing the bytes normally changes the digest, so compare with that version’s own release record.
Sources and scope
Android menus and access options vary by device. This site’s download record checks file identity; it does not include installing or running the app.
Adults 18+. Set time and spending boundaries before participation. Read the limits and breaks guide.
