When comparing PuTTY vs WinSSHTerm, the Slant community recommends PuTTY for most people. In the question“What are the best terminal emulators for Windows?” PuTTY is ranked 9th while WinSSHTerm is ranked 15th. 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
WinSSHTerm is free for anyone to use.
Pro Keyboard shortcuts
Keyboard shortcuts are especially valuable for professionals.
Pro Supports X Server
There is easy, automatic integration with X Server and starts/stops can take place with the launch/exit of WinSSHTerm.
Pro Supports file transfer
The user can start a WinSCP session inside WinSSHTerm, without the need to duplicate the session in WinSCP.
Pro Highly portable
The user can run WinSSHTerm from a USB drive on different computers.
Pro Ready for production use
There are no annoying bugs in WinSSHTerm. Navigation tools and keyboard shortcuts are a great time saver, especially if you have to manage multiple connections.
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 Not a true terminal emulator
It's a PuTTY interface and it's mostly used to access remote machines through ssh, so it may not be very suitable for working on a local machine.