PPK to OpenSSH Key Converter
Turn a PuTTY .ppk key into an OpenSSH key for ssh, scp and Git, passphrase and all.
Free · No signupYour key never leaves this tab
Getting the converter ready…
- 1Add your .ppkPaste it, drop the file, or choose it. PuTTYgen saves keys as .ppk.
- 2Unlock it if it has a passphraseThe fingerprint shows first, so you can check it is the right key.
- 3Save the OpenSSH keyDownload id_ed25519 and its .pub, with a passphrase if you like.
Prefer the command line?
- Private key
puttygen key.ppk -O private-openssh-new -o id_ed25519 - Public key
puttygen key.ppk -O public-openssh -o id_ed25519.pub
PuTTYgen asks for the passphrase on your machine. On Windows, use Conversions › Export OpenSSH key.
Leaving PuTTY behind?
A modern SSH client, no key juggling.
CtrlOps uses standard OpenSSH keys and manages them for you: store them, assign them per server, and keep them encrypted on your own machine.
Keep it handy
Key formats,
at a glance.
The same key can live in several containers. Here is which tools read which, and what converts.
| Format | Used by | Typical file |
|---|---|---|
.ppk | PuTTY, Pageant, PuTTYgen, WinSCP, FileZilla | mykey.ppk |
OpenSSH | ssh, ssh-keygen, scp, sftp, Git, VS Code | id_ed25519 / id_rsa |
PEM | OpenSSL, older OpenSSH, some cloud consoles | id_rsa (BEGIN RSA PRIVATE KEY) |
SSH2 public key | PuTTYgen’s Save public key (RFC 4716) | key.pub (BEGIN SSH2 PUBLIC KEY) |
| Key type | To OpenSSH | Good to know |
|---|---|---|
| Ed25519 | Converts | The best choice for new keys. |
| RSA | Converts | Use 2048 bits or more; many servers refuse less. |
| ECDSA P-256, P-384, P-521 | Converts | Supported by every current OpenSSH. |
| DSA | Converts, with a warning | OpenSSH 10.0 removed DSA, so most servers refuse it. |
| Ed448 | Cannot convert | OpenSSH has no Ed448 support at all. |
How the conversion works
Same key.
Different container.
Why .ppk and OpenSSH differ
PuTTY on Windows stores keys in its own .ppk format, which bundles the public key, the private key, a comment and an integrity check (a MAC) in one text file. Everything else, including ssh, scp, Git and CI systems, uses the OpenSSH format. The key itself is identical in both; only the packaging differs, so converting does not change or weaken it.
Passphrase-protected keys
Most .ppk files have a passphrase. Enter it and the key is decrypted in this tab: PPK version 3 derives the key with Argon2, version 2 with SHA-1, and the file’s MAC is checked so a wrong passphrase or an edited file is caught instead of producing a broken key. The OpenSSH key keeps a passphrase by default, encrypted with bcrypt and AES-256 exactly as ssh-keygen does, so converting never leaves an unprotected copy unless you choose one.
Converting with PuTTYgen, offline
The fully offline route is PuTTYgen. In the Windows app, choose Load, pick the .ppk, then Conversions › Export OpenSSH key. On the command line, puttygen key.ppk -O private-openssh-new -o id_ed25519 writes the private key and puttygen key.ppk -O public-openssh -o id_ed25519.pub the public one. The converter shows both commands with your file name.
Save the key and set permissions
Put the key in ~/.ssh/ and lock it down with chmod 600 ~/.ssh/id_ed25519 and chmod 700 ~/.ssh; ssh refuses a private key that other users can read. The chmod calculator explains the numbers, and the SSH config generator ties the key to a host so you can connect with a short name.
Is it safe to convert a key online?
The conversion runs entirely in your browser, with no network requests; you can watch the network tab while converting. Nothing is stored, and the private key stays hidden on screen until you choose to show it. Still, a private key is sensitive: for production or long-lived keys, the offline PuTTYgen command is the most cautious option.
Read PuTTY’s description of the .ppk formatPPK & OpenSSH FAQ
PuTTY keys,
explained.
Paste or upload the .ppk on this page and copy the OpenSSH private and public keys. Offline, run puttygen key.ppk -O private-openssh -o id_ed25519. Note that modern OpenSSH format is what ssh expects; classic PEM is only needed for older tools.
No - the OpenSSH ssh client does not read .ppk files. Convert the .ppk to an OpenSSH private key first (with this tool or puttygen), save it in ~/.ssh, chmod 600 it, and then ssh -i can use it.
Use the OpenSSH to PPK converter, which runs in your browser too, or run puttygen id_ed25519 -o key.ppk. The .ppk can then be loaded by PuTTY or Pageant.
This tool does the conversion entirely in your browser and never uploads your key - you can verify there are no network requests. For production keys, the safest option is still to convert offline with PuTTYgen; the tool shows you that exact command.
It does. Enter the passphrase when the tool asks: the key is decrypted in your browser and checked against the file’s MAC, so a wrong passphrase is caught, and the OpenSSH key keeps a passphrase by default. Offline, puttygen key.ppk -O private-openssh-new -o id_ed25519 asks for it locally.
They store the same key material in different containers. .ppk is PuTTY-specific and includes a built-in integrity MAC; OpenSSH format (id_ed25519, id_rsa) is the standard used by ssh and almost everything else. Converting just repackages the key - it does not change or weaken it.
Keep working
Tools and guides for your next step.