64-bit x86 PuTTY Packages
Who should use the 64-bit x86 builds
Independent resource: Putty.info is not the official PuTTY site and does not host binaries. Downloads open on the publisher’s hosts only.
If your Windows PC uses a normal Intel or AMD processor — virtually every laptop and desktop sold in the last decade — you want the 64-bit x86 packages. On the official download page this row is labeled “64-bit x86” and the installer filename looks like putty-64bit-<version>-installer.msi. The files live under a /w64/ path on the official download host.
The PuTTY project itself notes that the 32-bit packages exist mainly for backward compatibility with very old PCs or Windows versions. Do not choose 32-bit “just in case” on a modern machine.
Recommended: 64-bit x86 MSI installer
Start with the MSI unless you have a documented portable requirement. The installer ships the suite of tools documented in the PuTTY User Manual:
- putty.exe — SSH/Telnet client GUI
- pscp.exe — command-line SCP client
- psftp.exe — interactive SFTP client
- plink.exe — command-line backend for scripts and automation
- pageant.exe — SSH authentication agent
- puttygen.exe — key generation and conversion
After install, open PuTTY and use Help → About to confirm the version matches the stable release shown on our release center and on the official latest page.
Standalone 64-bit EXE alternatives
If policy blocks MSI installs, the official page lists per-architecture standalone binaries with the same names (putty.exe, pscp.exe, and so on). Filenames alone can look identical across architectures — the architecture is in the path (/w64/ versus /w32/ or Arm paths) and in the official page’s row label. Always pick the row that says 64-bit x86.
There is also a 64-bit x86 putty.zip that bundles the common tools. Mixing EXE files from different release versions is a common source of confusing bug reports; keep a set from one release together.
Verify the 64-bit package before you run it
- Confirm HTTPS and the official host before the file lands in Downloads.
- Download the adjacent
.gpgsignature for the MSI or EXE you chose. - Verify with the project’s published signing keys (see signatures).
- Optionally check the SHA-256 published in the official sums files (checksums).
Windows SmartScreen may warn on first run of niche tools; that is not a substitute for cryptographic verification, and a SmartScreen pass does not prove an unofficial mirror is safe.
Do not confuse x86_64 with Windows on Arm
“64-bit” is not enough by itself. Windows on Arm devices need the 64-bit Arm packages (putty-arm64-*-installer.msi), not the Intel/AMD x86_64 builds. If you are on a Snapdragon / Arm Windows laptop, read Windows Arm64 packages instead of this page.
After you install
Continue with how to use PuTTY, host key warnings, and the interactive troubleshooter if a first connection fails. For file copy, use the tools that came with the same MSI — see PSCP and PSFTP.