One vault, three platforms
The web app is open right now — nothing to install. The Windows and Android apps are available below, each with a SHA-256 you can check before you run it.
🌐Web App
Available now
Runs in any modern browser, installs to your home screen, works offline after first visit. This is also the iPhone/iPad app.
Requires: a current browser (Chrome, Edge, Safari, Firefox).
Open the Web App🖥️Windows
v1.4.0 · 2026-08-16 · 142.7 MB
Requires: Windows 10 64-bit
Download installerSHA-256: b489b8a56470d6d6113751e6b0e61e1647001719b291dd6b473606f88b9c0961
📱Android
v1.4.0 · 2026-08-16 · 109.1 MB
Requires: Android 8.0
Download APKInstalled directly, not through the Play Store — Android will ask you to allow installs from your browser once. Check the SHA-256 below against the file you downloaded.
SHA-256: cf37ed4f8e3dfdffc811021765a3c661b0ed1bf7a5a6677dc91efede2eeafc1f
Verify your download
Every release is published with a manifest listing each file's SHA-256, signed by a key that never touches this web server. Three ways to check, in increasing order of how little you have to trust us:
1 · By hand. Compare against the checksum shown beside the release above:
# Windows (PowerShell)
Get-FileHash .\Keepsake-win-Setup.exe -Algorithm SHA256
# macOS / Linux
sha256sum Keepsake-win-Setup.exe
2 · In your browser. Drop the file on the verify page and it is hashed locally and looked up in the signed manifest.
3 · Without trusting this website at all. From a copy of Keepsake you already had installed:
Keepsake.exe --verify Keepsake-win-Setup.exe
Options 1 and 2 both take the checksum from this server, so a compromise of the server could defeat them — we would rather say that than imply otherwise. Option 3 checks the manifest's signature against the release public key compiled into a binary that was on your machine before this download existed. That key is also printed on the security page; note it down once and you can verify any future release by hand, forever, without us.
Windows installers are not yet code-signed, so Windows will show an "unrecognised app" warning on first run. That is a statement about a certificate we have not bought, not about the file — which is exactly why the checks above exist.
Version history
Windows
- Entitlement is re-derived from the licence signature on every check, so editing the database no longer grants Premium. - A wound-back system clock no longer un-expires a licence. - Revoked keys are refused at activation; an unreachable feed changes nothing. - Rotating our signing key no longer invalidates licences already issued. - High-accuracy Urdu (Nastaliq) ships sealed to the licence: 4.2% character error against stock 33.3%. - Emergency Kit files are readable again, and dependency versions are now locked.
Android
- Entitlement is re-derived from the licence signature on every check, so editing the database no longer grants Premium. - A wound-back system clock no longer un-expires a licence. - Revoked keys are refused at activation; an unreachable feed changes nothing. - Rotating our signing key no longer invalidates licences already issued. - High-accuracy Urdu (Nastaliq) ships sealed to the licence: 4.2% character error against stock 33.3%. - Emergency Kit files are readable again, and dependency versions are now locked.
Release RSS feed — new versions, changelogs and checksums, straight to your reader.
Last verified — by tools\deploy\deploy.bat downloads-probe. Every claim on this site is listed, with its evidence, in the claim ledger.