Encrypt messages with a PGP public key and decrypt with the private key. Supports ASCII-armored input and output.
PGP (Pretty Good Privacy) encrypts a message so only the holder of the matching private key can read it. Paste the recipient's public key and your plaintext, and the tool returns an ASCII-armored PGP message: base64 text wrapped in -----BEGIN PGP MESSAGE----- and -----END PGP MESSAGE----- markers, safe to send by email, chat, or a bug tracker. To decrypt, paste an armored message and the matching private key, supplying the passphrase if the key is protected. Everything runs in the browser; keys and plaintext are never uploaded. The most common failure: encrypting to the wrong public key, then discovering the message can only be opened by someone else.
Encryption is hybrid. A fresh random session key is generated for the message, the plaintext is encrypted with that symmetric key, and the session key itself is then wrapped with the recipient's public key using its RSA or ECC algorithm. The binary packet is base64-encoded and framed in ASCII armor with begin/end markers and the format's closing CRC24 checksum line, so the result survives copy-paste through email and chat.
Decryption reverses the process. The armored block is parsed back to binary packets, the session key is unwrapped using the private key, and the message body is decrypted with it. If the private key is passphrase-protected, the passphrase is required. A key that does not match the public key used at encryption, a wrong passphrase, or a truncated armor block all end the same way: no plaintext.
Almost certainly you encrypted with the wrong public key, most commonly your own. A message can only be decrypted with the private key that matches the public key used at encryption time; if you encrypted to someone else's key, only they can open it. To test your setup, encrypt to your own public key, then decrypt with your own private key.
The page runs entirely in the browser: the key and the message are processed locally and never uploaded to a server. Pasting a private key into any web page still carries risk: clipboard history and browser history can retain it, and a compromised browser could read it. If a pasted key may have been exposed, treat it as compromised: stop using it and create a new keypair.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.