RustDesk is a remote-desktop program for viewing and controlling another computer across a local network or the Internet. Each device runs a client that can receive a connection through its displayed ID or start one by entering the other device’s ID. RustDesk carries screen updates, keyboard and pointer input, clipboard data, and permitted files. It does not create an operating-system account or bypass the host’s screen and accessibility permissions.
ID starts the session
The receiving device shows an ID and a temporary password. The person at the controlling device enters the ID, then authenticates with the password or waits for the remote person to approve the request. The ID locates the device through the configured service; it is not a secret by itself.
Share the temporary password only for the intended session. A permanent password enables unattended access and remains useful after the person leaves the computer, so it needs a unique value and restricted distribution. Reusing an ordinary account password increases the damage if it is exposed.
Permissions shape control
RustDesk cannot provide full control until the host operating system permits screen capture and input. On some systems, screen recording, accessibility, or service permissions must be granted separately. A connected session can therefore show a blank screen or accept no clicks even when the ID and password are correct.
Session permissions can allow keyboard and pointer input, clipboard synchronization, file transfer, audio, and remote restart. Turn off capabilities that the task does not require. Clipboard access may expose a recently copied password, while file transfer gives the controller a path to read or write data outside the visible application.
Direct or relayed
RustDesk attempts to establish a direct peer connection after the ID service introduces the devices. Firewalls, carrier-grade address translation, or restrictive networks can prevent that path. The session then uses a relay service, which forwards the encrypted traffic without becoming the remote desktop itself.
A relayed session moves screen traffic through the relay’s network allowance. Higher resolution, rapid video changes, and long sessions increase bandwidth use. If performance changes between two networks, check whether the connection switched from direct to relayed before assuming the remote computer is overloaded.
Run your server
RustDesk can use public services or point clients to a self-hosted backend. The free server contains an ID and signaling component plus a relay component. Self-hosting gives the administrator control over those services, but it also transfers responsibility for firewall rules, availability, keys, logs, backups, and upgrades.
Every client must receive matching server information and the correct public key. A typographical error can leave IDs unresolved or cause a key mismatch. Hosting the server behind a private address without a reachable domain or port mapping also prevents outside clients from reaching it. Test one external connection before deploying configuration to many devices.
OSS and Pro differ
The open-source server supplies the connection core. It does not include the commercial server’s complete web console, device management, API, identity-provider integration, and other centralized controls. Installing the free server should not be planned around administrative controls that belong to the other edition.
For a small deployment, individual client configuration may be enough. A larger fleet needs a repeatable method for server settings, passwords, ownership, revocation, and updates. Copying one configuration blindly can duplicate credentials or grant unattended access to devices that should require local approval.
Files cross separately
File transfer is different from controlling the desktop. It opens a transfer interface between local and remote storage and can continue without dragging files through the remote screen. The destination still needs enough space and write permission, and a partial transfer does not become complete merely because the session closes cleanly.
Confirm the destination path and compare the finished size before removing the source. Remote support can also expose personal folders that are unrelated to the repair. Limit the transfer scope and close the connection when the requested work ends.
Mobile has boundaries
Mobile clients follow platform restrictions. An Android device may need additional permissions or a supported input service for remote control. An iPhone or iPad can use RustDesk as a client, but the platform does not expose the device as a fully controllable remote host.
Keep the app foregrounded when the mobile system suspends background network activity. A remote session is not a durable management channel if the operating system can stop it to save power. For unattended computers, install and configure the system service instead of relying on an open portable window.
