macOS
Apple Silicon (M1 and newer) · macOS 13 or newer
Download DMG · 127 MBSHA-256
351441629786f6d1b61e620cd0df2d5cf57d753096ffd08891d4a87ee12436cf
Aszendra for macOS, Windows and Linux
Free, no account. Version 1.10.1, released 19. Oktober 2026.
Windows
64-bit (x64) · Windows 10 or newer
Download installer · 109 MBSHA-256
03129f9a8e387a5595035162cb847791f550371afa973fea2e86789bda5d94e0
Linux
x64 · Ubuntu 22.04, Debian 12, Fedora 39 or newer
.deb for Ubuntu and Debian · 98 MB AppImage for other distributions · 124 MBSHA-256 (.deb)
d2accc1a0c3769a1c95fee873b560bfbf094f05e7060da35c3a718cd0afd6430
SHA-256 (AppImage)
e9ab47181e87f9f420f4fcec5f4d53a3812504140b15f725ba515cff47a0f540
Not here yet
Intel Macs and Windows on ARM have no package of their own yet. On Windows-on-ARM the x64 package runs under emulation. For Intel Macs there is currently no route — a package in which the password vault silently goes missing would be worse than none. On Linux there is only x64 for now, no arm64.
Why your system warns you on first launch
Aszendra is not yet signed with a purchased certificate. That does not mean the file was tampered with — it means Apple and Microsoft have not confirmed the publisher, because doing so requires a paid developer certificate. Both systems therefore show a warning. Here is how to get past it, and how to check for yourself that you downloaded the right thing.
macOS
After you double-click the DMG and drag Aszendra into Applications, macOS will report on first launch that the app comes from an unverified developer. Since macOS 15, right-click → Open no longer suffices. The route is:
- Launch Aszendra once and dismiss the warning.
- Open System Settings → Privacy & Security and scroll all the way down.
- There you'll find “Aszendra was blocked” with an Open Anyway button. Click it and confirm with your fingerprint or password.
This is a one-time step. Later launches and updates don't ask again.
Windows
SmartScreen reports “Windows protected your PC”. Click More info, then Run anyway. Also a one-time step.
Linux
On Ubuntu and Debian, take the .deb: double-click it,
or run sudo apt install ./aszendra_*.deb in a terminal. It
sets up Chromium's sandbox correctly, and from Ubuntu 24.04 on also the
AppArmor profile it needs. Aszendra then puts updates in your
downloads folder, and you install them the same way.
Everywhere else, the AppImage: make it executable
(chmod +x Aszendra-*.AppImage) and start it. It replaces
itself when an update arrives. On Ubuntu 24.04 and newer, AppArmor
denies an AppImage its sandbox; there, the .deb is the right choice.
Check it yourself
The checksum above belongs to exactly the file behind the button. If it matches what arrives on your machine, the file was not altered in transit.
macOS:
shasum -a 256 ~/Downloads/Aszendra-1.10.1-arm64.dmgWindows (PowerShell):
Get-FileHash -Algorithm SHA256 "$env:USERPROFILE\Downloads\Aszendra-Setup-1.10.1-x64.exe"Linux:
sha256sum ~/Downloads/aszendra_1.10.1_amd64.deb ~/Downloads/Aszendra-1.10.1-x86_64.AppImageAszendra checks the updates it fetches later the same way — and in addition against a signature that can only be produced with our private key. How that works →
System requirements
| macOS | Windows | Linux | |
|---|---|---|---|
| Version | 13 (Ventura) or newer | 10 (1809) or newer | Ubuntu 22.04, Debian 12, Fedora 39 or newer |
| Architecture | arm64 (Apple Silicon) | x64 | x64 |
| Memory | 4 GB, 8 GB recommended | ||
| Disk | ~420 MB | ~390 MB | ~300 MB |
Moving from another browser
On first launch Aszendra reads bookmarks from Chrome, Edge, Brave, Firefox and Safari — if you let it. Nothing is taken over without asking, and nothing is changed or deleted. Passwords are not imported automatically; you add those to the vault deliberately.
Older versions
Every version ever released stays reachable at its fixed address and is never overwritten — otherwise every checksum would be worthless. The list is in the changelog.