A reachable computer still needs a public device ID
Discover or connect by address
Discover local devices or enter a hostname or IP address. Across subnets, establish reachability through your own network or VPN first.
SubnetDesk / FEATURES
What SubnetDesk can do
Take in the whole picture first, then go deeper where it matters. Every capability links to the detailed reference, including platform differences and permissions.
BUILT AROUND YOUR DAY
Already on your network. Connect directly.
Reach a computer by its accessible address on a LAN, private link or VPN. Keep remote desktop, file and audio work on your network.
Seeing the screen is only part of the task
Work within a remote session
Use file transfer, audio and clipboard alongside remote control, subject to platform support and system permissions.
You need to know who and where you are connecting
Verify identity and network scope
Check the target address, fingerprint and authentication settings. Public rendezvous or relay services are not prerequisites; unreachable networks still need routing.
Go deeper into the features
For devices that can already reach each other
SubnetDesk is an independently maintained RustDesk fork for LANs, private links, home labs and VPN-connected networks. It needs no public device ID, rendezvous server or Internet r…
Read the detailsAutomatic mDNS discovery
Find nearby devices on the LAN, then use recent devices, favorites and local aliases to return to frequently used computers. Stable identity distinguishes machines; a familiar disp…
Read the detailsDirect hostname and IP connections
Connect using a hostname or IP plus port. Native connections use TCP 21118 by default; LAN settings can change it. Configure a username and password on the receiving computer, enab…
Read the detailsRemote desktop, displays and input
View and operate the remote desktop with the mouse and keyboard. The native session toolbar provides display selection, scaling and quality-related controls. Multiple displays, cod…
Read the detailsFile transfer, clipboard and audio
The native client provides file transfer for sending documents, retrieving results or managing files during support. Read and write access still depend on session permissions, the …
Read the detailsOptional browser remote access
SubnetDesk already includes browser access; it is not limited to native clients. The desktop must explicitly enable Web access and configure listen addresses, allowed networks and …
Read the detailsIdentity and access boundaries
Username and password: explicitly configured on the receiving host; passwords are stored as Argon2id hashes. Device fingerprint: verify over a separate trusted channel on first con…
Read the detailsGet started in three steps
Prepare the host: install and open SubnetDesk, configure LAN credentials, discovery and the listening port, then grant necessary screen and input permissions. Find the target: ensu…
Read the detailsPlatforms and installation
Release downloads cover Windows, macOS, Linux and Android. See installers and release information for architectures and formats. There is currently no official iOS installer; brows…
Read the detailsUpdates and network requests
Windows and macOS desktop builds implement signed updates: check availability, read release notes, choose automatic downloads and install after verification. Update checking is ena…
Read the detailsCommon questions
Symptom First checks A device is missing LAN discovery, mDNS and guest-network isolation; try a manual address Discovered but connection fails Service readiness, credentials, TCP p…
Read the detailsWhen it is not a fit
Devices have no reachable network and no VPN will be configured. The workflow depends on public device IDs, rendezvous or Internet relays. A released native iOS client is essential…
Read the detailsSource and license
The public GitHub repository uses AGPL-3.0; consult its license text for the terms. Continue with the browser guide, Linux host notes or official release. Return to the product ove…
Read the details