OpenSSH to PPK Converter
Turn an OpenSSH or .pem private key into a .ppk for PuTTY, Pageant and WinSCP, passphrase and all.
Free · No signupYour key never leaves this tab
Getting the converter ready…
- 1Add your private keyid_ed25519, id_rsa, or a .pem file such as an AWS key pair.
- 2Unlock it if it has a passphraseThe key is decrypted here, in this tab.
- 3Download the .ppkFor PuTTY, Pageant, WinSCP and FileZilla, with a passphrase if you like.
Prefer the command line?
- Convert with PuTTYgen
puttygen id_ed25519 -o key.ppk
PuTTYgen asks for the passphrase on your machine. On Windows, use Load, then Save private key.
Tired of converting keys?
An SSH client that reads your keys as they are.
CtrlOps uses standard OpenSSH keys directly: store them, assign them per server, and keep them encrypted on your own machine.
Keep it handy
What it reads,
and what it writes.
Find your key by its first line, then pick the .ppk version your PuTTY understands.
| Format | First line | Comes from |
|---|---|---|
| OpenSSH | BEGIN OPENSSH PRIVATE KEY | ssh-keygen, GitHub guides, most Linux and macOS setups |
| PEM (PKCS#1) | BEGIN RSA PRIVATE KEY | AWS EC2 key pairs, older ssh-keygen, OpenSSL |
| PEM (SEC1) | BEGIN EC PRIVATE KEY | OpenSSL, ssh-keygen -m PEM |
| PEM (PKCS#8) | BEGIN PRIVATE KEY or BEGIN ENCRYPTED PRIVATE KEY | OpenSSL 3, cloud consoles, Java tools |
| .ppk | Read by | Good to know |
|---|---|---|
| Version 3 | PuTTY 0.75 and later (2021), current WinSCP and FileZilla | Argon2 protects the passphrase. The default. |
| Version 2 | PuTTY 0.74 and earlier, and tools built on them | Only for software that rejects version 3. |
How the conversion works
Same key.
PuTTY’s container.
Why convert OpenSSH to .ppk?
PuTTY, Pageant and the tools built on them only load keys in PuTTY’s own .ppk format. Keys made with ssh-keygen on Linux or macOS, and the .pem files cloud providers hand out, use OpenSSH or PEM format instead. The key inside does not change, so the public key already on your servers keeps working.
Which keys convert
Ed25519, RSA and ECDSA (P-256, P-384 and P-521) keys convert from OpenSSH format, from PEM files such as AWS EC2 key pairs, and from PKCS#8. DSA converts with a warning, since most servers now refuse it. Keys on a hardware security key (the sk- types) cannot be converted, because the private part never leaves the device.
Passphrase-protected keys
Enter the passphrase and the key is decrypted in this tab, then the .ppk is protected again, with the same passphrase or a new one. Version 3 derives the encryption key with Argon2id, as PuTTYgen does, so the passphrase is hard to guess even if the file is copied. Keys encrypted with chacha20-poly1305 or 3DES are the exception; run ssh-keygen -p -Z aes256-ctr -f id_ed25519 first to switch them to AES.
Converting with PuTTYgen, offline
PuTTYgen does the same conversion on your own machine. In the Windows app, choose Load, pick the key (set the file type to All Files), then Save private key. On the command line, puttygen id_ed25519 -o key.ppk writes a version 3 file; add --ppk-param version=2 for older software.
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 lines of the .ppk stay hidden on screen until you choose to show them. For production or long-lived keys, the offline PuTTYgen command is the most cautious option.
Read PuTTY’s description of the .ppk formatOpenSSH & PPK FAQ
Keys for PuTTY,
explained.
Paste your OpenSSH private key (the -----BEGIN OPENSSH PRIVATE KEY----- kind) or choose the file, and download the generated key.ppk. Offline, run puttygen id_ed25519 -o key.ppk. PuTTY, Pageant, and WinSCP can then load the .ppk.
PuTTY and Pageant only load .ppk files, so convert your id_ed25519 to .ppk first (with this tool or PuTTYgen), then load the .ppk in PuTTY under Connection > SSH > Auth, or add it to Pageant. The matching public key stays on the server unchanged.
Yes. Paste it here: PEM keys in PKCS#1, SEC1 and PKCS#8 form convert in the browser, including AWS EC2 .pem files and passphrase-protected PEM keys. Offline, puttygen key.pem -o key.ppk does the same.
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, converting offline with PuTTYgen is safest; the tool shows you that command.
It does. Enter the passphrase when the tool asks: the key is decrypted in your browser, and the .ppk keeps a passphrase by default, the same one or a new one. Only keys encrypted with chacha20-poly1305 or 3DES need re-encrypting first, with ssh-keygen -p -Z aes256-ctr -f id_ed25519.
They store the same key in different containers. OpenSSH format (id_ed25519, id_rsa) is the standard used by ssh and most tools; PuTTY .ppk is Windows-specific and includes a built-in integrity MAC. Converting just repackages the key - it does not change or weaken it.
Keep working
Tools and guides for your next step.