x64
user scopeanki-26.05-win-x64.msi
- SHA-256
- 2047f71d7771add993e15f2f01a56ea41617967ae5b3d6d3f402cbc40716c5e0
Anki · earlier release
The URL Anki published for this release, and the SHA-256 of every file in it, so you can prove the copy you have is that one and not something else wearing the same name.
Released 15 June 2026.
Anki is now on version 26.08.1. An older build stops getting security fixes, so install one only when you have a reason: a plugin that broke, a machine that cannot run the new one, a bug you need to reproduce. If you just want Anki, take the current version.
anki-26.05-win-x64.msi
anki-26.05-win-arm64.msi
This release shipped in more than one architecture, and the wrong one fails in a way that is not obvious: it either refuses to start or installs and then misbehaves. Take x64 unless the machine is genuinely 32-bit or ARM. Here is how to check which one your Windows is — and note that x86 means 32-bit, which is the part that catches people out.
The scope label says who the installer writes for. A user build installs into your own profile and needs no administrator rights; a machine build installs for everyone and does. On a work laptop where you cannot elevate, the user build is often the only one that will run at all. Silent install switches are on the same data.
Windows does this without installing anything. In PowerShell:
Get-FileHash .\anki-26.05-win-x64.msi -Algorithm SHA256
Compare what it prints with the value above. If they match, your copy is byte-for-byte the one Anki published. If they do not, it is a different file, whatever it is called and wherever it came from. Paste a hash into the verifier and it will tell you which release it belongs to.
If PowerShell is blocked by policy on the machine, the same thing works from plain cmd with certutil -hashfile anki-26.05-win-x64.msi SHA256. On macOS or Linux it is shasum -a 256 anki-26.05-win-x64.msi.
Publishers retire old releases, and we do not host copies, so a link from an earlier version can stop working without notice. Two ways it fails: an honest 404, or — more confusing — the server answers normally but hands you the current downloads page instead of the file. If what arrives is a few kilobytes of HTML rather than an installer, that is what happened.
The hash on this page stays useful either way. It still identifies Anki 26.05 wherever you find a copy, which is the whole point of publishing it: you can accept a file from somewhere else and still prove it is the one Anki built.