SubnetDesk 2.0 · Remote desktop for your LAN and VPN
Discover nearby devices and connect directly by IP or hostname, without a rendezvous or relay server.
An independently maintained RustDesk fork for Windows, macOS, Linux, and Android.
English · 简体中文
Why SubnetDesk · Features · Download · Quick start · Build
Actual 2.0 interface · New logo and unified theme · Nearby devices and quick reconnection
SubnetDesk focuses on one clear use case: remote control between devices that can already reach each other. Connect through local discovery or a manually entered address, without public device IDs, cloud accounts, or a coordination server.
That makes it a good fit for home labs, offices, classrooms, on-site support, and private networks connected by WireGuard, Tailscale, OpenVPN, or another VPN.
| SubnetDesk | Typical RustDesk deployment | |
|---|---|---|
| Connection | Direct IP address or hostname | Device ID through rendezvous, with optional relay |
| Discovery | Automatic mDNS discovery on the LAN | Device ID or address book |
| Server dependency | No coordination server required | Public or self-hosted rendezvous/relay server |
| Best suited for | LANs, routed private networks, and VPNs | Internet and cross-NAT access |
Important
SubnetDesk does not provide Internet rendezvous or relay services. The two devices must be reachable through the same LAN, a routed private network, or a VPN.
| Capability | The 2.0 experience |
|---|---|
| New interface | A unified logo, device artwork, and light/dark themes, with dedicated Home, Devices, and This device views. |
| Discovery and direct connections | Find nearby devices over mDNS, or connect by IPv4, IPv6, or hostname. The default TCP port is 21118. |
| Recents and favorites | Continue a connection from Home and organize favorite devices into groups. |
| Local access controls | Control discovery and incoming remote access separately; see password, system permission, and access readiness in one place. |
| Remote tools | Remote control, file transfer, terminal, clipboard, and audio, subject to platform support and host permissions. |
| Session windows | Switch between session tabs; drag, pin, or automatically hide the floating remote toolbar. |
| Access protection | Username/password authentication, device fingerprint verification, and CIDR source allowlists. The host stores its access password as an Argon2id hash. |
| Browser access | Optional HTTPS access to desktop hosts from a WebCodecs-capable browser. |
| Desktop updates | Windows/macOS support signature-verified updates when configured in the release build; manual downloads remain available. |
Choose a 2.0 package from GitHub Releases for your operating system and CPU. Use x86_64 for Intel/AMD PCs, and aarch64/ARM64 for Apple Silicon, Windows on ARM, or ARM Linux.
| Platform | Architectures | Packages |
|---|---|---|
| Windows x64 | Intel/AMD 64-bit | Recommended: *-x86_64-setup.exe or *-x86_64-portable.zip (targeting Win7 SP1 and later); separate Win10+ packages are also available |
| Windows ARM64 | Windows on ARM | *-aarch64-portable.zip, .msi, self-extracting .exe; not for Win7 |
| macOS | Intel, Apple Silicon | .dmg |
| Linux | x86_64, ARM64 | .deb, .rpm, .AppImage, .flatpak; Arch package on x86_64 |
| Android | ARM64, ARMv7, x86_64, universal | .apk |
Note
A release marked Pre-release is still a release candidate. The latest stable link may point to an earlier version. Nightly contains development changes.
- Windows: Extract the complete portable ZIP and launch the top-level
SubnetDesk.exe; keep the directory together. Exit from the tray before upgrading, and preserve a backup ofuserdata/, which contains configuration, device identity, and logs. Win10+ builds use the-win10-portable.zipsuffix, MSI, or self-extracting EXE. See the Win7 package notes for scope and validation limits. - macOS: Open the DMG for your architecture and drag SubnetDesk into Applications. To receive remote connections, follow the screen recording and accessibility permission prompts in This device.
- Linux: Choose the package for your distribution. 2.0 ships regular desktop packages; the separate DRM unattended/login-screen package is on hold. See host readiness notes for Wayland and login-screen limits.
- Android: Install the APK; choose
universalif unsure of your architecture. Receiving remote connections also requires the screen-sharing and input permissions requested by the app.
On Windows/macOS, check update status under Settings → About. If automatic updates are unavailable, upgrade from Releases manually; portable builds also use manual upgrades. See automatic updates.
Install and open SubnetDesk on both devices. The steps below use the desktop interface: the host is the device you want to access; the controller starts the connection. Screenshots show the Chinese UI.
- Open This device → Set password and save an access username and password in LAN · Settings. The action reads Change password when already configured.
- Complete the screen recording, input control, administrator access, or other prerequisites shown in This device.
- Return to Home and enable Remote access. Also enable Discoverable if you want other LAN devices to find this host automatically.
- Copy the connection address from This device. The default port is
21118; LAN settings also let you change listen addresses, the port, and allowed source CIDRs.
Discoverable and Remote access are separate controls. Discovery makes the device visible; incoming connections also need a configured password, system permissions, and remote access enabled. A controller does not need to enable incoming access to connect to another device.
- Select a host under Nearby devices on Home or in Devices. If it is not discovered, use + in the top-right corner to enter its address.
- On the first connection, compare the displayed fingerprint with the full fingerprint under This device → Device identity on the host, then trust it and continue.
- Authenticate with the host's access username and password. Manage saved connection credentials under Settings → Security & credentials.
Example addresses:
192.168.1.20
192.168.1.20:21118
workstation.local:21118
[fd00::20]:21118
Across subnets or a VPN, enter the host's reachable address directly. mDNS usually does not cross routers or VPNs, so a device can be reachable without appearing in discovery.
- Open a device's ⋯ menu or details to start File transfer, Terminal, or another tool allowed by the host.
- Use the floating remote toolbar for display, input, and session controls. Pin it to keep it visible, or reveal it from its edge handle after it hides.
- Add frequent devices to favorites for quick access from Home or a favorite group.
Enable Web remote access in the desktop host's LAN · Settings and configure listen addresses, allowed source networks, hosts, and a permission profile. After saving, open Browser access in This device to find the actual HTTPS URL. Follow the instructions to trust the host's generated local CA on the client, or use a valid certificate covering the access hostname. The browser must support WebCodecs and still authenticates with the host's access credentials. See the Web client notes.
| Symptom | Check first |
|---|---|
| Device not listed | Enable Discoverable on the host and allow mDNS on the network, or enter the IP/hostname directly. |
| Timeout or connection refused | Check routing, the host's Remote access toggle, and firewall access to TCP 21118 or your custom port. |
| Address reachable but access denied | Check the host's source CIDR allowlist and access username/password. A blank Network field uses built-in LAN/VPN ranges. |
| Video or input does not work | Check permissions in This device; on Linux also check Wayland, SELinux, and the login session. |
| Fingerprint changed | Independently verify the full fingerprint on the host before trusting it again. Reinstalling or clearing device identity can also change it. |
- Traffic stays on the network path between your devices; SubnetDesk does not require a public coordination service.
- The host's access password is persisted as an Argon2id hash rather than plaintext.
- Device fingerprints provide trust-on-first-use verification and help detect an unexpected endpoint identity change.
- CIDR allowlists let the controlled device limit which source networks may connect.
As with any remote-control software, expose the listening port only to trusted networks, use a strong unique password, and verify fingerprints through a separate trusted channel when possible.
See the SubnetDesk Privacy Policy for session data, local storage, update requests, and deletion controls.
Clone the repository with its submodules, then run the Flutter desktop build:
git clone --recurse-submodules https://github.com/zibo-chen/SubnetDesk.git
cd SubnetDesk
./build.py --flutter --hwcodecThe build requires Rust, Flutter, and platform-specific native dependencies. The native package workflow is the source of truth for pinned tool versions, target architectures, and packaging steps.
Bug reports, feature ideas, and pull requests are welcome. Before opening a change, check the existing issues and keep changes focused on the LAN/VPN-first product scope.
Join the SubnetDesk Discord community, or scan the QR code below to add me on WeChat. Mention SubnetDesk, and I will invite you to the WeChat group.
SubnetDesk is based on RustDesk and retains its open-source foundations. SubnetDesk is an independent project and is not an official RustDesk release.
Licensed under the GNU Affero General Public License v3.0. Use remote-control software only on systems you own or are authorized to administer.




