About this tool
Ed25519 is a modern digital-signature algorithm (EdDSA on Curve25519). Its keys are tiny, 32 bytes each, signing and verification are fast, and it avoids many of the implementation pitfalls of older algorithms. It’s the default for new SSH keys and is used by Signal, WireGuard, Tor, Git commit signing, JWTs (alg: EdDSA) and many APIs that sign webhooks.
Keys are generated by your browser’s Web Crypto API and never leave this page: nothing is uploaded, logged or stored. For production servers, generating keys on the machine that will use them (with openssl or ssh-keygen) is still best practice.
Formats
- PEM (PKCS#8 private, SPKI public): for OpenSSL, Node.js, Go, Java and most libraries.
- JWK: for JOSE and JWT libraries and JWKS endpoints (
"kty": "OKP", "crv": "Ed25519"). - Raw: the 32-byte private seed and public key, as used by libsodium, NaCl and many blockchain tools.
Ed25519 vs RSA and ECDSA
| Ed25519 | RSA 3072 | ECDSA P-256 | |
|---|---|---|---|
| Public key size | 32 bytes | 384 bytes | 64 bytes |
| Signature size | 64 bytes | 384 bytes | 64 bytes |
| Security level | ~128 bit | ~128 bit | ~128 bit |
| Needs a random number per signature | No | No | Yes (a weak RNG leaks the key) |
Using the keys
# OpenSSL 3: sign and verify a file
openssl pkeyutl -sign -inkey ed25519-private.pem -rawin -in message.txt -out message.sig
openssl pkeyutl -verify -pubin -inkey ed25519-public.pem -rawin -in message.txt -sigfile message.sig
FAQ
What is Ed25519?
A fast, secure digital signature algorithm using the Edwards form of Curve25519. Keys are 32 bytes and signatures 64 bytes.
Can Ed25519 keys encrypt data?
No, Ed25519 is for signatures only. For encryption or key exchange, use X25519 (the related Diffie-Hellman function).
How do I use Ed25519 for JWTs?
Sign with alg “EdDSA” using the private key, and publish the public key as a JWK with kty “OKP” and crv “Ed25519”.
Which browsers support this?
Current versions of Chrome, Edge, Firefox and Safari support Ed25519 in the Web Crypto API.