When comparing KiTTY vs WinSSHTerm, the Slant community recommends KiTTY for most people. In the question“What are the best terminal emulators for Windows?” KiTTY is ranked 8th while WinSSHTerm is ranked 17th. The most important reason people chose KiTTY is:
- Sessions filter - Shortcuts for pre-defined command - The session launcher - Automatic logon script - URL hyperlinks - Running a locally saved script on a remote session - Send to tray - Transparency - Quick start of a duplicate session - SSH Handler: Internet Explorer integration - pscp.exe and WinSCP integration - New command-line options
Ranked in these QuestionsQuestion Ranking
Pro Includes additional features over PuTTy
- Sessions filter
- Shortcuts for pre-defined command
- The session launcher
- Automatic logon script
- URL hyperlinks
- Running a locally saved script on a remote session
- Send to tray
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
Pro Startup sessions
Support start-up sessions which allow you to specify the window/tab layout, working directories, and programs to run on startup.
Pro Can store login credentials
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Uses Unicode for the best character compatibility.
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 No centralized configuration
Each session holds its own configuration of all features. This means that if one wants to change a configuration common to all sessions (say, the terminal font), it has to be changed in each stored session separately.
A better solution would be to have a default configuration and store only the changed elements for each session (both configurations would be merged, with e priority on the specific one).
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.