Skip to main content

Encryption and key tools

These tools use the Web Crypto API: AES-256-GCM for symmetric encryption, PBKDF2 for turning a passphrase into a key, and RSA for the asymmetric cases. Keys are generated in the tab and are never sent anywhere, which also means nobody can recover them for you.

Pick the tool by the input you already have. A passphrase and a file belong in the encrypt tool; a key pair you intend to keep belongs in the RSA generator; a certificate someone sent you belongs in the decoder, which reads public data only.

Pick the tool by the job

What you are doingToolIn → out
Encrypt text or a file with a passphraseAES-256-GCM Encryptortext or file → AES-256-GCM ciphertext + salt/IV
Generate a key pair you keepRSA Key Pair Generator2048/4096 bits → PEM public + private key
Read a certificate you were sentCertificate Decoder: Inspect X.509 Certificates LocallyPEM/DER → subject, issuer, validity, SANs

How to choose

  • If both sides can share a passphrase, AES-256-GCM is the shortest path — no key exchange to design.
  • RSA is for key transport and signatures, not for encrypting a large file directly.
  • A certificate decoder reads public fields only; it cannot recover a private key, and it does not validate the chain.
  • Losing the passphrase means losing the data. There is no reset path on a client-side tool.

Guides that explain the trade-offs

All 3 tools in this group run in the browser tab. See the full tool index or start from the home page.