When comparing WinSCP vs hyper, the Slant community recommends WinSCP for most people. In the question“What are the best SSH clients for Windows?” WinSCP is ranked 17th while hyper is ranked 22nd. The most important reason people chose WinSCP is:
In new versions also supports WebDav.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports FTP and SFTP
In new versions also supports WebDav.
Pro Free and open-source
It has very good compatibility with the other tools of this segment (e.g. PuTTY).
Pro Supports WebDAV
Pro Not bundled with Potentially Unwanted Programs (PUP)
Does not attempt to install unwanted software on installation.
Pro Supports PPK Keys
You can use the SSH server public/private key files from putty to log in.
Pro Supports Amazon S3
You can use in the last versions S3 so you're good if you use Amazon AWS.
Pro Portable
No Installation required.
Pro Integrated basic text editor
It has a integrated basic function text editor to create/edit/update files directly from client.
Pro Can protect stored passwords by strong AES cipher
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 Cross-platform due to electron browser-based foundation
Although not Windows-friendly. But nobody uses Windows terminal anyway.
Pro Built on electron, supports split panels and plugins
Cons
Con Keyboard shortcuts not editable
Con Slow
In my opinion, it's slower than Filezilla.
Con No x64 version
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.
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 Made with Electron
It uses a considerable amount of resources, compared to other offerings.
Con Not as cross platform as advertised
Most features only work on Mac OS.
Con Incorrect rendering
Terminal window has visual artifacts.
Con No configuration UI; all options must be set via JSON
Con Still maturing as of December 2016
Folks noticed some issues in the 1.0 release cited here.
Con Difficult to find information about it, because of the confusion with hyperterminal
