Home
Remote desktop

Remote desktop

Windows-only embedded tabs; an external client everywhere else. Stated plainly: embedded RDP tabs host the Microsoft RDP ActiveX control, so they exist on Windows only.

How it works per platform

On Windows
Choose a live desktop inside RemoteFlow as an embedded tab, or open Remote Desktop Connection as a separate, isolated client. The external action stays available as a fallback, and the default is a setting. RDP connections open as tabs in the Terminals workspace.
On Linux and macOS
RemoteFlow does not load the Windows component and keeps the external-client workflow, naming the native client to use when it cannot launch one directly.
Per-connection options
Domain, resolution, full screen, multi-monitor, clipboard redirection and drive redirection.
No password in .rdp files
Not even as the encrypted blob the format permits. A saved RDP password is handed to Windows for the seconds the client needs to start and taken straight back out; the generated .rdp lives in a per-launch folder that is deleted afterwards.

One platform difference, stated plainly. Embedded Remote Desktop tabs — a live Windows desktop rendered inside a RemoteFlow tab — are Windows-only. On Linux and macOS, RDP connections open in the platform's own client. Everything else in RemoteFlow is identical on all three platforms.

RDP as a first-class connection

An RDP connection's details with Launch RDP enabled and SFTP disabled — An RDP connection: Launch RDP enabled, Open SFTP disabled — actions are honest per protocol.

Creating a new connection with a protocol picker — RDP is one of the five protocols in the connection editor.

Set your preference on Windows

On Windows, RemoteFlow's settings include one Remote Desktop option: whether a connection opens as an embedded tab or in the external client by default. The external fallback stays one click away either way.