-
Notifications
You must be signed in to change notification settings - Fork 0
Clients
Cristhian Melo edited this page Jul 20, 2026
·
2 revisions
rpass uses the standard password-store format. Any client compatible with pass works with rpass — there are many options across all platforms.
| Client | Platform | Notes |
|---|---|---|
| Raycast | macOS / Linux / Windows | Uses rpass --json output natively |
| Vicinae | macOS / Linux | Menubar app, browser autofill |
| Pass for iOS | iPhone / iPad | Git sync, TOTP, Safari extension |
| Android Password Store | Android | Git sync, OpenKeychain integration |
| QtPass | Linux / Windows / macOS | GUI frontend for pass |
| Browserpass | Browser extension | Chrome, Firefox |
Note
This list is not exhaustive. Any app that reads the password-store format (.gpg files + .gpg-id) is compatible. Check the password-store ecosystem for more options.
All clients need two things:
- A remote Git repository — to sync your store across devices. See Getting Started for how to push your store to GitHub, GitLab, or any Git host.
- Your GPG private key — imported into the client or its companion app. See GPG Keys for the full workflow.
Each client has its own setup guide — refer to their official documentation. For Pass for iOS in particular, see the Pass for iOS wiki.
Important
Before importing your GPG key into any mobile client, check which key algorithms it supports. Not all clients support modern key types. See GPG Keys → Algorithm compatibility.