Free PGP encryption tool
Encrypt a message to someone's PGP public key, decrypt a message sent to you, or generate a PGP key pair. Everything runs on your device, so your private key and your passphrase never leave the browser tab. You never sign in, and closing the tab destroys the key.
Anyone can hold this key. It only lets people encrypt messages to the person who holds the matching private key.
Copied to clipboard
How the PGP encryption tool works
Runs entirely in your browser
Paste a key
Paste the recipient's public key to encrypt, or your own private key to decrypt. If you have neither, generate a key pair on the third tab.
Encrypt or decrypt
Your device does the work. The private key is unlocked in the browser tab, used, and thrown away, so it never crosses the network where it could be intercepted or logged.
Copy the result
Copy the ASCII-armored message and send it over any channel you like, including one you do not trust. Only the private key holder can read it.
Private by design: nothing leaves your browser
A PGP tool that decrypts on a server needs your private key and your passphrase, which is the entire secret. Handing those to a web service defeats the point of using PGP at all. This one never sends them anywhere:
100% client-side
Keys, messages, and passphrases stay in the browser tab. The page downloads the OpenPGP library once, and nothing you type is part of that request.
Nothing stored or logged
No account, no analytics on what you encrypt, no history. Reload the page and every key you pasted is gone from memory.
Open and verifiable
Cryptography comes from OpenPGP.js, the audited open-source implementation of the OpenPGP standard. No custom-rolled cryptography.
Public key versus private key
- Your public key is meant to be published. It only lets other people encrypt messages to you.
- Your private key decrypts those messages, and nobody else may ever hold it.
- Because the keys are separate, two strangers can exchange encrypted messages without first agreeing on a shared secret.
- Losing the private key or its passphrase makes every message encrypted to it permanently unreadable, so back both up before you publish the public key.
When to use a desktop client instead
This tool is right for a one-off message, for learning how PGP works, or for a key whose loss you could absorb. For a key that protects sources, funds, or a production system, use a desktop client such as GnuPG, where the code never arrives fresh over the network. That advice costs us a page view and is still the correct advice.
Built for developers and security-conscious teams
Journalists, maintainers, and anyone sending something private through a channel they do not control. BlockSurvey applies the same public-key thinking to research data with zero-knowledge surveys, where responses are encrypted on the respondent's device.
Developers
Encrypt a credential or a disclosure to a maintainer's published key before opening the issue.
Security & IT teams
Receive vulnerability reports encrypted to your team's public key, and decrypt them without pasting the key into a server.
Journalists & researchers
Read a message from a source who encrypted it to your published key, on a machine that is offline.
Building something that handles sensitive data?
BlockSurvey runs on zero-knowledge surveys, so the responses you collect are never sold or mined. The same public-key idea protects every response before it leaves the respondent's device.