Verify your download with SHA-256

What a fingerprint answers

A file fingerprint helps answer a narrow, useful question: is this downloaded file the same as the release identified on this website? SHA-256 calculates a value from the contents of a file. Renaming an APK does not change its contents, so the same file can have a different filename and still produce the same fingerprint. A changed or incomplete file will ordinarily produce a different value.

This check is particularly useful when an installation fails, a download has been interrupted, or several copies are sitting in a downloads folder. It removes one uncertainty before you start changing device settings. It does not tell you that every behavior inside the application is safe.

Use the checker on this page

Choose the APK you downloaded in the file checker below. Your browser reads the selected file locally and calculates its SHA-256 fingerprint. The checker does not upload that file. It compares the result with the release information hosted on this website and shows both the calculated value and the expected value.

A match means the selected file matches that published fingerprint. A mismatch means you should not install it as the current release. First check whether you accidentally selected an older download or a different file. If you are unsure, delete only the unwanted download, get a fresh copy through the homepage, and compare again. Do not overwrite a mismatch by editing the expected fingerprint yourself.

Check it with PowerShell instead

On Windows, you can use PowerShell to perform an independent local calculation. Open PowerShell in the folder containing the download and run the command shown below. If the file has a different name, change the quoted filename to match it. The LiteralPath option treats the filename literally, and the algorithm is specified explicitly for clarity.

Compare the complete result with the published fingerprint, not just the first few characters. Uppercase and lowercase hexadecimal letters represent the same value. If you share a screenshot of the result for support, crop out your Windows username or any unrelated folder names that you do not want to disclose. There is no need to share the full contents of your downloads folder.

Understand the trust boundary

The expected fingerprint and the APK come from the same website. If that website were compromised and both were replaced, this comparison alone would not expose the replacement. A matching hash is evidence of file consistency, not evidence of an independent audit, verified publisher identity, or freedom from malicious code.

Keep normal device protections enabled after a successful check. If installation produces a security warning, a matching fingerprint is not a reason to ignore it. For a persistent mismatch, contact support with the date, download address, and calculated value. The website may have published a newer release since your original download, so include the approximate time you downloaded the file. These details allow the difference to be investigated without guessing whether the problem is your browser, an old copy, or the hosted package.

Keep the downloaded file unchanged during verification. If you replace it with a newer copy, select that new file and run the calculation again before comparing the result.