Free SSH Key Pair Generator

The SSH Key Pair Generator is a free online tool that generate rsa ssh key pairs (2048 or 4096-bit) in your browser using the web crypto api. produces a private key (pem format), public key (openssh authorized_keys format), and sha-256 fingerprint.. It runs entirely in your browser with no installation or sign-up needed.

Yes — keys are generated using SubtleCrypto (Web Crypto API) in your browser. Nothing is sent to any server. Your private key never leaves your device.

The public key is in OpenSSH authorized_keys format (ssh-rsa AAAA... comment), compatible with GitHub, GitLab, server ~/.ssh/authorized_keys, and ssh-copy-id.

The private key is exported in PKCS#8 DER format wrapped in a PEM block (RSA PRIVATE KEY header), compatible with standard SSH clients.

Yes, completely free.

Absolutely. The SSH Key Pair Generator processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the SSH Key Pair Generator is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the SSH Key Pair Generator in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The SSH Key Pair Generator works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

For most situations, choose 4096-bit. The larger RSA modulus gives a wider security margin and is what current guidance recommends for long-lived keys you'll keep for years, such as your main GitHub or server login key. A 2048-bit key is the practical minimum still considered safe today; it generates a little faster and is perfectly fine for shorter-lived or lower-risk keys, like a throwaway key for a test server you'll delete next week. The trade-off is small: 4096-bit keys take marginally longer to create and authenticate but are otherwise indistinguishable in daily use. There is no benefit to going below 2048 bits, which is now considered weak. This generator offers both sizes from a dropdown, defaulting to 4096-bit — pick your size, click generate, and the key pair appears instantly.

The comment is an optional label appended to the end of the public key line, producing output like "ssh-rsa AAAA... user@hostname". It has zero effect on the cryptography — the key works identically with or without it. Its only job is human identification: when several public keys are stacked in one server's authorized_keys file, the comment tells you at a glance which key belongs to which person or machine, so you can revoke the right one later. Common conventions are user@hostname or your email address, but any short text works. If you leave the field blank, the tool simply omits it and the key is still completely valid. Add a comment in the optional field before generating to make your key easy to recognize, or skip it for a bare key.

The fingerprint is a short SHA-256 digest of the public key, shown as a string like "SHA256:abc123...". Because any change to the key produces a completely different fingerprint, it acts as a compact, human-comparable summary of the full key. You use it to confirm two parties are looking at the same key without reading out hundreds of characters: read the fingerprint aloud over the phone, compare it to what a server reports, or check it against the value GitHub displays for an added key. SSH itself shows fingerprints when you first connect to a host so you can catch tampering. The fingerprint is safe to share publicly — it cannot be reversed back into the key. This tool computes the SHA-256 fingerprint automatically and gives you a one-click copy button beside it.

Use only the public key — never paste the private key into a website. After generating, click Copy on the Public Key card to grab the full "ssh-rsa AAAA..." line. On GitHub, go to Settings, then SSH and GPG keys, click New SSH key, paste the line into the Key box, give it a title, and save. GitLab and Bitbucket follow the same pattern under their SSH Keys settings. Then test the connection from your terminal with "ssh -T git@github.com". Keep the matching private key safe on your own machine at ~/.ssh/id_rsa with permissions locked to chmod 600, since it is the secret half that proves your identity. The output produced here is in standard OpenSSH authorized_keys format, so it pastes directly into any of these services without conversion. Generate your pair and copy just the public line to get connected.

RSA and Ed25519 are two different algorithms for SSH key pairs. RSA is the long-established, universally compatible choice and works with essentially every SSH server and Git host, which is why a 4096-bit RSA key remains a safe, widely accepted default. Ed25519 is a newer elliptic-curve algorithm that produces much shorter keys with comparable or better security and slightly faster operations, but it requires reasonably modern OpenSSH and isn't accepted by some older systems. If you need maximum compatibility or are working with legacy servers, RSA is the dependable pick; if every system in your stack is current, Ed25519 is an excellent modern alternative. This tool generates RSA key pairs in 2048-bit or 4096-bit sizes using your browser's Web Crypto API — select a size and generate a fully OpenSSH-compatible pair in seconds.