QtPass is a multi-platform GUI for pass, the standard unix password manager.
Clone or download
Latest commit f3b41ae Dec 10, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
artwork Doxygen May 31, 2016
icons Should fix #383 May 3, 2018
localization Automated housekeeping Dec 10, 2018
main Saving Jul 6, 2018
src Automated housekeeping Dec 10, 2018
tests Need C++11 for tests Jun 26, 2018
.appveyor.yml Does appveyor do 5.10 yet (also CHANGELOG update) May 10, 2018
.coafile Added coala bears and did some minor cleanup Apr 20, 2016
.codecov.yml Run gcov manually Mar 10, 2017
.gitignore Ignore some more . . Jun 14, 2018
.linthub.yml Some tips from codefactor Apr 29, 2018
.travis.yml Travis build updated to Qt 5.10.1 May 15, 2018
CHANGELOG.md Automated housekeeping Dec 10, 2018
Doxyfile Updated doxyfile Jul 5, 2018
FAQ.md Add two entries in FAQ about the language Feb 10, 2018
LICENSE license and cleanup Jul 31, 2014
README.md Tested working on Mac Os HS with pinentry-mac Sep 25, 2018
appdmg.json fix path for mac release Oct 24, 2017
key_management.bat Change release Makefile to include gpg4win. Jun 14, 2015
qtpass.1 Apparently the man was completely wrong Oct 17, 2016
qtpass.appdata.xml Add appdata file for software centers May 17, 2016
qtpass.desktop Improvements to Dutch translations (desktop file) Sep 13, 2018
qtpass.iss Update to prevent the installer requesting admin Oct 24, 2018
qtpass.plist Updated plist, fixes #398 Jun 7, 2018
qtpass.pri Avoid adding -Wall if compiling with MSVC. Aug 25, 2018
qtpass.pro Forgotten update of .pro and .qcr file for merging of nl_NL and nl_BE Sep 13, 2018
qtpass.spec Version bump Jun 4, 2018
release-linux linux release May 8, 2015
release-mac Moved parentwin initialisation should fix #379 May 2, 2018
release-zip.mak Change release Makefile to include gpg4win. Jun 14, 2015
resources.qrc Forgotten update of .pro and .qcr file for merging of nl_NL and nl_BE Sep 13, 2018
windows.rc icons and such Aug 4, 2014



latest packaged version(s) Build Status Build status Coverity scan Coverage Status codecov CodeFactor Packaging status

QtPass is a GUI for pass, the standard unix password manager.


  • Using pass or git and gpg2 directly
  • Configurable shoulder surfing protection options
  • Cross platform: Linux, BSD, OS X and Windows
  • Per-folder user selection for multi recipient encryption
  • Multiple profiles
  • Easy onboarding

Logo based on Heart-padlock by AnonMoos.


From package

OpenSUSE & Fedora yum install qtpass dnf install qtpass

Debian, Ubuntu and derivates like Mint, Kali & Raspbian apt-get install qtpass

Arch Linux pacman -S qtpass

Gentoo emerge -atv qtpass

Sabayon equo install qtpass

FreeBSD pkg install qtpass

macOS brew cask install qtpass

Windows choco install qtpass

Packaging status

From Source


  • QtPass requires Qt 5.2 or later
  • The Linguist package is required to compile the translations.
  • For use of the fallback icons the SVG library is required.

At runtime the only real dependency is gpg2 but to make the most of it, you'll need git and pass too.

Your GPG has to be set-up with a graphical pinentry when applicable, same goes for git authentication. On Mac OS X this currently seems to only work with MacGPG2 from gpgtools or pinentry-mac from homebrew.

On most unix systems all you need is:

qmake && make && make install


This is done with make check

Codecoverage can be done with make lcov, make gcov, make coveralls and/or make codecov.

Be sure to first run: make distclean && qmake CONFIG+=coverage qtpass.pro

Security considerations

Using this program will not magically keep your passwords secure against compromised computers even if you use it in combination with a smartcard.

It does protect future and changed passwords though against anyone with access to your password store only but not your keys. Used with a smartcard it also protects against anyone just monitoring/copying all files/keystrokes on that machine and such an attacker would only gain access to the passwords you actually use. Once you plug in your smartcard and enter your PIN (or due to CVE-2015-3298 even without your PIN) all your passwords available to the machine can be decrypted by it, if there is malicious software targeted specifically against it installed (or at least one that knows how to use a smartcard).

To get better protection out of use with a smartcard even against a targeted attack I can think of at least two options:

  • The smartcard must require explicit confirmation for each decryption operation. Or if it just provides a counter for decrypted data you could at least notice an attack afterwards, though at quite some effort on your part.
  • Use a different smartcard for each (group of) key.
  • If using a YubiKey or U2F module or similar that requires a "button" press for other authentication methods you can use one OTP/U2F enabled WebDAV account per password (or groups of passwords) as a quite inconvenient workaround. Unfortunately I do not know of any WebDAV service with OTP support except ownCloud (so you would have to run your own server).

Known issues

  • Filtering (searching) breaks the tree/model sometimes
  • Starting without a correctly set password-store folder gives weird results in the tree view
  • On Mac OS X only the gpgtools MacGPG2 version works with passphrase or PIN

Planned features

  • Plugins based on field name, plugins follow same format as password files
  • Colour coding folders (possibly disabling folders you can't decrypt)
  • Optional table view of decrypted folder contents
  • Opening of (basic auth) urls in default browser? Possibly with helper plugin for filling out forms?
  • WebDAV (configuration) support
  • Some other form of remote storage that allows for accountability / auditing (web API to retrieve the .gpg files?)

Further reading


Website Source code Issue queue Chat