Generate an OpenPGP key pair locally in your browser: a public key to share and a private key to decrypt. Nothing is uploaded.
Running locally on your device ...
Choose options and generate the key pair
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
An OpenPGP key pair is made of two matching halves: a public key you can hand out freely, and a private key that stays secret. Anyone who wants to send you something encrypts it with your public key; only the holder of the matching private key can open the message afterwards. This asymmetry is exactly what makes PGP so useful, because you never have to exchange a shared password over an insecure channel.
This generator builds the pair directly in your browser. You choose between ECC on Curve25519 or NIST P-384 - modern, fast and with short keys - and classic RSA at 2048, 3072 or 4096 bits, which works with almost any older software. A name and an email form the user ID by which others recognise your key. If you also set a passphrase, the private key is stored encrypted with it, so it stays useless even in the wrong hands.
You get two files to download: the public key as .asc to distribute, and the private key as .asc to keep safe. Both are in the standard ASCII-armor format per OpenPGP RFC 9580 (backward-compatible with RFC 4880) and are therefore compatible with GnuPG, Kleopatra, Thunderbird or any other OpenPGP software - generated with the openpgp.js 6.3.1 library. Generation runs entirely locally using your browser cryptographic randomness source; no key is uploaded, stored or sent to a server.
| Input formats | No file (generator) |
|---|---|
| Output format | ASC |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: The private key is your secret - if it is lost, nothing that was encrypted to you can be decrypted anymore, and there is no recovery. Keep it safe and hand out only the public key. ECC keys are shorter and faster; some very old software understands only RSA.
| Type | Key size | Speed | Compatibility | Recommendation |
|---|---|---|---|---|
| ECC (Curve25519) | short | very fast | modern software | default choice when unsure |
| ECC (NIST P-384) | short-medium | very fast | modern + many government/enterprise systems | when NIST curves are required |
| RSA (2048-bit) | long | slower | very broad, even old software | minimum RSA size today |
| RSA (3072-bit) | longer | slower | very broad, even old software | solid middle ground |
| RSA (4096-bit) | longest | slowest | very broad, even old software | extra security margin |
No. Both keys are created entirely locally in your browser and are neither stored nor sent - that is the whole point.
ECC (Curve25519 or NIST P-384) is modern, very fast and has short keys. RSA (2048/3072/4096 bits) is older but broadly compatible with legacy software - 3072 bits is a solid middle ground. When unsure, pick ECC.
Only the public key. You keep the private key; with it you decrypt whatever is addressed to you.
Recommended yes: the passphrase encrypts the private key so it stays useless if stolen. Without one it is left unprotected.
Yes. They are in the standard OpenPGP format (ASCII armor) and can be imported into GnuPG, Kleopatra, Thunderbird and others.
Encrypt with PGP · Decrypt with PGP · Password generator · CSR Generator · View X.509 Certificate