PuTTY on macOS: When to Use OpenSSH, Homebrew, or a GUI Client

Looking for PuTTY on your Mac? First decide what you need it to do. For a regular SSH login, macOS already includes OpenSSH. If you need PuTTY utilities or want to convert a Windows .ppk key, the PuTTY package is available through Homebrew. If you want saved sessions and a graphical interface, look for an SSH client built for macOS.

Those are three different use cases—and installing PuTTY tools does not give you the same native Mac app experience as PuTTY on Windows.

Connect with the SSH client already on your Mac

Open Terminal and connect with your server username and hostname or IP address:

ssh deploy@203.0.113.25

OpenSSH is already included with macOS, so there’s nothing extra to download for a basic terminal session. You can also use it with SSH keys and host configuration, but it does not provide PuTTY’s Windows-style saved-session window.

The PuTTY project does not provide an official native macOS application comparable to its Windows app. Be cautious when a site advertises a “PuTTY for Mac” download: a Windows .exe is not a Mac app, and a third-party package is not an official PuTTY .dmg.

Install PuTTY utilities with Homebrew

If you specifically need PuTTY command-line tools, install the package through Homebrew:

brew install putty

Package contents and build requirements can change, so inspect the current formula information before relying on a particular tool:

brew info putty

After installation, check whether the commands you need are available in your shell:

command -v puttygen
command -v plink

A returned path means the command is discoverable. No output means it is not available in that shell’s PATH.

This route is useful for PuTTY utilities, but don’t assume it installs a graphical app with the same interface and session management as PuTTY on Windows. Homebrew is a third-party packaging route. MacPorts may also offer a package; check its current port information and instructions for your macOS version if you use it.

Convert a .ppk key for OpenSSH

OpenSSH does not directly use PuTTY’s .ppk private-key format. If you have a PPK file and want to connect with the built-in ssh command, use PuTTYgen to convert it to an OpenSSH private key.

For example, after installing the PuTTY package:

puttygen ./server-key.ppk -O private-openssh -o ./server-key-openssh

PuTTYgen may ask for the PPK passphrase. Use a new output filename so you don’t overwrite another key. Then restrict access to the converted private key and use it for your connection:

chmod 600 ./server-key-openssh
ssh -i ./server-key-openssh deploy@203.0.113.25

Keep the private key in a secure location, never send it to anyone, and retain a protected backup of the original until you’ve confirmed the converted key works.

Choose a tool by the job

What you need	A practical option	Keep in mind
A standard remote shell	Terminal with OpenSSH	Connections are entered as commands, not managed in a PuTTY-style GUI.
PuTTY utilities or PPK conversion	PuTTY package through Homebrew	This provides tools, not a guaranteed native graphical PuTTY app.
Saved connections and a graphical workflow	A macOS-compatible SSH client	Check that it supports the features you need.
Remote file browsing	An SSH client with SFTP support	SFTP is a separate capability; confirm it is included.

When choosing a graphical client, verify current macOS support, compatibility with your Mac’s processor, and whether the edition includes the features you need. Don’t choose an app just because “PuTTY” appears in its name.

Download safely

For official PuTTY releases, use the PuTTY project’s download page and check which platform each file targets. For the Homebrew build, use the formula and install through Homebrew rather than an unfamiliar download mirror.

Avoid running an installer simply because its filename includes “PuTTY.” Check who publishes it, where it comes from, and whether it is intended for your Mac and macOS version. Package and platform details can change, so check the current information instead of assuming an older build will work.

The short version

• Just need SSH? Use ssh in Terminal.
• Need PuTTY tools or PPK conversion? Install the Homebrew package and check which commands are available.
• Want saved sessions or a graphical interface? Pick a client designed for macOS and confirm it has the features you want.

Treat these as separate choices: macOS OpenSSH is a command-line client, and the Homebrew PuTTY package is not an official native PuTTY GUI for Mac.

I originally published a more detailed version of this guide on the SSHFlow blog.

I'm also building SSHFlow — an SSH client where every server gets its own workspace for terminals, SFTP, code, and databases.