Runs in your browser · nothing uploaded

RSA Keypair Generator — 2048/3072/4096 with PEM Export

Generate an RSA-OAEP keypair in your browser and export the public and private keys as PEM files. 2048, 3072, or 4096 bits. No upload, no server, free.

Loading tool…

More tools

All free, all private — everything runs in your browser.

Keys

AES Encryption Tool

Encrypt or decrypt with your own AES-128/256 key and IV in GCM or CBC mode. A raw, explicit bench for learning and development — runs entirely in your browser.

Keys

PBKDF2 Key Deriver

Derive a cryptographic key from a password with PBKDF2-HMAC-SHA256. Tunable iterations, random or custom salt, hex or base64 output. Runs in your browser.

Files

File Encryptor

Password-protect any file before you email or share it. AES-256-GCM with a PBKDF2-derived key, performed locally by your browser — no upload, no signup. Free.

FilesPro

Bulk File Encryptor

Batch-encrypt many files with a single password into one downloadable .sealbox archive, and restore them all at once. AES-256-GCM per file, performed locally — no upload. SealBox Pro.

Text

Text Encryptor

Turn any message into a shareable encrypted string and back. AES-256-GCM with PBKDF2 key derivation, performed locally by your browser. No upload, free.

TextPro

Encrypted Notes Vault

Keep private notes encrypted with a master password, stored only on your device. The master password derives an AES-256-GCM key and is never stored. 100% client-side. SealBox Pro.

How to use RSA Keypair Generator

  1. 1Choose a modulus size: 2048 (fast), 3072 (comfortable), or 4096 (conservative).
  2. 2Click Generate — the browser's Web Crypto API creates an RSA-OAEP keypair on your device.
  3. 3Copy or download the public key PEM (X.509 SPKI) and share it freely.
  4. 4Download the private key PEM (PKCS#8) and store it securely — anyone with it can decrypt your data.

RSA Keypair Generator FAQ

What do I get when I generate a keypair?
Two PEM files: the public key (X.509 SubjectPublicKeyInfo) and the private key (PKCS#8), both base64-encoded and wrapped in the standard BEGIN/END PEM headers. These formats work with OpenSSL, ssh-keygen conversions, and most crypto libraries.
Is it safe to generate keys here?
The keypair is generated by your browser's Web Crypto API using its own cryptographic random source, entirely on your device. Nothing is transmitted. Still, for high-value keys, prefer generating them on a machine you fully control with audited tooling — a compromised browser can compromise anything generated in it.
Which key size should I pick?
2048 bits is the general minimum and fastest; 3072 is a comfortable margin; 4096 is the conservative choice for long-lived keys. Bigger keys are slower to generate and use, with modest security gain.