Xshell review

Xshell is NetSarang’s Windows terminal emulator for connecting to and managing remote Unix, Linux, and Windows hosts. It supports SSH1 and SSH2, SFTP, Telnet, Rlogin, serial connections, and RDP, so it covers more than SSH-only workflows. Connections can use passwords, public keys, or Kerberos, with Jump Host proxies and TCP/IP or X11 tunneling available for access paths that need them.

For daily administration, Xshell organizes saved sessions in folders and can apply configuration updates in batches. A Compose Pane lets you draft commands and broadcast them across terminal sessions. It also supports scripts in Python, VB, and JScript, script recording, and output-based triggers. Within its tabs, you can run CMD, PowerShell, and WSL commands.

That breadth makes Xshell a Windows-based connection and session-management tool, not a cross-platform terminal client. Its fit depends partly on whether your users and devices can stay on Windows.

Xshell packs a useful range of remote-access options into one Windows client. The protocol list includes SSH, SFTP, Telnet, Rlogin, serial, and RDP; authentication and tunneling options include public keys, Kerberos, Jump Hosts, and X11. That can reduce the need to keep separate tools around for different kinds of hosts.

The features that matter most for repeat administration are session folders, batch configuration updates, and command broadcasting through the Compose Pane. Scripting, recording, and output-based triggers add ways to automate recurring work, while CMD, PowerShell, and WSL tabs keep local Windows commands close to remote sessions.

The pricing is straightforward for an individual commercial user: according to the pricing information, Xshell costs $119 as a one-time perpetual license, covers one user on up to two devices, and includes one year of maintenance, updates, and support. Xshell Plus is $139 and adds Xftp. A fully functional 30-day evaluation is listed with no credit card required. Personal and educational use is free, but commercial and business use is prohibited.

The clearest constraint is the Windows-only desktop client. In one r/linuxadmin thread, an Xshell user switching to Linux said maintaining a large host list in SSH config felt less comfortable; commenters suggested alternatives such as ClusterSSH and Ansible. Xshell may suit a Windows-based workflow, but it is not the choice for teams that need the same client on Linux.

The free license is also not a business-use option: the listed terms restrict it to personal, home, and educational use. The commercial Xshell license is single-user and limited to two devices, so it is not a shared team license. The pricing information does not publish seat or device limits for the free tier, or renewal prices for maintenance after the included year. Maintenance extensions are available for one or two more years, but their prices are not published.

Campus License Subscriptions are available for colleges and departments, but pricing requires contacting sales. That leaves larger deployments without a public price to compare. One Reddit user also described a display-plot limitation in their free-version use; we would treat that as an individual report, not a confirmed product-wide restriction.

The commercial Xshell license is a $119 one-time purchase for one user on up to two devices, with one year of maintenance, updates, and support included, according to the published pricing details. Xshell Plus costs $139 one time and adds Xftp; that is a $20 step up. The $399 Xmanager Power Suite includes Xmanager, Xshell, Xftp, and Xlpd, a $260 jump from Xshell alone.

Personal, home, and educational users can use Xshell free for non-commercial purposes. Commercial use is prohibited on that plan. The 30-day evaluation is fully functional and does not require a credit card. Campus License Subscriptions require a sales quote.

These are perpetual licenses, not monthly or annual subscriptions. The catch: only the first year of maintenance is included. Prices for maintenance extensions and renewals are not published, nor are seat or device limits for free use. Teams should confirm licensing costs with sales before standardizing.

Moving to Xshell means rebuilding or bringing over your connection setup, but the published material does not say whether sessions can be imported from another terminal or exported from Xshell. Before switching, inventory saved host details, authentication methods, tunnels, scripts, and triggers; the product brief lists support for these, but does not document a migration path. Treat export and import as questions to verify, not assumed features.

Leaving may be simpler for connections than for configuration: Xshell supports common protocols including SSH, SFTP, Telnet, and RDP, but the brief does not describe portable session files or script compatibility with other clients. Xshell is a Windows desktop client, so admins moving to Linux workstations should plan on a different tool.

We have no Reddit posts or comments in the published sources, so we can’t substantiate a claim about why users leave. Check the current docs for export options, then test a small set of sessions before moving a team.