How we verify downloads

Short version: every download button on Softwares Academy goes to the developer’s own website or official release page. We never host, re-upload, repack or wrap an installer, and we show you the facts you need to check the file yourself.

The impostor domains we track, each with its source, are listed in the download site checker and published as open data on GitHub.

What a publisher-source review covers

  1. The official source. We find the developer’s own website and, for open-source software, the repository the developer controls. We cross-check them against each other: the website should link to the repository and the repository should link back.
  2. The current version and its date. We read these from the developer’s release page, not from another download site. Most download portals copy each other, which is how outdated versions spread.
  3. File names, sizes and SHA-256 checksums. Where the developer publishes a release on GitHub, the SHA-256 value comes from that release. You can compare it with your own copy in a few seconds (see below).
  4. Lookalike sites. Popular free tools attract copycat domains that rank in search results and hand out modified installers. We only name a site as a lookalike when the developer, or a reputable security or tech publication, has identified it.
  5. Install notes that matter. Supported Windows and macOS versions, ARM64 and Apple Silicon builds, the winget package ID, and known antivirus false positives with the developer’s own explanation.

Each program page shows its source-check date. Releases may change between checks; follow the official source for the current information. A page’s publication or layout-update date is separate from the date of its source review.

What a source check does not prove

A source check records the publisher information we found on the stated date. It is not a malware scan, a guarantee of safety or a hands-on compatibility test. Not every publisher supplies checksums, and not every entry has a stored file hash. Where a checksum is provided, compare the exact release and filename; a matching hash confirms identical bytes, not that software is harmless. Prices and release details can change after our check.

How to check a file you downloaded

On Windows, open PowerShell in the folder where the file is and run:

Get-FileHash -LiteralPath ".\file-name.exe" -Algorithm SHA256

On macOS or Linux, open Terminal and run:

shasum -a 256 file-name.dmg

Compare the calculated SHA-256 with the publisher’s value for the exact version, platform and filename. If the values differ, keep the file unopened and obtain a fresh copy from the official source. A matching hash identifies the expected bytes; it is not a malware scan.

What we will never do

  • Host software files on our own servers.
  • Use a “download manager”, “fast downloader” or any installer that adds offers.
  • Offer paid software for free, or link to cracks, keygens, activators or modified builds.
  • Invent ratings, download counts or reviews.

Ads and how this site is paid for

Softwares Academy is free to use and is funded by display advertising from Google AdSense. Ads are labelled “Advertisement” and are kept away from download buttons, so you can always tell which button is ours. No developer pays us to be listed or to be described favourably.

Found a problem?

If a link, version or checksum on our site is wrong, or you have spotted a fake download site we should warn about, please tell us through the contact page. We correct errors and update the page date when we do.

For files up to 128 MiB, use our local SHA-256 file checker to calculate and compare a publisher checksum without uploading the file. Use the operating-system commands for larger downloads.

Digital signatures and hands-on checks

A publisher-source review, a local file-hash comparison and a Windows digital-signature check are distinct checks. When we inspect a downloaded file, the entry identifies the filename, date and method; that does not imply we installed the application. Our Windows installer signature guide includes actual command observations and explains why a valid signature is not a safety guarantee.

Catalogue references and filename hints

A digest stored with a catalogue entry may be a publisher-displayed value or a local file measurement; read that entry’s source and method. The checker’s entry review date is a general record date, not necessarily the date a particular file was downloaded or hashed. A stored match agrees with those reference bytes; it does not prove a current release or software safety.

A filename is only a hint. Our dated WinRAR comparison measured two official same-name files with different bytes. In the SHA-256 checker, a filename-only difference therefore asks for a trusted reference, while a comparison with an expected digest explicitly reports agreement or disagreement with the value supplied.