Download
Every build below comes from the same published GitHub release, and every filename and size on this page is that release's own.
macOS
One build, both architectures
The macOS build is a universal binary. It runs natively on Intel Macs and on Apple Silicon, so there is no architecture to choose between.
Or install it with Homebrew. The fully qualified name is the point of the line, not verbosity: it is what lets one command trust the cask and install it in the same step.
$brew install --cask scottkw/storcat/storcat
Homebrew installs the command as storcat, all lowercase.
Windows
Installer or portable
The Windows build is 64-bit Intel and AMD only. There is no Windows-on-ARM build in this release, so there is no architecture to choose here either.
The installer puts the program on the machine and adds the usual shortcuts. The portable build is the program: it runs from wherever you put it, including a USB stick, and installs nothing. The installer is the smaller download because it carries the same program compressed and expands it during setup — the two files are one program packaged two ways, not two different builds.
Linux
Five builds, and here the architecture is a real choice
Take an amd64 build on an ordinary Intel or AMD machine and an arm64 build on a 64-bit ARM board such as a Raspberry Pi. The AppImage is built for x86_64 only, so on ARM the Debian package or the archive is the way in.
Install either Debian package with apt rather than dpkg: the package declares two library dependencies, and apt resolves them where dpkg would leave the package half-configured. The leading ./ is what tells apt the argument is a file in this folder and not the name of something to fetch.
$sudo apt install ./storcat_3.0.0_amd64.deb
$sudo apt install ./storcat_3.0.0_arm64.deb
Built for Debian 12 / Ubuntu 22.04 and compatible derivatives. Either package installs the program as StorCat, with the capitals — the same program Homebrew installs under a lowercase name.
The AppImage needs one command before it will start, to mark the file executable:
$chmod +x StorCat-v3.0.0-linux-x86_64.AppImage
StorCat-v3.0.0-linux-x86_64.AppImage is 82.6 MB because it bundles its own GTK and WebKit libraries instead of using the system's copies, and that bundling is the whole of the size difference. storcat_3.0.0_amd64.deb is 3.8 MB because it borrows those same libraries, which is also why it declares two package dependencies where the AppImage declares none. If your distribution is not one the Debian package was built for, the AppImage is the build that asks nothing of it.
Both compressed archives hold a single binary named StorCat and nothing else — no installer, no dependencies declared, nothing written outside the folder you unpack into.
Verify your download
Confirm the file arrived intact
The release carries a tenth file, checksums.txt, listing the SHA-256 of every artifact above. Download it from the same release, put it beside the file you downloaded, and run the command for your platform in the folder containing the file you downloaded. You get a one-word answer; there is nothing to compare by eye.
macOS and Linux
$shasum -a 256 --ignore-missing -c checksums.txt
--ignore-missing is doing real work. You have one of the nine files listed; without that flag the command treats the other eight as failures and reports a wall of errors for a download that is perfectly fine.
Windows
Three lines in PowerShell, in order, in the same folder. The last one prints OK or FAILED. Change the filename in the first line if you downloaded the installer instead.
>$f = 'StorCat-v3.0.0-windows-amd64.exe'
>$h = (Get-FileHash -Algorithm SHA256 -Path $f).Hash.ToLower()
>if (Select-String -Path checksums.txt -SimpleMatch -Quiet -Pattern "$h $f") { 'OK' } else { 'FAILED' }
Copy those lines rather than retyping them. -SimpleMatch and the two spaces inside the quoted pattern are both load-bearing, and a single space there reports FAILED for a download with nothing wrong with it.
If it says nothing was verified
shasum: checksums.txt: no file was verified means you are in the wrong folder — the file you downloaded is not in it. It is not a report about your download. Move checksums.txt next to the downloaded file, or change into that folder, and run it again.
What this establishes, exactly: the bytes you received are the bytes this release is serving — transfer integrity, and no more than that. The list sits on the same release as the files it describes, so it cannot speak to the origin of those bytes, only to whether they reached you unaltered.