Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Release file differences on the homepage and the github page
05-02-2026, 10:21 AM
Post: #1
Release file differences on the homepage and the github page
Hello!

You can download the emulator release either from the homepage downloads section, or from the github releases assets. But these downloaded files are not the same. For example checking the 1.20.3 windows portable release, inside the zip the 'PPSSPPWindows64.exe' file has a different filesize and hash depending whether you downloaded it from the home page or the github. The github package is also missing the 'PPSSPPWindows.exe' file, but not sure if that matters.

Why are the .exe files having different sizes and should the files be identical?

Thanks for the emulator!
Find all posts by this user
Quote this message in a reply
05-03-2026, 02:20 PM
Post: #2
RE: Release file differences on the homepage and the github page
They're built two different ways. The github assets are built with github CI (which I think uses the latest compilers, or whatever compilers are on there) while the official releases are built using MSVC build tools 2022, so that we can still function on Windows 7.
Find all posts by this user
Quote this message in a reply
05-06-2026, 04:37 PM
Post: #3
RE: Release file differences on the homepage and the github page
Thanks for the answer!
Find all posts by this user
Quote this message in a reply
05-10-2026, 06:22 PM
Post: #4
RE: Release file differences on the homepage and the github page
It’s a common point of confusion, but the short answer is that the site builds and the GitHub releases usually come from different build environments. The version on the homepage is often an automated "gold" build compiled on the dev's own build server, whereas GitHub assets are frequently generated by GitHub Actions. Even with the same source code, different compiler versions or optimization flags will spit out different hashes and file sizes. As for the missing 32-bit PPSSPPWindows.exe on GitHub, most modern CI pipelines are dropping x86 support to save on compile time and bandwidth, while the main site usually keeps the "complete" legacy bundle for maximum compatibility. As long as you're grabbing them from those two official sources, you're safe—just don't expect the hashes to match up perfectly across different mirrors.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump: