This page explains where the versions, SHA256 checksums and files on APPWL app pages come from, and how we make sure they match the official release.
Where installers come from
Every installer is downloaded directly from the app's official channel: the project's download page, its official GitHub Releases, or its official download server (for example download.videolan.org, download.gimp.org, download.kde.org, voidtools.com). The "Official link" next to each file on an app page is that file's original address, so you can always fetch the same file from there.
We never modify or repackage installers, never add bundled software, and never offer cracked or "modified portable" builds.
Where SHA256 checksums come from
Each checksum states its source:
- Matches the official published hash — the project publishes a hash on its release page or in a checksums, .sha256 or .DIGEST file; we compute the SHA256 of the downloaded file and compare it. Where the project signs releases with GPG (for example Notepad++, HandBrake, KeePassXC, VLC, LibreOffice) we also verify the signature.
- Matches the GitHub Release digest — the project publishes no separate hash, but GitHub computes a SHA256 digest for the release asset; we compare against that.
- Computed locally — there is no official hash to compare against (for example GitHub's auto-generated source archives); we show our own value and label it as such.
Unverified hashes never appear on the site. To check a file yourself, see our SHA256 guide (Chinese): /guides/verify-sha256.
Where the Quark Drive files come from
The files in our Quark Drive shares are the same files downloaded from the official channels above and checked against their SHA256, uploaded unchanged apart from the file name; the app's license is included in the folder. If the SHA256 of your download matches the page, you have the official build. The drive is simply a faster mirror; the official release is the reference.
How fast we follow new releases
- For apps with a GitHub repository, the site checks the official GitHub Releases every 6 hours. When a new stable release appears, the app page switches to the new version, release date, official download link and GitHub's SHA256 digest, with the official release notes. Our target is within 48 hours of the upstream release.
- Drive copies are downloaded, verified and uploaded by hand, so they can lag a little; until then the page states clearly that the drive still holds the older version.
- Apps without a GitHub repository (for example Everything, GIMP, VLC, LibreOffice and Kdenlive, which ship from their own servers) are followed by our editors manually.
- The "Checked" date only changes when the page content really changes.
Screenshots
Screenshots on app pages were taken by our editors while actually running the official installer in a test environment — the setup wizard, first launch and language settings — and the caption states the environment. We never use marketing images, other people's screenshots or generated images; if we could not take real screenshots, the page has none.
Ratings
Ratings come only from real visitors to this site, and each visitor counts once per app (their latest rating). The average is shown — and added to the page's structured data — only once at least 5 people have rated. We never pre-fill ratings or import them from other sites.
Reporting a broken link or a bad file
- Broken drive link: use "Link broken? Let us know" in the download section. The site also checks drive links automatically on a schedule.
- Checksum mismatch or a file that looks tampered with: use the same button, stop the installation and download again from the official link.
- Copyright issues: use the takedown page; we remove content after checking the claim.
This site is maintained by the APPWL editorial team — see About APPWL.