b2KIT

PGP / GPG Key Pair Generator

Generate OpenPGP key pairs (RSA or ECC) with user ID, expiration, and passphrase protection. Export as ASCII-armored text.

Tested tool guide Tested browser tools Checked August 16, 2026

What PGP / GPG Key Pair Generator does and how it behaves

Choose RSA or ECC, enter an OpenPGP user ID, set an expiration, and supply a passphrase for private-key protection. The tool produces the public and private portions of a new key pair as ASCII-armored text for use with compatible OpenPGP software. Key creation and export stay in the browser, which matters because the private portion must remain secret. A common surprise is that the user ID accompanies the public key, so a name or email entered there can be visible to everyone who receives it.

How the result is produced

1

Key construction

After RSA or ECC is chosen, the generator creates matching OpenPGP public and private key material, then binds the entered user ID to the key. The expiration choice is recorded as OpenPGP key metadata rather than as a timer that destroys stored key data. Repeating the same entries creates a different key pair because each generation uses new random key material.

2

Protection and export

The passphrase protects the exported private-key material. It is not part of the public key and is not needed by people who encrypt to you or verify your signatures. The public and private portions are exported in ASCII armor, a text representation with labeled PGP block boundaries. Generation and export occur in the browser, so this tool does not upload the private key.

Good uses

  • Creating a personal encryption identity before publishing the public-key block on a profile or sending it directly to specific correspondents.
  • Generating a fresh signing key for a software project, package release, document archive, or other workflow that accepts OpenPGP signatures.
  • Making an expiring test key for checking key import, encryption, decryption, signing, and verification in GPG or another compatible OpenPGP application.

Limits and checks

  • ASCII armor is an encoding, not an additional security boundary. A block labeled as a private key remains sensitive even when its text resembles an ordinary encoded document.
  • Expiration does not delete the key or revoke it. Copies remain usable as key material, while OpenPGP applications decide how to treat the recorded expiration during operations.
  • RSA and ECC are algorithm families, not universal compatibility guarantees. Confirm that every application and device in the intended workflow supports the generated key type before adopting it.

Common questions

Can I recreate the same key from the same user ID and settings?

No. The user ID, expiration, algorithm choice, and passphrase are settings, not a reproducible seed. A second generation creates a different key pair, fingerprint, and armored output. Back up the original private-key block and remember its passphrase if identity continuity matters. Possessing only the public-key block cannot reconstruct the corresponding private key.

Should I send both armored blocks to someone who wants my key?

No. Share only the ASCII-armored public-key block. The private-key block permits decryption and signing once unlocked, so keep it under your control even when it has passphrase protection. Recipients import the public key into their OpenPGP software. Retain the private key for your own application and store a protected backup separately.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools