Skip to content

SSH Key Generator

Generate a key pair. Keep the private key. Share the public one.

Free · No signupGenerated in your browser

Generated on your device

Choose your key.

A key pair for your next server, Git host or project.

Key type

A label to identify the key. It does not change access.

Private keys are exported without a passphrase. You can add one locally after saving.

Two keys. One secure connection.

Generate a pair to get your public key, private key and SHA256 fingerprint here.

No account neededNo key uploads

Ready when you are. Key generation starts only when you choose Generate.

Prefer your terminal?

Generate a separate pair locally with the current settings:

ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519

From key pair to connected server

Keep your SSH workflow in CtrlOps.

Generate keys, connect to servers and manage access from one local desktop workspace.

Explore SSH key managementDownload for MacDownload for Windows

Put your keys to work

Generate. Save.
Connect.

Choose a key type and generate a pair

Ed25519 is the default for this generator. RSA is available for environments that require it, with a choice of 2048, 3072 or 4096 bits. Add an optional comment to help identify the key, then choose Generate key pair.

Save both files on your device

Download the public .pub file and the private key. On macOS or Linux, move them into ~/.ssh without overwriting existing files, set the directory to chmod 700 ~/.ssh and the private key to chmod 600 ~/.ssh/id_ed25519 (or id_rsa). Use the chmod calculator to understand the permissions.

Add a passphrase to the private key

Browser-generated keys here are unencrypted. Run ssh-keygen -p -f ~/.ssh/id_ed25519, using your actual saved filename, to add a passphrase locally. Your passphrase stays in your terminal; this page does not ask for it.

Install only the public key

On systems with ssh-copy-id, use ssh-copy-id -i ~/.ssh/id_ed25519.pub user@host. Alternatively, append the public line to that user’s ~/.ssh/authorized_keys on the server, or add it in your Git provider’s SSH key settings. The private key stays on your device.

Prefer generating locally?

The tool also builds a ssh-keygen command using your chosen settings. Run it locally to create a separate key pair and choose a passphrase during generation. The browser-generated pair and the terminal-generated pair will be different.

For an Ed25519 pair, run ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519. Choose a different filename if that key already exists.

Read the OpenSSH key generation reference

Before you connect

SSH keys,
explained.

Is it safe to generate SSH keys in the browser?

This tool generates keys entirely client-side using the Web Crypto API - the private key is never sent over the network, logged, or stored anywhere. You can verify that with your browser network tab open. For maximum assurance on production or long-lived keys, generating locally with ssh-keygen or CtrlOps is still the gold standard.

Should I use Ed25519 or RSA?

Use Ed25519 for new keys - it is fast, compact, and very secure, and is supported by all modern systems. Choose RSA (3072 or 4096 bits) only when you need to connect to an older server or tool that does not support Ed25519. Avoid DSA and 1024-bit RSA, which are considered weak.

How do I add my public key to a server?

The easiest way is ssh-copy-id user@host, which appends your public key to ~/.ssh/authorized_keys on the server. You can also paste the public key into that file manually. Only ever copy the public key (the .pub file) to servers - never the private key.

What file permissions do SSH keys need?

Your private key should be chmod 600 (readable only by you), the ~/.ssh directory should be chmod 700, and the public key can be chmod 644. SSH will refuse to use a private key that other users can read. See our chmod calculator for the details.

How do I add a passphrase to a generated key?

Keys from this tool are generated without a passphrase. Add one locally with ssh-keygen -p -f ~/.ssh/id_ed25519 - it encrypts the private key at rest so a stolen key file is useless without the passphrase. An SSH agent can cache it so you only type it once per session.

Where are SSH keys stored?

By convention, in the ~/.ssh directory in your home folder. The default names are id_ed25519 and id_ed25519.pub for Ed25519, or id_rsa and id_rsa.pub for RSA. Create the ~/.ssh directory with chmod 700 if it does not already exist.

Keep exploring

Tools and guides for your next step.

Your privacy preferences. We use product analytics to improve CtrlOps. Google measurement runs without analytics cookies. Live chat stays off until you allow it. Cookie policy