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 will no longer display infinite user authentication banners if the server keeps sending them. If the server sends additional banners after the first, subsequent banners are discarded with a single log warning.
The SSH Client now enforces a maximum per-connection channel limit. Currently, the SSH Client limit is fixed at 1000 channels per connection.
sexec:
When stdout is redirected, the sexec command-line client now writes any errors and help text to stderr instead of stdout.
This should make errors easier to diagnose when sexec is used with Git, or with other applications which expect stdout to conform to an application protocol.
Dynamic port forwarding:
Hardened surfaces which could allow runaway memory use when the SSH Client is configured to act as a SOCKSv4 or HTTP CONNECT proxy. Implemented a timeout for the initial proxy request.
When using dynamic port forwarding (proxy forwarding) for server-to-client connections, bind addresses could be matched incorrectly. Fixed.
FTP-to-SFTP bridge:
The FTP bridge now requires that passive-mode data connections arrive from the same client IP address as the FTP control connection.
FTP control connection replies can now correctly contain UTF-8 characters, as advertised.
Double quotes are now escaped if they appear in quoted paths sent in FTP control connection replies.
CR and LF characters are now removed if they appear in file or directory names sent in directory listings.
Control connection commands containing NUL bytes are no longer accepted.
Graphical SFTP:
Disabled icons are now slightly less terrible on very old Windows versions.
