DevOps
How to Use a PPK File in PuTTY
A practical Windows guide to using a PPK file in PuTTY for SSH access, including session setup, host configuration, and common connection mistakes.
What a PPK File Is
A PPK file is PuTTY’s private key format. If you are connecting to a Linux server or AWS EC2 instance from Windows using PuTTY, this is the file format PuTTY expects for key-based SSH access.
Many hosting providers and cloud platforms give you a PEM file first. If you use PuTTY, you often convert that PEM file into a PPK file with PuTTYgen before trying to connect.
What You Need Before Connecting
Before using a PPK file in PuTTY, make sure you have the target server IP or hostname, the correct SSH username, and the private key file already converted into PPK format. You also need PuTTY installed on your Windows machine.
For AWS EC2, the username depends on the image you launched. Common examples include ubuntu, ec2-user, admin, and root, depending on the server setup.
- PuTTY installed
- A valid `.ppk` private key file
- Server IP address or public DNS
- Correct SSH username
- Port 22 open in the server firewall or security group
How to Load the PPK File in PuTTY
Open PuTTY and enter the server IP or hostname in the Host Name field. Leave the port as 22 unless your server uses a custom SSH port. Then, in the left sidebar, expand Connection, expand SSH, and click Auth.
In the Auth section, look for the private key file field and browse to your PPK file. Select it, then go back to the Session tab. At that point, you are ready to connect or save the session for later use.
- Open PuTTY
- Enter server IP or hostname
- Go to Connection > SSH > Auth
- Browse to your `.ppk` file
- Return to Session and click Open
How to Save the Session
If you will connect regularly, save the session so you do not have to re-enter the server host and key file path every time. In the Session section, enter a name under Saved Sessions and click Save.
This is especially helpful if you manage multiple servers from Windows and want each one to keep its own key association and host settings.
What Happens on First Connection
The first time you connect, PuTTY may show a server host key warning. This is normal when the host has not been seen before on your machine. Verify that the server is the one you expect, then accept the key and continue.
After that, PuTTY will open the terminal session and prompt you for the username if it was not already supplied in the session settings.
Common Errors and Fixes
Most PuTTY SSH problems are caused by the wrong username, a server firewall issue, or the wrong private key. If PuTTY says access denied or authentication failed, double-check that the PPK file matches the server and that you are using the correct login user.
If PuTTY times out, confirm that the server is running, reachable publicly, and allowing inbound SSH on port 22 or your custom port.
- Authentication failed: wrong key or wrong username
- Connection timed out: port 22 blocked or server unreachable
- Network error: hostname not found: wrong IP or DNS
- Server refused our key: the matching public key is not authorized on the server
Related SSH and Key Guides
If you still have a PEM file instead of a PPK, start with the PEM-to-PPK conversion guide first. If you are using AWS EC2 from Windows, the EC2 SSH tutorial is the best companion article because it explains usernames, security groups, and host details in context.
- Related article: /blog/convert-pem-to-ppk
- Related article: /blog/how-to-ssh-into-aws-ec2-from-windows
- Related article: /blog/how-to-convert-ppk-to-pem
- Blog hub: /blog
FAQ
What is a PPK file used for?
A PPK file is PuTTY’s private key format and is used to authenticate SSH connections from PuTTY on Windows.
Can I use a PEM file directly in PuTTY?
Usually no. PuTTY typically expects a PPK file, so you often need to convert PEM to PPK first using PuTTYgen.
Where do I load the PPK file in PuTTY?
In PuTTY, go to Connection, then SSH, then Auth, and browse to the PPK file in the private key field.
Why does PuTTY say authentication failed?
The most common causes are the wrong SSH username, the wrong private key, or the matching public key not being authorized on the server.
Can I save the PPK configuration in PuTTY?
Yes. You can save the host and key settings as a named session from the Session tab.
Related free tools
If you want to turn this topic into action, use one of ShortIQ's free tools for campaign planning, UTM structure, or QR distribution.
Continue Reading
Explore more guides on link shortener SaaS strategy, Bitly alternatives, and white label link management.
Was this article helpful?
Tell us if this guide solved the problem or what was still missing. We use this to improve the blog and only follow up if you explicitly allow it.