Skip to content
RemoteAccessApp
Get Pro

Switch from Windows Terminal

Go beyond ssh in Windows Terminal: saved hosts, files and more

Windows Terminal is a host for command-line shells, and Windows' OpenSSH client gives you ssh, sftp and scp on the command line. Microsoft's documentation lists OpenSSH on Windows 10 as a feature on demand you install from optional features. A graphical file manager and saved RDP or VNC hosts aren't part of them.

RemoteAccessApp gives your servers a home: saved SSH hosts in tabs, a two-pane SFTP and FTP file manager, server-to-server copies, saved RDP and VNC, and your Windows PCs.

Download freeCreate a free account
  • Saved hosts in tabs
  • Graphical SFTP and FTP
  • RDP and VNC too

Fed up with Windows Terminal? Here's what changes

  • File transfer by command line

    With Windows Terminal: Microsoft's OpenSSH documentation describes sftp and scp as command-line tools.

    With RemoteAccessApp: A two-pane SFTP and FTP file manager with drag and drop, server-to-server copies and uploads to many servers. Switching from FileZilla covers these copies in detail.

  • OpenSSH may need installing

    With Windows Terminal: Microsoft's documentation lists OpenSSH on Windows 10 as not installed by default, to install and enable from optional features.

    With RemoteAccessApp: RemoteAccessApp's SSH client is part of the app, installed in one go without administrator rights.

  • A terminal, not a host list

    With Windows Terminal: Windows Terminal is a host for command-line shells, per Microsoft.

    With RemoteAccessApp: Saved hosts with their keys and passwords, folders and search, a host key check, and one command sent to every server. Switching from PuTTY covers saved passwords and .ppk keys.

More reasons to switch

  • Host list on every PC

    Your hosts follow your account, and open in a browser terminal too. The same synced list comes up in switching from mRemoteNG.

  • RDP and VNC

    Saved RDP and VNC connections in tabs next to your SSH hosts. If they live in a connection manager now, switching from Royal TS and switching from Remote Desktop Manager cover moving them.

  • Your PCs

    Remote desktop to your Windows PCs through any router, plus PowerShell on many PCs at once.

Windows Terminal vs RemoteAccessApp

Windows Terminal and RemoteAccessApp side by side, as of October 2026
Saved hosts with passwords or keysWindows TerminalHosts in your ~/.ssh/configRemoteAccessAppYes, passwords encrypted on your PC
Graphical SFTP and FTP file managerWindows TerminalCommand-line sftp and scpRemoteAccessAppYes: two-pane SFTP and FTP file managers, free
Server-to-server file copiesWindows Terminal Not listedRemoteAccessAppYes: streams between two servers, or uploads to many at once
Saved RDP and VNC connectionsWindows Terminal Not listedRemoteAccessAppYes: saved RDP and VNC connections in tabs, free
SSH from a browser or phoneWindows Terminal Not listedRemoteAccessAppYes, on the website
One command sent to every serverWindows Terminal Not listedRemoteAccessApp Yes

Windows Terminal facts are from its official website and documentation as of October 2026; products change. RemoteAccessApp facts are for the current version. * Not listed: we didn't find it on Windows Terminal's official site when we checked, which doesn't mean it can't be done.

Switch from Windows Terminal if

  • You manage more than a couple of servers.
  • You want a graphical file manager and server-to-server copies.
  • You want RDP, VNC and your PCs next to SSH.
Download freeCreate a free account

Switch from Windows Terminal in 2 minutes

What carries over, what doesn't and tips for each kind of tool are in the switching guide.

  1. Step 1: Install RemoteAccessApp and sign in

    Download the free installer for Windows 10 or 11 and choose the Console. It installs without administrator rights. Create a free account if you don't have one.

  2. Step 2: Bring your hosts across

    On the Connections tab, Import from this PC… finds hosts in your SSH config file, saved .rdp files and Windows' recent Remote Desktop connections, and Import from file… reads a CSV file (there's a template to fill in). Add the rest by hand: address, port, user name and protocol. Your Windows Terminal setup stays as it is.

  3. Step 3: Import your keys

    Import your private keys for key sign-in: OpenSSH, PEM and PuTTY .ppk keys are read, passphrase-protected ones included. Passwords are never imported: you're asked for each one the first time, and can save it encrypted on your PC.

  4. Step 4: Check each server's key and connect

    The first time you connect, compare the host key fingerprint with the one you expect and trust it. A server whose key changes later is refused with a warning.

  5. Step 5: Keep your ssh config

    Import from this PC… reads the hosts in your ~/.ssh/config, so your existing aliases come across. SSH to a Linux server.

Questions, answered

Windows Terminal and other product names on this page are trademarks of their respective owners, used only to identify those products. RemoteAccessApp isn't affiliated with, endorsed by or sponsored by them. Facts about other products come from their official websites as of .

RemoteAccessApp features