By Remote desktop editorial team · Last verified [date] · Current release [tag]
When to self-host
Use public servers for a simple first connect. Self-host when you want private ID and relay endpoints on infrastructure you control. Upstream docs: rustdesk.com/server and client Network notes.
Client settings
In RustDesk, open Settings → Network, unlock network settings, and enter your ID server, relay, key, and API when using Pro. Export/import config strings appear in upstream deployment docs for fleet setups (--config).
Scope
This guide does not run your server for you. It maps the Windows client doors. Related: unattended, first run, GitHub, /.
Extra remote desktop context
Prefer GitHub Releases for rustdesk/rustdesk when you need rustdesk--x86_64.exe or rustdesk--x86_64.msi. ARM64 peers take rustdesk-*-aarch64.exe from the same tag. Public copy says the current release rather than hardcoding dotted versions.
Wake both machines, confirm Your ID, and move the mouse once before you chase self-host, unattended passwords, or file transfer trees. Skip Softonic-style wrappers. Related: download safe, releases, GitHub, home.
Lab images may block unknown executables. Use a PC you control or an approved channel. Sleep and wrong IDs kill more sessions than codec choice. Update through the same GitHub door you used to install. Comparison shape: vs AnyDesk.
Tags are bare numbers without a v prefix. Nightly builds exist for testers; everyday installs prefer stable tag assets. Read AGPL-3.0 licence text on the repo before redistributing modified builds.
More remote desktop context for Windows
Prefer GitHub Releases for rustdesk/rustdesk when you need rustdesk--x86_64.exe or rustdesk--x86_64.msi for remote desktop on Windows. ARM64 peers take rustdesk-*-aarch64.exe from the same tag. Public copy says the current release rather than hardcoding dotted versions in HTML.
Wake both machines, confirm Your ID, and move the mouse once before you chase self-host, unattended passwords, or file transfer trees for remote desktop. Skip Softonic-style wrappers. Related: download safe, releases, GitHub, home, vs AnyDesk.
Lab images may block unknown executables. Use a PC you control or an approved channel when you need a clean remote desktop path. Sleep and wrong IDs kill more remote desktop sessions than codec choice. Update through the same GitHub door you used to install.
Tags are bare numbers without a v prefix. Nightly builds exist for testers; everyday remote desktop installs prefer stable tag assets. Read AGPL-3.0 licence text on the repo before redistributing modified builds. First-hour notes live on /installed. Machine chooser: for this computer.
A successful remote desktop connect on two machines you trust beats stacking three mirrors. Keep one Start Menu entry. Prefer the Flutter x86_64 exe or msi on the stable tag unless you have a specific reason to take another asset. Sciter-labelled builds appear as legacy UI paths on some tags.
Frequently asked questions
Do I need self-host to start?
No. Public servers work out of the box. Self-host is optional. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.
Where are the fields?
Client Settings → Network (unlock network settings): ID, Relay, API if Pro, and key. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.
Where do Windows files come from?
GitHub Releases for rustdesk/rustdesk. Prefer rustdesk-*-x86_64.exe or .msi. Related: releases. Prefer GitHub Releases for rustdesk/rustdesk, confirm the asset name before you run it, and keep one update door for remote desktop on Windows.