About the SSH Key Generator
SSH Key Generator creates an SSH key pair for logging in to servers, GitHub, GitLab and cloud machines without a password. Choose Ed25519 (recommended) or RSA, add an optional comment such as your email, and press Generate. You get the public key as the single line that servers expect (starting ssh-ed25519 or ssh-rsa), the private key in a file format that the ssh command reads, and the key's fingerprint. The keys are created in your browser with its secure random numbers, nothing is uploaded, and the Ed25519 private key uses the standard OpenSSH format.
Updated October 2026
How to use the SSH Key Generator
- 1Choose Ed25519, or RSA 2048 or 4096 if a system needs RSA.
- 2Type a comment such as your email address, or leave it empty.
- 3Press Generate SSH key pair.
- 4Save the private key to ~/.ssh and give it permission 600.
- 5Add the public key line to your server's authorized_keys or to your GitHub account.
Why use SSH keys
A key is much stronger than a password: it cannot be guessed, it is never sent over the network, and you can remove one key without changing the others. Developers use SSH keys for servers, for pushing code to GitHub and for automated deployments.
Setting up in four steps
Create the pair, put the private key where your SSH client looks for it and protect it, then register the public key where you want to log in.
- Save the private key as ~/.ssh/id_ed25519
- chmod 600 ~/.ssh/id_ed25519
- Add the public line to authorized_keys or your Git host
- Test with ssh -T [email protected] or ssh user@server
Safe habits
Never share the private key or paste it into chat. Use one key per computer, add a passphrase and remove keys you no longer use. If a laptop is lost, delete its public key from your servers and accounts.
Related tools
For PEM keys use the RSA Key Generator, for passwords the Password Generator and for checking file fingerprints the Hash Generator. The Chmod Calculator explains permission 600.
Features
- Ed25519 in the OpenSSH private key format
- RSA 2048 and 4096
- One-line public key ready to paste
- SHA-256 fingerprint
- Copy and save buttons
- Tested against ssh-keygen
Frequently asked questions
What is an SSH key?
A pair of files that prove who you are to a server. The public key is placed on the server, and the private key stays with you. The server checks that you hold the private key without you sending a password.
Ed25519 or RSA?
Ed25519 is modern, small, fast and secure, and is the best default. Use RSA only for old systems that do not support Ed25519, and then 4096 bits is safer than 2048.
Where do I put the keys?
Save the private key as ~/.ssh/id_ed25519 (or id_rsa), run chmod 600 on it, and add the public key line to ~/.ssh/authorized_keys on the server or to GitHub's SSH settings.
Does the key have a passphrase?
No. Add one with ssh-keygen -p -f ~/.ssh/id_ed25519. A passphrase protects the key if the file is stolen.
Is it safe to make keys in a browser?
The keys come from the browser's secure random generator and are not sent anywhere. For high-value systems, make the key on your own computer with ssh-keygen.
What is the comment?
A label at the end of the public key, such as your email, so you can tell keys apart in authorized_keys. It does not affect the cryptography.
What is the fingerprint?
A short hash of the public key. Servers and GitHub show it so you can check that you added the right key.
Does the page keep the keys?
No. They exist only on screen until you leave the page.