Frequently Asked Questions (FAQ)
Questions are grouped by topic. Click any question to open its answer.
Getting Started
Section titled “Getting Started”How do I get GpgFrontend?
Go to the Downloads page and click the download button. Then follow Getting Started for the install steps on your system.
Which operating systems does GpgFrontend support?
GpgFrontend runs on Windows, macOS, and Linux. On BSD you have to build it from source. For the exact versions, see System Requirements.
How do I update GpgFrontend to the latest version?
Get the newest version from the Downloads page. Then:
Run the new installer.
Replace the old app with the new one.
Replace the old AppImage file with the new one.
Your settings and keys are kept, unless the release notes say otherwise. If you installed from an app store or a package manager, update there instead.
The built-in update check offers newer fix releases of your own series (for example, 2.2.x). If your series is old, it also offers the current release and marks it (recommended). If your series gets no more fixes, it only offers the current release. You choose what to download. See Which Updates the App Offers.
How does GpgFrontend tell me about a new version?
Only if you allow it. The update check is off unless you turn it on. You can do that on the last page of the Welcome to GpgFrontend window, which opens at the first start, or in Settings > Updates.
When it is on, GpgFrontend checks quietly in the background when it starts, at most once a day. It never pops up a window. If a newer version exists, a small badge appears on Help > Check for Updates. Click it to see what is new and to download it.
The check does not ask GitHub. It downloads a signed list of releases from
GpgFrontend’s own update server (update.bktus.com), and checks the
signature before it trusts the list. See
Finding Your Settings and
How Releases and Updates Work.
The Flatpak and Mac App Store builds have no update check. Flathub and the App Store deliver their updates.
Is there still a Qt5 build?
Not for v2.2.x. Qt is the toolkit GpgFrontend is built with, and v2.2.x needs Qt6. Qt5 builds were only made for the older v2.1.x line. If your system cannot run Qt6, for example Windows 7, you need a v2.1.x release. See Older Versions Still Supported and System Requirements.
OpenPGP and the Engines
Section titled “OpenPGP and the Engines”How do OpenPGP, PGP, and GnuPG (GPG) relate?
- OpenPGP is the open standard for encrypted email, files, and digital signatures. The current version of the standard is RFC 9580. It replaced the older RFC 4880.
- PGP was the original closed-source software from the 1990s. It is rarely used today, but people often say “PGP” when they mean the OpenPGP standard.
- GnuPG (GPG) is the most widely used free, open-source program that follows the OpenPGP standard.
Today, when people say “PGP encryption”, they almost always mean the OpenPGP standard. The tool they actually use is GnuPG (GPG) or another compatible app.
GpgFrontend is an easy-to-use app for OpenPGP. It uses GnuPG as its main engine. Since the v2.2.x series, it also offers a second engine, rPGP.
Which engines does GpgFrontend use?
The engine is the part of GpgFrontend that does the encryption work. GpgFrontend has two:
- GnuPG is the default and main engine in the regular desktop edition. It is proven and widely used. It is the best choice if you need full compatibility with an existing GnuPG setup.
- rPGP is a second engine, written in Rust and built into GpgFrontend. It supports newer OpenPGP features, including version 6 of the standard (RFC 9580).
What is the rPGP engine?
rPGP is the second engine, next to GnuPG. It is built into GpgFrontend, so GpgFrontend can do everyday OpenPGP tasks even when GnuPG is not installed. See the question above for how the two engines compare.
Does rPGP replace GnuPG in GpgFrontend?
No. In the regular GpgFrontend desktop edition, GnuPG is still the default and main engine.
The rPGP engine is an extra. It is used where GnuPG is not available, such as in the Mac App Store edition, and for newer OpenPGP features. Some advanced GnuPG features, such as smart cards, do not work with rPGP.
Can I use the same keys with GnuPG and rPGP?
Not always. In GpgFrontend, GnuPG and rPGP store their keys separately. Some key types, data formats, and newer OpenPGP features do not work the same way in both engines.
If you need full compatibility with an existing GnuPG setup, use the regular GpgFrontend desktop edition with the GnuPG engine.
GpgFrontend Lite (Mac App Store)
Section titled “GpgFrontend Lite (Mac App Store)”Is GpgFrontend available on the Mac App Store?
Yes, as GpgFrontend Lite. It is a lightweight edition that uses the rPGP engine and does not include GnuPG.
The regular GpgFrontend desktop edition is not on the Mac App Store. The next question explains why. If you need the regular edition, get it from the Downloads page or with Homebrew.
Why is there a separate GpgFrontend Lite edition?
Every Mac App Store app must run in the macOS App Sandbox. A sandbox is a closed area that keeps an app away from the rest of your system.
The regular GpgFrontend desktop edition is built around GnuPG. It offers advanced settings, works with a GnuPG setup you already have, and reaches your normal desktop environment. These things do not fit inside the sandbox.
So GpgFrontend Lite is a separate edition, not a replacement for the regular one. It uses the rPGP engine and keeps its keys inside the sandbox storage that macOS manages for the app. It still handles the everyday OpenPGP tasks: encryption, decryption, signing, verification, and local key management.
| Feature | Regular Desktop Edition | Lite Edition (App Store) |
|---|---|---|
| Engine | GnuPG (Primary) + rPGP | rPGP Only (Pure Rust) |
| Environment | Full System Access | macOS Sandbox (Enhanced Security) |
| GnuPG Integration | Yes (System GPG) | No (Self-contained) |
| Best For | Professional & Critical Work | Modern v6 Workflows & Quick Tasks |
Where are keys stored in GpgFrontend Lite?
GpgFrontend Lite stores its keys on your Mac, inside the sandbox storage that macOS manages for the app. It does not upload your keys or messages to any server.
Removing the app or resetting your system can erase this storage. So back up the OpenPGP keys you create or import in GpgFrontend Lite. If your keys are lost, your encrypted data cannot be recovered.
Can GpgFrontend Lite use my existing GnuPG keyring?
No. GpgFrontend Lite does not include GnuPG and does not connect to it. So it cannot directly use the keys you already have in GnuPG.
To use a key from another OpenPGP app, export the key from that app and import it into GpgFrontend Lite. Be careful when you export secret keys, and keep your backups safe.
Which version should I use: GpgFrontend or GpgFrontend Lite?
Use the regular GpgFrontend desktop edition if you need GnuPG, smart cards, advanced settings, or full compatibility with an existing GnuPG setup.
Use GpgFrontend Lite if you prefer a simple Mac App Store app for everyday OpenPGP tasks on macOS.
Why GPG / OpenPGP
Section titled “Why GPG / OpenPGP”Why choose GPG/OpenPGP over other encryption tools?
- Open source and reviewed: GPG is open-source, free, and maintained by a large community. Its code has been reviewed for decades, which builds security and trust.
- You are not tied to one company: it is fully based on an open standard. It works across major platforms, email apps, and tools. You can take your keys and data anywhere.
- Full set of features: encryption with a passphrase or with keys, digital signatures, key management, key revocation, and the “web of trust” (a way for users to confirm each other’s keys).
- Transparency and control: every encryption step is visible and adjustable. You decide how your data is secured, with no hidden algorithms or automation.
- Works together: it is compatible with any software that follows OpenPGP, so your data stays easy to read and share.
Closed-source tools may limit which platforms they run on, hide how data is encrypted, or tie you to their own products.
How secure is GPG?
When used correctly, GPG gives strong protection:
- Strong algorithms and key sizes are available, in line with modern standards.
- Open source: the code is constantly reviewed by experts around the world.
- No mass leaks: no major flaw has ever led to a wide theft of GPG private keys.
- Most risks come from user mistakes, not from GPG itself. Examples are weak passphrases, badly stored keys, and malware on the device.
In short: how you look after your keys and passphrase matters just as much as the software you use.
Has GnuPG ever been successfully attacked?
According to the official GnuPG FAQ 11.8:
“If you mean, ‘has GnuPG traffic ever been successfully cryptanalyzed?’, the answer is a flat ‘no’. We are unaware of any credible reports of any of the ciphers used in GnuPG having ever been successfully cryptanalyzed.”
“Cryptanalyzed” means that someone broke the encryption itself.
What makes GPG/OpenPGP different from instant messengers or built-in encryption?
- No accounts or servers: you don’t need to register or rely on any service.
- Long-term trust: keys can be used for years, to sign files, email, and software, and to build a “web of trust”.
- Works offline: encrypt or sign files and send them any way you like, with no internet needed.
- Manual and open: everything is under your control, with no forced automation or cloud syncing.
Instant messengers (Signal, Matrix, etc.) are great for real-time chat. But they need accounts, central servers, and frequent key changes. So they are less suited to offline or anonymous use.
When is GPG/OpenPGP the best tool?
- Secure file exchange with strangers: journalists, whistleblowers, or anyone who needs to pass on documents anonymously.
- Publishing signed content: software releases, scientific results, or public statements that people must be able to check for years.
- Air-gapped environments: moving encrypted data between computers that are never connected to the internet.
- Full transparency: every encryption step is visible and can be checked.
Why not just use password-based encryption?
Public-key encryption (as in GPG) uses a pair of keys: a public key that you share, and a private key that you keep. It is more flexible and secure:
- No need to share passwords in advance; you only publish your public key.
- Anyone can encrypt for you, even if you’ve never met.
- Digital signatures prove who wrote a message and that it wasn’t changed.
- Keys can be revoked or replaced at any time without breaking old data.
Can I use GPG with keys or data from other programs?
Yes. If your keys and encrypted data are in an OpenPGP-compatible format, GnuPG and GpgFrontend can work with them. This includes most keys and data from other GPG programs and from older PGP programs.
Using GpgFrontend
Section titled “Using GpgFrontend”What if I see “GnuPG not installed correctly”?
This message mainly applies to GpgFrontend versions before 2.2.0, or to tasks that need GnuPG in the regular desktop edition.
Since GpgFrontend 2.2.0, if GnuPG is not available, GpgFrontend switches to the built-in rPGP engine. The app still starts and offers the basic OpenPGP features.
To use the GnuPG engine, the keys you already have in GnuPG, smart cards, or other GnuPG-only features, install GnuPG:
Recent regular desktop builds include GnuPG. If needed, you can also download GnuPG from the official GnuPG website.
Install GnuPG using Homebrew with brew install gnupg.
Install GnuPG via your package manager, for example sudo apt install gpg
or sudo dnf install gnupg.
How do I import or export keys in GpgFrontend?
- In the main window, click Keys > Manage Keys. The KeyPair Management window opens.
- Open its Key menu. It has Import Key and Export Key.
You can also drag key files and drop them onto the Key ToolBox, the key list in the main window. See Import and Export Keys.
Can I encrypt and decrypt files as well as text?
Yes, GpgFrontend handles both text and files. See File Operations and Text Operations.
Does GpgFrontend support OpenPGP smart cards or tokens?
Yes, if your GnuPG supports smart cards. Smart cards need the GnuPG engine. The rPGP engine does not support smart cards or tokens.
To manage a card, click Advanced > Open Smart Card Controller. This opens the Smart Card Controller window. Sandboxed builds (Flatpak and the Mac App Store edition) do not have this window. See OpenPGP Smart Cards.
Is GpgFrontend available in my language?
GpgFrontend comes in these languages:
- English
- Chinese (Simplified)
- Chinese (Traditional)
- French
- German
- Italian
- Spanish
- Russian
- Polish
- Turkish
To change the language, open Settings, choose General, and pick your language under Language. Want to help translate? See the translation guide.
What is a profile?
A profile is one complete GpgFrontend setup: its own keys, its own settings, and its own saved state. You already have one, and one is enough for most people.
Make a second one if you want to keep work and personal keys apart, or if you want a setup you can carry to another computer. See Profiles.
Can I move my whole setup to another computer?
Yes. Open the Profiles menu and choose Export This Profile. That writes
your keys, settings and saved state into a single .gfp file, protected by a
passphrase you choose.
On the other computer, use Import Profile File, or just double-click the file. See Profiles.
The Mac App Store Lite edition has no Profiles menu. There, back up your keys with a KeyPackage instead.
What is IM Encrypt?
Normal encrypted text is a big block that chat apps often break. IM Encrypt turns your message into one short line that pastes cleanly into any messenger.
You find it in the Operations menu, while a text tab is open. There are no toolbar buttons for it.
The other person pastes the line into GpgFrontend and clicks Decrypt as usual. See Instant Messaging.
What are Nightly versions?
Nightly versions are test builds. They are made automatically from the newest code, with new features and fixes that are still being tested. They are less stable than official releases and may change in ways that break things. Do not use them for important work. Get them from the Downloads page.
Nightly files are not signed with the maintainer’s OpenPGP key. Instead, each
nightly build comes with a checksum list (SHA256SUMS.txt). The project’s
build on GitHub signs that list. Always check the list, then check your
download against it. See
Check a Test Build.
Nightly downloads are larger than official ones, because they include information for finding bugs. The app runs just as fast. Please report problems and feedback on GitHub.
For how stable, beta, release candidate and nightly builds relate, see Stable, Beta, Release Candidate and Nightly in the Version Numbering Policy.
Changes in Recent Versions
Section titled “Changes in Recent Versions”Looking for something that moved or went away after an update? Start here.
I cannot find a setting. Where did the tabs go?
The settings window was rebuilt in v2.2.2. The row of tabs across the top is gone. In its place there is a search box and a list of pages down the left side.
Type what you are looking for into the search box. It matches page names and the settings on them, so you do not have to guess. See Finding Your Settings.
Where did my favourite keys go?
The Favourite tab was replaced by key categories in v2.2.2. Categories do the same job and more: you can have as many as you like, name them, and give each one a colour.
Old favourites are not carried over, so you need to make a category and put those keys back in it. See Key Categories.
Why can I no longer generate a DSA key?
DSA is an older key type. With the rPGP engine, you cannot make new DSA keys, or new RSA keys below 3072 bits. The current OpenPGP standard (RFC 9580) says new keys of these kinds must not be made.
Existing keys of these types still import and still work. The GnuPG engine still offers both if you really need one.
What happened to the startup self-check?
It was removed in v2.2.2. GpgFrontend no longer verifies its own libraries while starting.
It is still a good idea to check that your download is genuine. The best time to do that is before you install. See Code & Binary Verify.
Your Keys, Privacy, and Security
Section titled “Your Keys, Privacy, and Security”How does GpgFrontend handle passphrases or PINs?
This depends on the engine used by the active key database.
With the GnuPG engine, GpgFrontend never reads or stores your GPG key
passphrases or smart card PINs. GnuPG asks for them itself, with its own
helper programs (pinentry and gpg-agent), separate from GpgFrontend.
With the rPGP engine, there are no such helper programs. So GpgFrontend asks for the passphrase itself and passes it to the rPGP engine. The engine keeps it in memory for a while, so you do not have to type it again for every task. It is never written to disk. You can set how long it is kept on the rPGP page in Settings.
For GpgFrontend’s own encryption (for example a KeyPackage), passphrases and PINs are used only in memory and cleared right away. On the Advanced page in Settings, you can change Secure Level and Application Key Protection. See Memory Security and App Secure Key.
Can lost passwords or keys be recovered?
No. Neither GpgFrontend nor the maintainer can recover a lost passphrase or private key. That is what keeps your data safe from everyone else. So back up your private key and remember your passphrase.
How does GpgFrontend keep communication secure?
It uses a proven OpenPGP engine (GnuPG by default, or the rPGP engine when chosen) with strong encryption algorithms. Only the intended recipients can decrypt your messages.
What data does GpgFrontend collect?
GpgFrontend does not collect or send any personal or usage data. All encryption runs locally. Update checks are off unless you turn them on, and there is no tracking or analytics built in.
There is also no AI feature in the app, and nothing you do is ever sent to an AI service. See the AI Policy.
Community and Support
Section titled “Community and Support”Is GpgFrontend really free? Can I donate?
Yes, it is completely free, and no, the project does not take donations. There is no paid version and no locked features. If someone asks you to pay for GpgFrontend, it is not from this project. See Free & No Donations for the full story, and for ways to help that matter more than money.
Is AI used to build GpgFrontend?
AI coding tools help write ordinary code, tests and documentation, under the direction and review of the maintainer. There is no AI in the app itself, and AI does not write the cryptography; that is done by GnuPG and rPGP. The AI Policy explains the whole arrangement.
Found a bug?
Please report it as an issue on GitHub. If you are not on GitHub, you can write to the maintainer instead. See Contact.
Interested in contributing?
You are welcome to change GpgFrontend’s code and send your improvements as a Pull Request on GitHub. You can also send patches by email if you prefer to contribute anonymously. See Contributing to GpgFrontend to get started, and the AI Policy if you use AI tools in your work.