CrossDesk remote desktop features
From a single remote computer to a wall of connected desktops, keep your devices within reach.
Cross-platform remote desktop
Start remote sessions between Windows, macOS, and Linux computers. The main window brings your device ID, connection controls, and recent devices together for quick reconnection.
Remote sessions support keyboard and mouse input, audio, text clipboard sharing, and file transfer. Availability depends on the client platform and version.
Download desktop clients →
DeskHub: manage multiple devices
Preview multiple remote devices in one window, organize them into groups, expand the desktop you want to control, and connect, disconnect, or distribute files in batches.
DeskHub supports group control and streaming settings. Group control sends identical coordinates and keys to connected devices, so results can differ across screen sizes.
Resolution, frame rate, and bandwidth controls depend on the remote device’s capabilities.
Browser and mobile access
Enter a device ID and password in the Web client to start a connection. Native iOS and Android clients also let you control a computer from a phone or tablet.
The remote computer must have CrossDesk installed and running. Mobile and browser clients may support a different set of features from desktop clients.
Open web client →
Terminal CLI: connect from the command line
crossdesk-cli connects to a computer by its 9-digit device ID and starts in read-only, silent mode. Select a monitor, adjust quality, zoom and pan, or enable keyboard and mouse control when needed.
Standard terminals display the desktop as ANSI characters. Terminals supporting the Kitty graphics protocol can show pixel graphics. The CLI detects Kitty support automatically and falls back to ANSI.
Captured on October 31, 2026 from real read-only sessions with the same host, using a 128 × 40-cell pseudo-terminal to capture and render protocol output. Appearance varies with terminal fonts, window size, and protocol support. Select an image to view it at full size.
Install and connect
Install Node.js 22 or later and npm. Installation selects the native executable for your operating system and CPU architecture; no local compilation is required.
npm install -g @chunkdash/crossdesk-cli@latest
crossdesk-cli doctor --json
crossdesk-cli 123456789
Replace 123456789 with the host’s 9-digit device ID and enter its password at the hidden prompt. doctor checks the local environment without connecting. The host must run CrossDesk with a capturable graphical session, and both ends must use a signaling service that supports temporary CLI identities.
Choose a renderer
Select ANSI or Kitty explicitly. Use --zoom native to inspect fine detail in ANSI mode.
crossdesk-cli 123456789 --renderer ansi --zoom native
crossdesk-cli 123456789 --renderer kitty
View, control, and exit
| Action | Keys |
|---|---|
| Enable keyboard and mouse control | Press c in read-only mode |
| Inspect detail / fit the desktop | d / f |
| Zoom / pan | +, - / arrow keys |
| Pause remote input and enter local command mode | Ctrl+] |
| End the session | Press q in read-only mode; in control mode, press Ctrl+], then q |
Zoom and pan shortcuts apply in read-only or local command mode. In control mode, ordinary keys are sent to the host; press Esc in local command mode to return to the session. The CLI acts only as a controller and currently does not provide audio playback, file transfer, or clipboard sync.
Hardware acceleration and connectivity
Built on MiniRTC, CrossDesk supports H.264 / AV1 video and hardware codecs. NVIDIA, VideoToolbox, and other acceleration options depend on hardware, operating system, and build configuration.
Connections attempt P2P access first and can use a TURN relay when a direct connection is unavailable. You can also deploy your own signaling and relay services.
Read the self-hosting guide →