Encrypt Online
Theme

OpenPGP Message Encrypt & Decrypt

Encrypt text to recipient public keys or decrypt an armored message with a matching private key

Encrypt an OpenPGP message
How it works: The recipient shares a public key. The sender checks its fingerprint and encrypts. The recipient decrypts with the private key. Step-by-step guide
Protect a message for someone else with the public key they shared with you.
Paste complete public-key blocks. Compare each fingerprint with the recipient.
OpenPGP Message Encryption

OpenPGP encrypts a message to one or more recipient public keys. A matching private key is needed to decrypt it. This differs from the site's password-based AES workflow, where both people share one passphrase.

Encrypt or Decrypt a Message
  1. The recipient creates a key pair, protects the private key, and shares only the public key.
  2. The sender pastes the plaintext and recipient public key, then compares the displayed fingerprint through a trusted channel.
  3. The sender encrypts and shares the complete armored message.
  4. The recipient decrypts with the matching private key and its passphrase.
What This Workflow Does Not Verify

Reading a public key does not establish the owner's identity. Verify the complete fingerprint separately. This message form does not sign messages, verify signatures, discover recipients, contact keyservers, or use Web Key Directory lookups.

Reproducible Evidence

This tool has a versioned public record with three synthetic cases. Each expected result is recomputed from the production diagnostic core during the release check; the record also publishes fixture and source SHA-256 digests.

  • OPENPGP-RECIPIENT-READY-001valid
    One synthetic Curve25519 public key is readable and has an encryption-capable subkey.
  • OPENPGP-WRONG-BLOCK-TYPE-002mismatch
    An armored message block is pasted where a recipient public key is required.
    Expected code: INVALID_PUBLIC_KEY.
  • OPENPGP-ARMOR-TRUNCATED-003malformed
    A public-key armor header is present but the block is incomplete.
    Expected code: INVALID_PUBLIC_KEY.

Open the complete citation evidence record (JSON)

Implementation source-sha256:f1cadda9eb7ff218; verified 2026-08-05. Read the record's scope before citing a result; structural or cryptographic evidence is not automatically an identity or trust verdict.

FAQ
Where do I get an OpenPGP public key?

Ask the recipient to share their armored public key and full fingerprint. They can create a new pair with the OpenPGP Key Pair Generator or a managed tool such as GnuPG.

Can this page confirm that a public key belongs to someone?

No. Compare the key fingerprint with the recipient through a trusted channel before encrypting sensitive text.

Can I sign or verify messages here?

Not in this workflow. It is limited to encrypting and decrypting armored text messages.

What if I only have a passphrase?

Use the Encrypt Tool. OpenPGP recipient encryption requires a public key.