Free online PGP-style encryption: RSA-2048/4096 hybrid AES-256-GCM with public-key fingerprints and local key generation — runs in your browser (not GnuPG wire-compatible).
TL;DR: Free online PGP-style encryption tool: RSA-2048/4096 wraps a random AES-256-GCM session key, with SPKI SHA-256 public-key fingerprints for out-of-band checks. Web Crypto API, local only — keys never leave your device (not GnuPG wire-compatible).
For local tools, open DevTools → Network and search your input — it should not appear in requests.
Next steps
Usage Guide
When you need generate → encrypt → decrypt in the browser without pasting plaintext to a third-party server, use this tool. It builds on Web Crypto (RSA-OAEP + AES-256-GCM hybrid encryption), offers RSA-2048/4096, and shows an SPKI SHA-256 public-key fingerprint for out-of-band checks. Keys and ciphertext appear as PEM-style text, entirely on-device. Important: this is a local asymmetric workflow, not an OpenPGP/GnuPG-compatible mail encryption suite.
1. Three workflows
Hybrid encryption means a random AES-256-GCM key encrypts the body while RSA-OAEP protects that session key. Plaintext length is not bound by the RSA OAEP limit. Losing the private key means the ciphertext is gone — back it up offline right after generation.
- Generate: pick RSA-2048 or 4096, create a key pair, note the fingerprint, then store both keys safely. Use “Use for Encrypt / Decrypt” to fill the matching tab.
- Encrypt: on Encrypt, paste the recipient public key (or fill it from Generate) and plaintext to get a transferable ciphertext payload.
- Decrypt: on Decrypt, paste your private key and ciphertext to restore plaintext.
2. Fingerprints and key checks
Use 2048 for faster demos; choose 4096 when you want a longer-lived key. RSA only wraps a 32-byte session key; the body stays under AES-GCM.
- The fingerprint is SHA-256 of the public key SPKI DER, grouped for phone/in-person checks — not an OpenPGP v4 fingerprint.
- Confirm the fingerprint over a second channel before encrypting to reduce fake-public-key risk.
- OpenPGP key armor (BEGIN PGP PUBLIC KEY BLOCK) is rejected; use SPKI/PKCS#8 keys from this tool.
- PKCS#1 BEGIN RSA PRIVATE KEY also fails — Web Crypto needs PKCS#8 (BEGIN PRIVATE KEY).
3. Security boundaries (read this)
- Public keys can be shared; private keys must never land in chat logs, tickets, or screenshots.
- Keys stay local here, but browser extensions, corporate proxies, or shared machines can still snoop the clipboard — use a trusted device for sensitive work.
- Do not assume gpg CLI can decrypt the output: algorithms and wrapping follow this site convention (armored JSON) for an in-browser loop and teaching demos.
- For real OpenPGP interop (mail, key servers), use a dedicated OpenPGP implementation instead of this page.
4. Good fits and bad fits
Related tools: AES for symmetric-only work, RSA for short RSA-only messages, SHA-256 for hashing. If you arrived via "pgp encryption" looking for mail-grade OpenPGP, read this boundary first.
- Good: local demos of asymmetric crypto, temporarily protecting a config/token, teaching RSA+AES hybrid mode.
- Good: privacy-sensitive ops when you refuse to paste plaintext into random "encrypt online" sites.
- Bad: long-lived identity, revocation, multi-key rings, or talking to external PGP users.
- Bad: replacing HTTPS or server-side key management — transport and custody are separate layers.
5. Payload format and version
Ciphertext is site-local armored JSON (version, RSA-wrapped session key, IV, AES-GCM body) — not an OpenPGP Message. Decrypt elsewhere only with the PKCS#8 private key from this page and the full payload.
6. Checklist and sibling tools
- Back up the private key offline right after generation.
- Confirm the SPKI SHA-256 fingerprint out of band before encrypting.
- Use AES for symmetric-only work, RSA for short RSA-only messages, hash tools for integrity.
- For mail-grade OpenPGP interop, use a dedicated client — gpg will not decrypt this payload.
FAQ
No. Key generation, encryption, and decryption all run on your machine through the browser's Web Crypto API — the private key never touches a server. Browser extensions, corporate proxies, or shared computers can still snoop the clipboard, though, so do sensitive operations on a trusted device.
It is PGP-style hybrid encryption: RSA-OAEP (2048 or 4096 bits) wraps a random AES-256-GCM session key, mirroring OpenPGP's hybrid philosophy — but the armored payload is a site-defined JSON format, not an OpenPGP message.
Yes. The message body is encrypted with a random AES-256-GCM session key, and the RSA public key only wraps that 32-byte session key, so plaintext length is never bound by RSA's single-block limit. Bear in mind that losing the private key makes the ciphertext unrecoverable — back it up offline right after generation.
It is the SHA-256 of the public key's SPKI DER, shown in groups of four hex characters. Confirm it with your counterpart over a second channel (a phone call, say) before encrypting, to reduce the risk of a swapped fake key. Note that it is not an OpenPGP v4 fingerprint and will not match gpg --fingerprint output.
Not interoperably. Pasting a BEGIN PGP PUBLIC KEY BLOCK is rejected outright, and a PKCS#1 BEGIN RSA PRIVATE KEY cannot be imported either — Web Crypto expects PKCS#8 (BEGIN PRIVATE KEY). For mail-grade OpenPGP interop, use a dedicated client instead.
2048 is fine for demos and short-lived text protection, and it generates faster; choose 4096 when the key must live longer or your strength expectations are higher. The body is always protected by AES-256-GCM and RSA only wraps the session key, so the size mainly affects key-operation time and long-term strength expectations.
Related Tools
Related Articles
PGP Encryption Complete Guide: Protect Your Private Communications
Learn PGP / OpenPGP hybrid encryption, how to verify public-key fingerprints, and how a browser PGP-style tool differs from GnuPG mail interop.
The Complete Guide to PDF Tools: Merge, Split, Compress, and Convert — All in Your Browser
Everything you need to work with PDF files without uploading them: when to merge vs split, how PDF compression actually works, converting PDF to JPG and back, and why browser-local processing matters for contracts and ID documents.
Online CSV to SQL Tool: Import Tabular Data into Databases
CSV to INSERT with empty cells → NULL, MySQL backticks or PostgreSQL quotes, BOM stripping, Markdown pipe escaping, and when to switch to COPY/LOAD instead.