You can set up free remote desktop access between your own devices in about 10 to 15 minutes with RustDesk.
This is for home users, remote workers, IT helpers, and anyone tired of subscription-heavy remote access apps.
Estimated time: 10–15 minutes for direct setup, about 20 minutes if you also add your own relay server.
Quick Answer
Install RustDesk on both devices, open it, note the ID and one-time password on the computer you want to control, then enter that ID from your second device and connect. If you want more control, you can also point both apps to your own self-hosted RustDesk server using Docker.
Why this trick is worth using
RustDesk is an open-source remote desktop tool built for people who want a cleaner alternative to the usual mix of limited free plans, commercial-use nags, and account lock-in. The official project offers clients for Windows, macOS, Linux, Android, iPhone, and iPad, and the setup is refreshingly simple for basic remote help or access. Recent coverage from XDA also highlighted its strong file transfer, multi-platform support, and self-hosting flexibility.
What you need first
- Two devices with internet access
- RustDesk installed on both devices
- Optional: a small server or VPS plus Docker and Docker Compose if you want your own relay
How to set up RustDesk for free remote access
-
Install RustDesk on both devices.
Download the correct build from the official RustDesk website or the project’s GitHub releases page. The client docs also list platform-specific install notes. -
Open RustDesk on the computer you want to control.
When the app launches, it will show an ID and a one-time password. Leave that window open. That device is now ready to receive a connection. -
Enter that ID on your second device.
On your laptop, tablet, or phone, open RustDesk and type the remote device’s ID into the connect box. Start the session, then enter the password shown on the remote computer. -
Approve permissions and test the session.
On macOS and some Linux setups, RustDesk may ask for screen recording, accessibility, or input permissions. Approve them, reconnect if needed, and make sure you can move the mouse, open an app, and resize the remote window. -
Set a permanent password if this is your own machine.
In RustDesk, open Settings and then Security so you do not have to rely on a fresh one-time password every session. The official client documentation also notes a--passwordoption for command-line setup. -
Optional: point both devices to your own RustDesk server.
If you want your own infrastructure, RustDesk’s self-host guide says the minimum working ports are TCP 21115–21117 and UDP 21116. A simple beginner route is the official Docker method: install Docker, download the official RustDesk OSS compose file, then rundocker compose up -d. Full details are in the RustDesk self-host docs. -
If you self-hosted, add your server in the app.
On each device, open Settings > Network, unlock the network settings, and enter your own server details. This tells both clients to use your ID and relay server instead of the public default.
Expected checks
- You see a RustDesk ID and password on the target device.
- The second device connects without asking you to create an account.
- You can control the mouse and keyboard on the remote system.
- File transfer or clipboard sync works if you enable those features.
- If you self-hosted, both devices show your custom server in Network settings.
Common mistakes
- Installing RustDesk on only one device and expecting it to discover the other automatically.
- Ignoring macOS accessibility or screen-recording prompts, which can block control even when the connection succeeds.
- Forgetting to open the required ports when self-hosting, especially TCP 21115–21117 and UDP 21116.
- Typing the wrong ID or using an expired one-time password after the app has refreshed.
- Assuming iPhone and iPad can be remotely controlled the same way as desktops; the official docs note iOS cannot itself be controlled remotely.
Troubleshooting
- Connection starts but screen control does not work: Recheck local permissions on the remote device, especially macOS screen recording and accessibility access.
- Direct connection fails: Try again first, then use your own relay server if you are behind strict NAT or firewall rules.
- Self-hosted server seems online but clients do not connect: Verify your ports, confirm the server address is correct in Settings > Network, and make sure both devices are using the same server settings.
- Session feels slow: Lower the display quality in RustDesk and test from a stronger network. XDA’s hands-on write-up notes RustDesk generally feels lean, but bandwidth still matters.
Takeaway
If you want a free remote desktop tool that works quickly and gives you the option to self-host later, RustDesk is an easy one to keep in your toolkit. Start with the no-account direct connection, then move to your own server only if you need tighter control.
Related links
- RustDesk official site
- RustDesk client documentation
- RustDesk self-host documentation
- RustDesk on GitHub
- RustDesk releases
- XDA hands-on review
Next step: If this solves your quick remote-access problem, save RustDesk on your main devices now and set a permanent password before the next time you actually need it.