Our SSH client supports all desktop and server versions of Windows, 32-bit and 64-bit, from Windows XP SP3 and Windows Server 2003, up to the most recent – Windows 11 and Windows Server 2025.
Our client is free for use of all types, including in organizations.
Our SSH and SFTP client for Windows incorporates:
- One of the most advanced graphical SFTP clients.
- Single-click Remote Desktop forwarding.
- State-of-the-art terminal emulation with support for the bvterm, xterm, and vt100 protocols.
- Support for corporation-wide single sign-on using SSPI (GSSAPI) Kerberos 5 and NTLM user authentication, as well as Kerberos 5 host authentication.
- Support for ECDSA, RSA and DSA public key authentication with comprehensive user keypair management.
- Encryption and security: Provides state-of-the-art encryption and security suitable as part of a standards-compliant solution meeting the requirements of PCI, HIPAA, or FIPS 140-2 validation.
- SSH jump proxy: Connect to a final destination SSH or SFTP server by connecting through an SSH jump server. In the graphical SSH Client, this is configured in Proxy settings, on the Login tab.
- Obfuscated SSH with an optional keyword. When supported and enabled in both the client and server, obfuscation makes it more difficult for an observer to detect that the protocol being used is SSH. (Protocol; OpenSSH patches)
- Powerful SSH port forwarding capabilities, including dynamic forwarding through integrated SOCKS and HTTP CONNECT proxy.
- Powerful command-line parameters which make the SSH client highly customizable and suitable for use in specific situations and controlled environments.
- SFTP drive mapping: Access files on an SFTP server as if they were local, from any Windows application.
- An FTP-to-SFTP bridge allowing you to connect to an SFTP server using legacy FTP applications.
- An advanced, scriptable command-line SFTP client, sftpc.
- A scriptable command-line remote execution client, sexec, and a command-line terminal console client, stermc.
- A scriptable command-line tunneling client, stnlc, with support for static port forwarding rules, dynamic SOCKS-based tunneling, and FTP-to-SFTP bridge.
- Our .NET SSH library, FlowSshNet, with example PowerShell scripts showing how to use the SSH library for file transfer and remote program execution from PowerShell.
- Bitvise SSH Server remote administration features.
Bitvise software does not contain ads, install product bundles or collect user data for sale. We are 100% supported by users who license our software. Thank you!
The SSH Client is now less permissive with regard to NUL characters in protocol strings where NULs are not expected.
When making an outgoing connection via an HTTP CONNECT proxy, the SSH Client now limits the maximum size of received HTTP headers.
SSH:
The SSH Client now implements a configurable timeout for the duration of the initial SSH key exchange.
The Keep-alive / broken session detection feature now has a configurable initial timeout. Previously, it could be enabled or disabled, but the period could not be configured.
SFTP:
The SSH Client now implements more granular limits for the sizes of decoded SFTP strings.
The SSH Client now limits the maximum backlog of unfulfilled handle close operations.
Graphical client:
Restoring the SSH Client main window after it's hidden to the system tray should now work better if it was previously displayed on a second monitor that was unplugged.
Graphical terminal:
The window title and scroll bar for the SSH Client's graphical terminal window now support dark mode.
New Remote Desktop:
The RDP profile signing feature introduced in version 9.61 could cause Remote Desktop to exit abruptly on some systems. The implementation of this feature should now be more resilient.
sftpc:
The sftpc command-line client now supports Stat and RealPath commands.
A long-standing issue prevented auto-completion from working correctly when a switch parameter was passed before a path. Fixed.
stermc:
The stermc command-line client now supports a pass-through rendering mode for Windows Terminal. This substantially improves stermc usability with Windows Terminal.
Pass-through mode cannot be used with bvterm. Pass-through mode does not support printable session recording, but supports full session recording which includes escape sequences.