How to use
- Pick the key type. Use Ed25519 unless an old device or service does not accept it, in which case choose RSA.
- Enter a comment that will trail the public key. An email or
name@machineis common, and it can be left empty. - A new key pair is created when the page opens and each time you press Generate new key. The SHA256 fingerprint is shown with it.
- Paste the public key as a single line into the server’s
authorized_keysfile, or into the SSH key page of GitHub or GitLab. - Download the private key and save it as
id_ed25519(id_rsafor RSA) in your.sshfolder. On Linux and macOS runchmod 600on it so only you can read it, or ssh will refuse to use it.
Key types and sizes
| Type | Public key line starts with | Notes |
|---|---|---|
| Ed25519 | ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA… |
Short and fast. The public key Base64 is always 68 characters. |
| RSA 2048 | ssh-rsa AAAAB3NzaC1yc2EAAAADAQAB… |
The widest compatibility. The public exponent is 65537. |
| RSA 3072 | same | More margin than 2048, slightly slower to generate. |
| RSA 4096 | same | The largest. Logins may need a little more computation. |
Weak sizes such as RSA 1024 are not offered. Since OpenSSH 8.8 the SHA-1 based ssh-rsa signature scheme is off by default, but RSA keys themselves keep working through rsa-sha2-256 and rsa-sha2-512.
Two private key formats
- OpenSSH format (
-----BEGIN OPENSSH PRIVATE KEY-----): works directly withssh -i,ssh-addand most Git clients. Runningssh-keygen -y -fon a file made by this tool prints the same public key shown on screen. - PKCS#8 PEM (
-----BEGIN PRIVATE KEY-----): the standard format read by OpenSSL and programming libraries.
Both hold the same key. The fingerprint is computed from the public key only, so it matches the output of ssh-keygen -l -f yourkey.pub whichever private format you pick.
Keeping the key safe
- Anyone holding the private key can log in as you. Do not paste it into chat, email or an issue tracker.
- The downloaded private key has no passphrase. Add one with
ssh-keygen -p -f id_ed25519. - The public key is safe to share. If the private key is lost or may have leaked, delete the matching line from the server’s
authorized_keysand create a new key. - For a key guarding an important server, generating it yourself with
ssh-keygenon a machine you trust is the most certain route. This tool suits development keys and quick setups.
FAQ
Is the key sent to a server?
No. The key is generated on your device with the browser’s WebCrypto (crypto.subtle), and the public key encoding and fingerprint are computed in this page too. Nothing is transmitted or stored. The private key you see on screen does remain wherever you copy or download it, so handle it with care.
Ed25519 or RSA?
GitHub, GitLab and current OpenSSH servers all support Ed25519, so it is a fine default. If a very old device or an internal system rejects it, use RSA 3072 or larger.
Why can’t I set a passphrase here?
OpenSSH’s encrypted private key format relies on bcrypt-based key derivation, which browsers don’t provide as a standard API. Run ssh-keygen -p -f filename after downloading to add one.
What if it says Ed25519 generation is unavailable?
Ed25519 in WebCrypto is a relatively recent feature. Update the browser or choose RSA.
What is the fingerprint for?
Compare it with the SHA256:... value shown on first connection or in GitHub settings to confirm you are looking at the same key. To compute hashes yourself, try the Hash Generator.
Related tools
- For PEM keys used in certificates and signing, the RSA Key Generator makes PKCS#1 and PKCS#8.
- For an account password use the Password Generator.
- To inspect a Base64 string use the Base64 Encoder and Decoder, and for message signing see the HMAC Generator.
Generated keys are processed only in your browser and never sent to a server.