How To Install Putty on Debian 13

PuTTY is one of the most widely used SSH clients in the world, and for good reason. Whether you are connecting to a remote VPS, a bare-metal server, or a development machine, PuTTY gives you a clean graphical interface to manage SSH sessions, save connection profiles, and handle key-based authentication without wrestling with terminal flags every time.

If you want to know how to install PuTTY on Debian 13, this guide covers everything from installation to session configuration, SSH key setup, PSCP file transfers, and fixing the most common errors that trip people up. Debian 13 (codenamed Trixie) ships PuTTY 0.83.x in its default repositories, which means you do not need third-party sources, PPAs, or manual builds.

This tutorial is written from a sysadmin perspective and tested directly on Debian 13 Trixie. By the end of this guide, you will have a fully working Putty on Debian 13 setup, with SSH sessions saved, key authentication ready, and file transfers operational using PSCP.

What Is PuTTY and Why Use It on Debian 13?

Before running a single command, it helps to understand what you are actually installing and what it does on Linux.

PuTTY is a free, open-source terminal emulator and SSH client that supports SSH, Telnet, SCP, and SFTP protocols. It was originally built for Windows but has been ported to Linux and other Unix-based systems for years.

On Debian 13, PuTTY gives you a graphical alternative to the native ssh command. This matters most when you manage multiple servers with different credentials, ports, and key files. Instead of typing long SSH flags each time, PuTTY lets you save named sessions and connect with a double-click. It stores all session data and known host keys locally in ~/.putty/.

PuTTY vs OpenSSH on Debian 13

These two tools are not competitors. They serve different workflows.

OpenSSH handles scripted or automated tasks more cleanly. PuTTY wins when you need to switch between multiple saved sessions quickly or when onboarding teammates who are migrating from Windows.

Prerequisites

Make sure you have these in place before starting:

• Debian 13 (Trixie) installed on a physical machine, VM, or cloud instance
• A user account with sudo privileges (not the root account)
• An active internet connection to reach Debian’s package repositories
• Access to a terminal: press Ctrl + Alt + T on GNOME desktops or open your terminal emulator directly
• Optional but recommended: a remote Linux server or VM to test SSH connections

Step 1: Update Your Debian 13 System

Always update your package list before installing anything new. This ensures APT pulls the latest version of PuTTY and avoids dependency conflicts.

sudo apt update && sudo apt upgrade

What this does:

• apt update refreshes the list of available packages from all configured repositories
• apt upgrade upgrades any currently installed packages that have newer versions available

Expected output:

Get:1 http://deb.debian.org/debian trixie InRelease [172 kB]
Reading package lists... Done
Building dependency tree... Done

If you see errors about missing keys or unreachable repositories, check your /etc/apt/sources.list file and confirm your internet connection is active.

Step 2: Install PuTTY and PuTTY Tools via APT

Debian 13 includes PuTTY in its default repositories. No third-party PPA, Snap, or source compilation is required for this Linux server tutorial.

Install both the graphical client and the command-line tools in one command:

sudo apt install putty putty-tools

What each package installs:

• putty: the graphical SSH/Telnet client with the configuration window
• putty-tools: includes PSCP (secure file copy), PSFTP (interactive secure FTP), and PuTTYgen (SSH key generator)

When APT asks Do you want to continue? [Y/n] type y and press Enter.

Alternative APT Commands

Some administrators prefer apt-get or aptitude. All three package managers work equally well on Debian 13:

# Using apt-get
sudo apt-get install putty putty-tools

# Using aptitude (install it first if not present)
sudo apt install aptitude
sudo aptitude install putty putty-tools

The aptitude tool offers an interactive dependency resolver, which can be helpful in complex environments. For most users, plain apt is the right choice.

Step 3: Verify the PuTTY Installation on Debian 13

After installation completes, confirm PuTTY installed correctly. The most reliable way is to check the PSCP version, which works in both desktop and headless server environments:

pscp --version

Expected output on Debian 13:

pscp: Release 0.83
Build platform: 64-bit Unix
Compiler: gcc 14.2.0
Source commit: d2c178c49a0ae6fa9ef75ca84fb3c9d0d675ea85

You can also confirm the binary path with:

which putty

Expected output:

/usr/bin/putty

PuTTY Version Reference by Debian Release

All versions deliver the core SSH functionality covered in this guide.

Step 4: Install PuTTY on Debian 13 via Flatpak (Alternative Method)

If you want the latest upstream PuTTY release with sandboxed isolation, Flatpak is a solid alternative to the APT method.

When to Choose Flatpak Over APT

• Choose APT if you want a distro-tested, auto-updated version with full PSCP filesystem access
• Choose Flatpak if you want the newest Flathub build and do not mind sandbox restrictions for file transfers

Install Flatpak on Debian 13

sudo apt install flatpak

Add the Flathub Repository

sudo flatpak remote-add --system --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Install PuTTY from Flathub

sudo flatpak install --system flathub uk.org.greenend.chiark.sgtatham.putty

Verify and Launch the Flatpak Version

flatpak list | grep -i putty

Expected output:

PuTTY    uk.org.greenend.chiark.sgtatham.putty    0.83    stable    flathub

To run the Flatpak version:

flatpak run uk.org.greenend.chiark.sgtatham.putty

Note: PSCP file transfers work fully with the APT version. The Flatpak sandbox may restrict filesystem access required for PSCP to function correctly. Stick with the APT method if you plan to use PSCP regularly.

Step 5: How To Install PuTTY on Debian 13 and Launch It

Once installed, you have two ways to launch PuTTY on Debian 13.

From the terminal:

putty

From your desktop environment:

• GNOME: Press the Super key, type “PuTTY” in the Activities search bar, and click the PuTTY SSH Client icon
• KDE Plasma: Open the application launcher and search for “PuTTY”
• XFCE: Open the applications menu and find PuTTY under Internet or System

The PuTTY Configuration window opens immediately. The layout is identical to the Windows version, which makes migration seamless for teams switching from Windows-based workflows.

Step 6: Configure and Save SSH Sessions in PuTTY

This is where PuTTY earns its place on a Debian 13 system. Saved sessions eliminate the need to remember IPs, ports, and usernames for every server you manage.

Create a New SSH Session

1. Enter your remote server’s IP address or hostname in the Host Name field
2. Set the Port to 22 (the default SSH port)
3. Select SSH as the connection type under “Connection type”
4. Type a descriptive name in the Saved Sessions field (e.g., prod-web-01)
5. Click Save

Connect to a Saved Session

1. Select the session name from the Saved Sessions list
2. Click Load, then click Open
3. PuTTY connects and opens a live terminal window to the remote server

On the first connection, PuTTY displays the server’s host key fingerprint. Verify it matches your server’s fingerprint, then click Accept to store it in ~/.putty/sshhostkeys.

Step 7: Set Up SSH Key-Based Authentication in PuTTY

Password-based SSH is convenient but not the most secure option for servers you access regularly. Key-based authentication eliminates passwords entirely and is the standard in any serious configure PuTTY on Debian 13 workflow.

Generate an SSH Key Pair with PuTTYgen

PuTTYgen is included in putty-tools. Generate an Ed25519 key pair, which offers strong security with fast performance:

puttygen -t ed25519 -o ~/.ssh/putty-key.ppk

Enter a strong passphrase when prompted. This passphrase protects the private key file if it is ever stolen.

Export the Public Key

puttygen -L ~/.ssh/putty-key.ppk > ~/.ssh/putty-key.pub

Copy the Public Key to Your Remote Server

ssh-copy-id -i ~/.ssh/putty-key.pub user@your-remote-server-ip

This appends your public key to ~/.ssh/authorized_keys on the remote server automatically.

Configure PuTTY to Use Your Private Key

1. Launch PuTTY and load your saved session
2. Navigate to Connection > SSH > Auth > Credentials
3. In the “Private key file for authentication” field, click Browse
4. Select ~/.ssh/putty-key.ppk
5. Go back to Session, click Save to update the session config
6. Click Open to connect; PuTTY authenticates with the key and no password is required

Ed25519 keys require PuTTY 0.68 or later. Debian 13’s PuTTY 0.83 fully supports them.

Step 8: Transfer Files Using PSCP on Debian 13

PSCP (PuTTY Secure Copy Protocol) is the command-line file transfer tool included in putty-tools. It functions like the standard scp command but uses PuTTY’s SSH engine.

Upload a File to a Remote Server

pscp /path/to/local-file.txt user@remote-server:/path/to/destination/

Download a File from a Remote Server

pscp user@remote-server:/path/to/remote-file.txt ./local-destination/

Transfer a Full Directory Recursively

pscp -r /path/to/local-directory user@remote-server:/path/to/destination/

Specify a Custom Port or SSH Key

pscp -P 2222 -i ~/.ssh/putty-key.ppk /path/to/file.txt user@remote-server:/destination/

• -P 2222: specifies a non-default SSH port
• -i ~/.ssh/putty-key.ppk: uses your .ppk private key for authentication

Troubleshooting PuTTY on Debian 13

These are the most common errors encountered during a Putty on Debian 13 setup, with exact fixes you can run immediately.

Error 1: “Network error: Connection refused”

Cause: SSH is not running on the remote server, or a firewall is blocking port 22.

Diagnose:

sudo systemctl status ssh

Fix: Start SSH and allow it through UFW:

sudo systemctl enable --now ssh
sudo ufw allow ssh

Error 2: “Host Key Verification Warning”

Cause: This is normal on your first connection to a server. PuTTY has not stored the host key yet.

Fix: Verify the displayed fingerprint matches your server, then click Accept. If this warning appears on a server you have connected to before, the host key changed, which could indicate a server reinstall or a man-in-the-middle situation. Confirm with your server admin before accepting.

Error 3: “Permission Denied (publickey)”

Cause: Wrong SSH key file specified, or incorrect file permissions on the remote server’s .ssh directory.

Fix on the remote server:

chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

Fix in PuTTY: Confirm the correct .ppk file is set under Connection > SSH > Auth > Credentials.

Error 4: “putty: command not found”

Cause: Installation failed silently, or the binary is not in your PATH.

Fix:

sudo apt install --reinstall putty putty-tools
which putty

Error 5: PSCP Fails with “Fatal: Cannot open file”

Cause: The destination path on the remote server does not exist, or the user lacks write permissions.

Fix: Create the destination directory first:

ssh user@remote-server "mkdir -p /path/to/destination"

Then retry the PSCP transfer.

How to Remove PuTTY from Debian 13

If you need to uninstall PuTTY for any reason, the process is straightforward.

Remove the APT Installation

sudo apt remove putty putty-tools
sudo apt autoremove

Remove the Flatpak Installation

sudo flatpak uninstall uk.org.greenend.chiark.sgtatham.putty

Remove Saved Sessions and Preferences

PuTTY stores all session data and host keys in ~/.putty/. Back it up before deleting:

cp -r ~/.putty ~/putty-backup
rm -rf ~/.putty

Congratulations! You have successfully installed Putty. Thanks for using this tutorial for installing the Putty SSH and telnet client on Debian 13 “Trixie” system. For additional help or useful information, we recommend you check the official Putty website.