Download Bitvise SSH Client 
Current version: 8.49, size: 23.1 MB
The link is to Amazon CloudFront and should be very reliable. If it does not work, try alternative.
If the installer downloads but does not start, check below.
Our installers are cryptographically signed. Our most recent installers use an Extended Validation digital certificate from DigiCert. Here is how to verify. Do not run installers for Bitvise software that do not carry a valid digital signature by Bitvise.
Bitvise SSH Client is easy to uninstall.
Using Bitvise SSH Client requires you to read and agree with its License Terms.
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!
Upgrading from a previous version
To upgrade from a previous version, download the new installer, execute it, and follow the process. The installer will detect an existing installation and will automatically remove it before installing the new one. During this process, your settings will be preserved.
Help! The installer does not start?
Depending on your Windows version, security settings, and how the installer was downloaded, you may need to take an extra step to start it. On Windows Server 2016, right-click the installer executable in Windows Explorer, click Properties, and see if you need to check Unblock on the General tab.
Bitvise SSH Client: Free SSH file transfer, terminal and tunneling
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 2022.
Our client is free for use of all types, including in organizations. To begin, simply download it here.
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.
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.
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.
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!
Graphical SFTP File Transfers
Bitvise SSH Client incorporates one of the most advanced SFTP file transfer clients, supporting:
Bitvise SSH Client also incorporates an advanced, scriptable command-line SFTP client.
Bitvise SSH Client provides integrated access to the SSH server’s console, either via VT-100 and xterm protocols supported by most SSH servers on any platform, or via the enhanced bvterm protocol supported by Bitvise SSH Server:
Bitvise SSH Client also incorporates a command line terminal emulation client, stermc, as well as a command-line remote execution client (sexec).
Single sign-on
When using Bitvise SSH Client to connect to a GSSAPI-enabled SSH server in the same or a trusted Windows domain, you can let Kerberos 5 (or on older platforms, NTLM) perform the server as well as user authentication for you. No manual host key verification; no management of user passwords and public keys. Just tell the SSH client which server in the domain to connect to, and if that server is Bitvise SSH Server (WinSSHD) or another server with compatible support for GSSAPI, the two programs will authenticate and establish a secure connection automatically.
Port Forwarding
Bitvise SSH Client is a powerful SSH2 port forwarding client with many features, including:
Dynamic tunneling via integrated proxy supporting SOCKS4, SOCKS4A, SOCKS5 and HTTP CONNECT proxy tunneling protocols. Configure your applications to connect to target hosts through the SSH Client’s proxy, and no manual tunneling rules need be configured.
How to set up programs for dynamic tunneling: Firefox, IE; with these settings in Bitvise SSH Client.
Port forwarding settings can be saved to and loaded from a profile. One can maintain multiple complex tunneling configurations without having to manually enter parameters before each session.
Bitvise SSH Client minimizes its presence by displaying only a system tray icon when running in the background. If an error is encountered while the program is minimized, the icon reflects that.
Server-side forwarding: with Bitvise SSH Server and Client, a server and multiple clients can be set up so that all port forwarding rules are configured centrally at the server, without requiring any client-side setting updates. The SSH clients only need to be configured once, and port forwarding rules can easily be changed when necessary.
Command-line parameters are supported. Using command-line automation, a port forwarding session can be started from a link in the Startup menu without requiring any user interaction whatsoever. Help with the command-line parameters can be found in the SSH client log area when it is first started, or by executing ‘BvSsh /?’ from a command prompt.
After an SSH session is established, any external application can be launched automatically.
If an SSH session is interrupted, Bitvise SSH Client can automatically reconnect to the server.
Bitvise SSH Client also incorporates an advanced, scriptable command-line tunneling client.
Highly customizable
Additionally, when the graphical Bitvise SSH Client is running, you can use the command line utility BvSshCtrl to programmatically cause the client to log in, log out, or exit. Run ‘BvSshCtrl’ for help.
Portable use of Bitvise SSH Client
The latest versions of our SSH Client additionally support storing host key information and client authentication keypairs in an SSH Client profile. This means that you can copy the contents of the SSH Client installation directory to a USB key, insert the USB key into another computer, and run the graphical SSH Client as follows:
This will tell the Client to not use the Windows registry, and to connect exclusively using the host and keypair information you have saved into Profile.bscp.
For more information about the supported command line parameters, run the graphical SSH Client as follows:
Bitvise SSH Client further includes command line clients – sftpc, sexec, stermc, and stnlc – which also support the -noRegistry and -profile parameters. These command line clients are frequently used unattended, but can also be used interactively. For more information, check Using Bitvise SSH Client Unattended.
Command-Line SFTP Client
Bitvise SSH Client incorporates sftpc, an advanced command-line SFTP client which supports:
Command list: after installing Bitvise SSH Client, get this help by connecting to a server using sftpc, then execute «help» and «help «
The «log» utility can be used with sftpc to store the output of each individual SFTP session in a separate, uniquely named log file for auditing.
The «retry» utility can be used with sftpc to automatically repeat transfer attempts after specific types of failures.
Command-Line Remote Execution Client
Bitvise SSH Client incorporates sexec, a scriptable command-line remote execution client which can be used to securely execute programs on remote machines from a batch file. The batch file can perform actions based on the exit code reported from the remote program, and can capture the remote program’s output for processing by simple redirection of sexec output.
Another command-line program included with Bitvise SSH Client, stermc, conveniently opens an SSH terminal emulation session with xterm, VT-100 and bvterm support in the same Command Prompt window it is started from. If you SSH from computer A to computer B running Bitvise SSH Server, and you also have Bitvise SSH Client installed on computer B, you can use stermc to conveniently establish an onward SSH terminal session to computer C.
All Bitvise command-line clients support all authentication methods supported by Bitvise SSH Client, can load settings from a profile configured in the graphical client, work with the same user keypair and host key database as the graphical client, can connect through a SOCKS or HTTP CONNECT proxy, and support a common set of command-line parameters controlling most aspects of establishing an SSH connection.
Command-Line Tunneling Client
Bitvise SSH Client incorporates stnlc, a scriptable command line port forwarding client with support for static port forwarding rules, dynamic SOCKS-based tunneling, as well as the FTP-to-SFTP bridge.
FTP-to-SFTP Bridge
Bitvise SSH Client incorporates an FTP-to-SFTP bridge which performs translation between the FTP and SFTP protocols, allowing any FTP client application to connect securely to an SFTP server through Bitvise SSH Client. Both active mode and passive mode FTP data connections are supported, as well as restarted transfers, directory listings and other features. All FTP clients should be able to list directories and transfer files across Bitvise SSH Client’s FTP-to-SFTP bridge, including integrated clients in applications such as DreamWeaver, GUI clients such as BulletProof FTP, and command line clients such as the default ftp.exe client accompanying Windows. If an FTP client you use fails to work with Bitvise SSH Client’s FTP-to-SFTP bridge, let us know.
See Accessing an SFTP Server with an FTP Client for more information about the FTP bridge.
Using with Bitvise SSH Server
When connected to Bitvise SSH Server, our client can do all of the above, as well as the following:
bvterm console: When connected to Bitvise SSH Server, our client provides you with the best console available on the Windows platform. Our bvterm protocol supports the full spectrum of a Windows console’s features: colors, Unicode characters, all-key access and large scrollable buffers.
Remote server configuration: Using Bitvise SSH Client, all SSH Server settings can be configured remotely without having to use Remote Desktop.
Windows version compatibility
Bitvise SSH Client supports the following Windows versions:
A recent Bitvise SSH Client version should be used on all platforms. The SSH Client is security-sensitive software that communicates across a network. Using a recent version is the only way to receive updates. Therefore, we do not recommend indefinite use of older versions.
Encryption and security features
Key exchange algorithms:
Data integrity protection:
FIPS 140-2 validation
When FIPS is enabled in Windows, our software uses Windows built-in cryptography, validated by NIST to FIPS 140-2 under certificates #2937, #2606, #2357, and #1892. On Windows XP and 2003, our software uses the Crypto++ 5.3.0 FIPS DLL, originally validated by NIST under certificate #819 (historical). When FIPS mode is not enabled, additional non-FIPS algorithms are supported.
Cryptographic implementations and availability
Current Bitvise software versions (8.36 and higher) use the following cryptographic implementations for different algorithms, on different versions of Windows:
What is SSH?
The Secure Shell protocol version 2, or SSH2, specifies how a client can connect securely to an SSH server, and then use the resulting secure link to access the server’s resources. Among other things, the client can run programs; transfer files; and forward other TCP/IP connections over the secure link.
The SSH2 protocol is a descendant of the SSH v1.x series of protocols. SSH version 2 is standardized at IETF, and the vast majority SSH implementations now support SSH version 2. SSH version 1 is less secure, and is almost no longer being used.
How secure is SSH?
The Secure Shell protocol provides the services of server authentication; encryption; data integrity verification; and client authentication. Server authentication is performed using RSA, DSA, or ECDSA public key algorithms. For encryption and data integrity verification, a number of algorithms are provided which every SSH product can implement in a modular fashion. Client authentication can be performed using a password, a public key, single sign-on Kerberos, and other methods.
The SSH2 protocol specification is publicly available and has been reviewed by several independent implementers. When properly used, the protocol is understood to be secure against all known cryptographic attacks, passive as well as active.
Client vs. server
In internet protocols, the terms client and server have specific technical meanings:
A client may run all of the time or some of the time, depending on when a user needs it. A client may more likely run on a desktop computer, but can also run on a server computer if this computer needs to send out request or initiate connections.
A server usually runs all the time, in the background. A server may more likely run on a computer in a data center. However, it is also perfectly feasible to use server programs on a desktop computer.
If you are looking for SSH software, you are looking for a server if you want to set up a computer to receive connections from other people and their computers. You are looking for a client if you wish to connect, using SSH, to someone else’s computer.
SSH compared to SSL/TLS
SSH and TLS/SSL are different protocols used for similar purposes. Both protocols are used to authenticate communicating parties and secure data during transport.
SSL/TLS tend to use X.509 certificates, is based on ASN.1 encodings, and is most commonly used to as a security layer for HTTP, SMTP, and FTP traffic.
The SSH protocol tends to use public keys without a certificate infrastructure, is based on a simpler binary encoding, and tends to be used as a security layer for SFTP and SCP file transfers, terminal shell access, and forwarding of connections for other applications.
SSH can be perceived as a less clunky version of TLS. Due to its deliberate independence from X.509 certificates, SSH lends itself well to connections between entities with an existing trust relationship, where TLS does poorly. TLS lends itself better to connections between strangers.
SSH features
SSH is a highly flexible protocol, and many different types of services can use it. The protocol’s open architecture allows these services to run at the same time without impeding one another.
An SSH client and server can transfer files using the protocols SCP and SFTP, which run on top of an established SSH session. While SCP is the old Unix rcp utility transplanted onto a different transport, SFTP is a flexible remote file access protocol that can be used in advanced ways. SFTP is better standardized and widely supported, so often software that provides an SCP-like interface really uses SFTP instead.
Note that SFTP is unrelated to FTP, or to FTP over TLS/SSL. The protocols are independent and very different.
A frequently used service is the remote console. This involves allocating a channel within the SSH session, which is then used as transport for a terminal protocol such as vt100 or xterm. The client displays to the user a console window within which the user can execute command line programs on the server.
SSH also provides exec requests. An exec request executes a program on the server like a remote console, but without expectation of interactive input. Exec requests are useful for automated remote administration.
Another popular SSH function is port forwarding, or TCP/IP connection tunneling. With SSH port forwarding, it is possible to secure a TCP/IP connection established by an independent application that would otherwise be vulnerable to network attacks. To learn more, check out our introduction to port forwarding.
What do you want to do?
I want to connect from my computer to an SSH server that’s already set up:
I want to set up an SSH server for other people to connect to:
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 roles of Bitvise SSH Client and SSH Server
Bitvise SSH Server is used to accept connections from SSH clients. The server is intended to run for a prolonged period of time, and will provide SSH clients that connect with access configured by the server administrator. The SSH server might be configured to provide access to a terminal console, port forwarding, or file transfer to and from the server using SFTP, SCP, or FTPS.
Bitvise SSH Client is used to initiate connections to SSH servers. It is usually used interactively, so it will only run when a user runs it, but it can also be launched unattended to run scripted commands or file transfers, or to maintain an SSH connection for port forwarding. The SSH client is used to access a terminal console on an SSH server, to initiate port forwarding, or to initiate file transfers to and from SSH servers using SFTP.
Both products are connectivity products. They cannot be used standalone. For an SSH server to be useful, you need clients that will connect to it. For an SSH client to be useful, you need an SSH server to connect to.
The two products can be installed on the same machine, but there is no benefit in connecting an SSH client to an SSH server running on the same machine, except for testing.
Bitvise SSH client
Время на чтение: 2 минуты
На рынке приложений для ПК, которые специализируются на SSH подключении, есть множество клиентов. Но почему-то среди приложений для ОС Windows клиент Putty пользуется особым внимание, в то время как другое ПО отошло на задний план.
В частности, к таким приложениям можно отнести Bitvise SSH client, которое попросту недооценили пользователи Виндовс.
Его настройка, а также основные особенности будут рассмотрены в данной статье.
Почему лучше скачать именно Bitvis, а не Putty
Вас может спугнуть два фактора перед тем, как вы решитесь загрузить Bitvise SSH client к себе на компьютер: приложение распространяется платно, нет версии rus для него. На счет первого довода можно поспорить, поскольку для личного пользования Bitvise SSH client можно скачивать бесплатно, а вот компаниям приложение обойдется дороговато. А к англоязычной версии клиента со временем можно привыкнуть.
Основное преимущество Bitvise SSH client в том, что этот клиент идет с графическим интерфейсом, о чем пользователи Putty только и мечтают. Кроме того, в приложении легко разобраться, потому вы быстро научитесь заходить на server и использовать Bitvise SSH client для своих целей.
Как пользоваться Bitvise
В целом, если вы ранее пробовали заходить на любой server, используя какой-либо клиент, то вы с легкостью научитесь пользоваться Bitvise SSH client. Для того, чтобы зайти на server, для начала вам нужно воспользоваться модулем клиента и сгенерировать публичный ключ. Для этого вам нужно будет лишь указать, куда сохранять ключи, какое шифрование использовать, прописать пароль (а лучше не прописывать) и нажать Generate.
А чтобы зайти на сервер, вам нужно будет лишь прописать его параметры в разделе Login и после этого попробовать подключиться. После этого вы подтвердите ключ сервера и перед вами появится терминал для управления хостом. Вот и вся премудрость использования клиента Bitvise!
