RustDesk for Windows
Most Windows PCs should use the x86_64 EXE. Install RustDesk for regular remote access, or use the MSI package when you need managed or scripted deployment.
RustDesk 1.5.3 · EXE · x86_64
Download the RustDesk client that matches your operating system and processor architecture. RustDesk 1.5.3 provides builds for desktop and mobile devices in multiple package formats. Installation, system permissions, and whether a device can act as a controller or controlled endpoint vary by platform.
Most Windows PCs should use the x86_64 EXE. Install RustDesk for regular remote access, or use the MSI package when you need managed or scripted deployment.
RustDesk 1.5.3 · EXE · x86_64
Choose the DMG that matches your Mac. Apple Silicon uses the ARM64 build and Intel Macs use x86_64. A Mac that will be controlled remotely also needs the required macOS privacy permissions.
RustDesk 1.5.3 · DMG · Apple Silicon / Intel
Choose the package that matches your distribution. Debian and Ubuntu use DEB, Fedora and CentOS use RPM, while AppImage and Flatpak provide additional installation options.
RustDesk 1.5.3 · DEB · x86_64
Install the universal APK or choose an architecture-specific Android build. Android can act as a controller and, after the required screen-capture and input permissions are granted, can also receive remote-control sessions.
RustDesk 1.5.3 · Universal APK
Install RustDesk from the App Store to use an iPhone or iPad as a remote controller. The current iOS client can connect to other supported devices but cannot itself be remotely controlled through RustDesk.
App Store · Controller
RustDesk also provides builds for additional processor architectures and Linux package formats. Use this list when the main download cards do not match your device.
Choose a package that matches your operating system and processor architecture. After installation, grant any system permissions required by that platform and launch the RustDesk client.
Windows normally uses an EXE, macOS uses the DMG for Apple Silicon or Intel, Linux should use a package that matches the distribution, Android uses an APK, and iOS installs through the App Store.
Install RustDesk normally for your platform. A Mac that will receive remote control needs Screen Recording and Accessibility permissions; Android requires the appropriate screen-capture and input permissions when used as a controlled device.
After launch, RustDesk displays an ID for that device. Enter another device's ID to start a connection, or provide your own device ID to a trusted person who needs to connect to you.
RustDesk clients use the same remote-access system, but installation, permissions and controller or controlled-device capabilities differ by platform. Each device receives its own RustDesk ID; devices do not share a single ID.
Windows can be used both to control another device and to receive remote connections. Standard installation is suited to ongoing access, while portable use and managed MSI deployment support different deployment needs.
macOS can both start and receive RustDesk sessions, but receiving remote control requires Apple privacy permissions in addition to installing the application.
RustDesk provides packages for major Linux distributions. Remote-access behavior also depends on the desktop environment and whether the system uses X11 or Wayland.
Android can control remote computers and can also accept remote-control requests after screen sharing and the required Android permissions are enabled.
The RustDesk iOS app is a controller. It can connect from an iPhone or iPad to another supported remote device, but the iOS device itself cannot currently be controlled through RustDesk.
On macOS, grant Screen Recording and Accessibility when the Mac will be controlled remotely. On Android, enable screen capture and the additional permissions required for remote input or file access.
The standard RustDesk client can use RustDesk public infrastructure. If you operate your own RustDesk Server, configure the client with your ID Server, Relay Server when required, and the corresponding server Key.
Every RustDesk device has its own ID. To connect, enter the ID of the remote device and complete authorization with its password or local confirmation. Multiple devices can use the same server infrastructure, but they do not share one device ID.
Download and installation
RustDesk 1.5.3 is the current stable GitHub release as of November 21, 2026. The release provides multiple Windows, macOS, Linux and Android builds, with iOS available through the App Store.
The EXE is suitable for normal installation on individual Windows devices. MSI packages are useful for managed deployment and software-distribution workflows. Choose the package that matches the processor architecture of the device.
Download the ARM64 / Apple Silicon DMG for Macs with an Apple M-series processor. Intel Macs should use the x86_64 DMG. After installation, a Mac that will receive remote control must also be granted the required privacy permissions.
Ubuntu and Debian-based distributions normally use DEB, Fedora and CentOS-based distributions use RPM, Arch Linux and Manjaro use pkg.tar.zst, and openSUSE uses its corresponding RPM. AppImage and Flatpak builds are also available.
The Android client is available from the official RustDesk GitHub Releases and from F-Droid. RustDesk is not currently distributed through Google Play.
No. The current RustDesk iOS app is a controller only. It can initiate connections to supported remote devices, but RustDesk does not currently support controlling an iPhone or iPad as the remote endpoint.
No. Each RustDesk device receives its own device ID. Clients may use the same public or self-hosted server infrastructure, but the ID identifies an individual device.
Open RustDesk network settings and configure the ID Server and server Key for your self-hosted environment. A Relay Server can also be specified when required. Detailed Server OSS deployment and client configuration steps are available in the RustDesk documentation.