When comparing PuTTY vs WinSCP, the Slant community recommends PuTTY for most people. In the question“What are the best SSH clients for Windows?” PuTTY is ranked 1st while WinSCP is ranked 16th. The most important reason people chose PuTTY is:
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the [15 Essential Open Source Tools for Windows Admins list by InfoWorld](https://www.infoworld.com/article/2854954/microsoft-windows/15-essential-open-source-tools-for-windows-admins.html).
Ranked in these QuestionsQuestion Ranking
Pro De facto standard client for SSH, Telnet and Rlogin
PuTTY is one of the oldest and most popular clients. It has earned the trust of a great number of users over a long period by being reliable, offering useful features and helpful support. It got into the 15 Essential Open Source Tools for Windows Admins list by InfoWorld.
Pro Source code available
Full source available. Compile and modify it yourself.
Pro Lightweight and portable
Pro Not bundled with Potentially Unwanted Programs (PUP)
Does not attempt to install unwanted software on installation.
Pro Supports FTP and SFTP
In new versions also supports WebDav.
Pro Can protect stored passwords by strong AES cipher
Pro Free and open-source
It has very good compatibility with the other tools of this segment (e.g. PuTTY).
No Installation required.
Pro Can be automated with batch scripts
put a line in bat file ""D:\Program Files\WinSCP\winscp.com" /console /script="D:\ftp\scripts\transfer.txt". All the info can be found on their site.
Pro Integrated basic text editor
It has a integrated basic function text editor to create/edit/update files directly from client.
Con Lacks features
It is JUST an SSH client. There are many other options with built in X-servers, Multitabbing, etc.
Con Can not save passwords
Anyway, you can use "PuTTYgen" to generate a key pair, then use "Pageant" to do a password-less SSH remote login.
Con Ugly design, too simple
Con Tedious logging/tracing
Its tedious to set up logging and tracing (e.g. for serial connections).
Con No global settings
If you want to change a setting for all your connections, you'd have to do it individually.
Con No login scripting
Con Weird keyboard selection handling
If you are accustomed to several commanders, the selection method in WinSCP behaves unexpected - most often selects too much.
Con Keyboard shortcuts not editable
Con Does not support UNC
Does not support UNC. This makes working with the "Library"-function in Win 7, 8, 10 not possible when working over a network.