Kitedesk install guide

Kitedesk installers for Windows, macOS, Linux and Android are downloaded directly from the official site. For now, the Windows installers are not code-signed, so Microsoft Defender SmartScreen shows a warning; the macOS app is not notarized by Apple, so macOS may block the first launch; and the Android app is installed from an APK file rather than an app store. This page covers which file to download for each OS, the install steps, how to get past each warning, the permissions to grant on first launch, and common problems.

In file names, <version> stands for the actual version number, such as 1.4.13-1. The * in the commands below stands in for the version number, so if your downloads folder holds files from more than one version, delete the old ones or type the exact file name.

At a glance

  • Windows 10/11 (x64): kitedesk-<version>-x86_64.msi (recommended, installer) or kitedesk-<version>-x86_64.exe (portable, runs without installing). Not code-signed yet, so SmartScreen shows a warning. Windows steps
  • macOS (Apple silicon and Intel): kitedesk-<version>.dmg. Not notarized yet, so the first launch may be blocked. macOS steps
  • Linux (x86_64): .deb for Ubuntu, Debian and Linux Mint, .rpm for Fedora, .AppImage for other distributions. The deb, rpm, AppImage and tar.gz packages need glibc 2.39 or later (for example Ubuntu 24.04 or later, Debian 13 or later). Linux steps
  • Android (arm64, armv7): kitedesk-<version>-aarch64.apk for most phones, kitedesk-<version>-armv7.apk for older 32-bit devices. Kitedesk is not in an app store, so you install the APK directly. Android steps
  • iOS: in preparation.

Verify the download (SHA-256)

While the installers are unsigned and not notarized, comparing SHA-256 checksums is the most reliable way to confirm that your file is the one published on the official site. Check once before installing.

  • 1. Copy the published value: on the releases page (in Korean), open the version you downloaded and click the copy icon next to the file (its tooltip reads "SHA256 복사").
  • 2. Compute your file's value: run the command for your OS below.
  • 3. Compare: the two values must match from start to finish. If they differ at all, don't install; download the file again from the official site.

The commands that compute the value on each OS are:

  • Windows: open PowerShell from the Start menu and run Get-FileHash $HOME\Downloads\kitedesk-*. PowerShell prints letters in upper case; values that differ only in letter case are the same. To compare automatically, run (Get-FileHash $HOME\Downloads\<file name>).Hash -eq '<copied value>' and check that it prints True.
  • macOS: run shasum -a 256 ~/Downloads/kitedesk-* in Terminal.
  • Linux: in a terminal, go to the folder where you saved the file and run sha256sum kitedesk-*.
  • Android: you can install on the phone without this step. To check anyway, download the same APK on a computer and compare it using the steps above.

A matching SHA-256 confirms that you have the same file that was published; it does not replace code signing or Apple notarization.

Windows

Kitedesk runs on Windows 10 and 11 (x64). Windows 7 and 8.1 are not supported, and no ARM64 build is published.

  • kitedesk-<version>-x86_64.msi: recommended; installs Kitedesk.
  • kitedesk-<version>-x86_64.exe: portable; runs without installing.

Neither file is code-signed, so Microsoft Defender SmartScreen shows a warning. An unsigned file starts building reputation from zero with every new version, so the same warning appears again after each update.

Windows install steps

  • 1. Download: get the MSI from the home page or the releases page.
  • 2. Get past the browser warning: if Microsoft Edge blocks the download, open the downloads list, open the … (More actions) menu next to the file, and choose Keep, Show more and then Keep anyway. Chrome may warn that the file isn't commonly downloaded; you can still keep it from the downloads list.
  • 3. Check SHA-256: compare it with the published value as described in Verify the download.
  • 4. Get past SmartScreen: run the file. When "Windows protected your PC" appears, click More info, then Run anyway.
  • 5. Finish: follow the installer to finish.

The portable EXE shows the same SmartScreen warning and is opened the same way.

PCs with Smart App Control

When Smart App Control on Windows 11 is On, the unsigned Kitedesk app is blocked until it earns reputation in Microsoft's cloud service, and there is no way to allow a single app. To check its state, open the Windows Security app from the Start menu and go to App & browser control > Smart App Control.

  • On: the current public build may not run. Rather than turning the protection off, please use another PC.
  • Evaluation: does not block for now, but Windows may switch it to On later.
  • Off: Smart App Control does not block Kitedesk.

We don't recommend turning Smart App Control off. Microsoft: Smart App Control FAQ

Windows troubleshooting

  • There is no Run anyway button: PCs managed by a company or school can block unsigned apps by policy. Ask your administrator.
  • The warning comes back after every update: unsigned files restart their reputation with each version. Check the SHA-256 of the new version and run it the same way.
  • Your antivirus warns: see If problems continue.

macOS

One DMG file (kitedesk-<version>.dmg) installs on both Apple silicon (M1 and later) and Intel Macs. The app is not notarized by Apple yet, so macOS may block it the first time you open it.

  • Development testing was done on an Apple silicon Mac running macOS 26 Tahoe.
  • macOS 27 Golden Gate (released 2026-09-14) installs only on Apple silicon Macs; macOS 26 is the last release for Intel Macs.
  • Kitedesk has not been checked yet on macOS 15 Sequoia, macOS 27 or Intel Macs. The app declares macOS 10.15 as its minimum, but that has not been verified. If you try it, please tell us how it went.

macOS install steps

  • 1. Download: get the DMG and check its SHA-256.
  • 2. Move to Applications: open the DMG and drag Kitedesk into the Applications folder.
  • 3. Open: open Kitedesk from the Applications folder. If a block message appears, follow "Allow the first launch" below.
  • 4. Grant permissions: follow "Grant macOS permissions" below.

Allow the first launch

macOS 15 Sequoia and later (including 26 Tahoe and 27 Golden Gate): since macOS 15 you can no longer Control-click an app in Finder to get past Gatekeeper. Allow it in System Settings instead.

  • 1. Open Kitedesk once so that the block message appears, then close the message.
  • 2. Choose Apple menu > System Settings > Privacy & Security, go to the Security section and click Open Anyway. The button is available for about an hour after you try to open the app; if you don't see it, start again from step 1.
  • 3. Enter your login password, then click OK. Kitedesk is then saved as an exception and opens normally. After you replace it with a new version, you may need to repeat these steps the first time you open it.

macOS 14 Sonoma and earlier: in Finder, Control-click Kitedesk, choose Open, then click Open in the dialog. The System Settings method above also works. For details, see Apple: Open a Mac app from an unknown developer.

Grant macOS permissions

If a permission is still missing, Kitedesk's home screen shows a Permissions card for it, one at a time. Click Configure on the card, or go to Apple menu > System Settings > Privacy & Security and turn on Kitedesk under the item.

  • To let other devices control this Mac: turn on Screen & System Audio Recording and Accessibility. The app's card calls the first one "Screen Recording".
  • To control other devices with this Mac's keyboard: turn on Input Monitoring.
  • Start at boot (optional): if the app's home screen shows the "For starting on boot, you need to install system service." card, click Install only if you want Kitedesk to start automatically at boot.

If macOS asks you to restart the app after you grant a permission, do so. Apple guides: Screen & System Audio Recording, Accessibility, Input Monitoring

Permission problems after an update

The macOS app uses an ad-hoc signature rather than an Apple Developer ID, so after you install a new version macOS may treat it as a different app. The permissions can then look enabled in System Settings while the screen doesn't arrive or input doesn't work.

  • 1. In System Settings > Privacy & Security, turn Kitedesk off and on again under each affected item (Screen & System Audio Recording, Accessibility, Input Monitoring).
  • 2. If that doesn't help, select Kitedesk in the list, remove it with the − button, then open the app again and grant the permission anew.
  • 3. Quit Kitedesk completely and open it again.

Since macOS 15, a prompt asking whether to keep allowing screen recording may appear from time to time (since macOS 15.1 it appears less often for apps you use regularly). Keep allowing it to continue using Kitedesk.

Linux

The Linux packages are for x86_64 (64-bit PCs); no ARM build is published. The deb, rpm, AppImage and tar.gz packages all need glibc 2.39 or later.

  • Distributions that meet the glibc requirement (examples): Ubuntu 24.04 or later, Debian 13 or later, Linux Mint 22 or later, Fedora 40 or later, RHEL 10 family
  • Distributions that can't run it (examples): Ubuntu 22.04, Debian 12, RHEL 9 family. Their glibc is older than 2.39, so Kitedesk won't run. The deb package does not list a glibc version as an install requirement, so it may still install on these systems; check your version before installing.

Run the command below in a terminal; the end of the first line shows your glibc version (for example 2.39).

ldd --version

Pick the file for your distribution:

  • Ubuntu, Debian, Linux Mint: .deb
  • Fedora: .rpm (see the Fedora 45 note below)
  • Other distributions: .AppImage
  • Advanced users: .tar.gz
  • Flatpak (.flatpak): an experimental file that has not been confirmed to run, so it is not recommended for now. It has also not been confirmed as an alternative for older distributions such as Ubuntu 22.04 or Debian 12.

The rpm, AppImage, tar.gz and Flatpak files have only been checked for their contents; installing and running them on each distribution has not been tested yet. If you try one, please tell us how it went.

Install the deb (Ubuntu, Debian, Mint)

  • 1. Download kitedesk-<version>-x86_64.deb and check its SHA-256.
  • 2. In a terminal, go to the folder where you saved it (usually ~/Downloads) and install it with apt. Don't use dpkg -i, which cannot install the required dependencies.
sudo apt install ./kitedesk-*-x86_64.deb
  • 3. Start Kitedesk from your applications menu.

Install the rpm (Fedora)

On Fedora 43 and 44, install it with:

sudo dnf install ./kitedesk-*-x86_64.rpm
  • Fedora 45 and later: starting with Fedora 45, rpm refuses unsigned packages by default (Fedora change page). The published rpm is not signed yet, so installation may fail. We don't recommend options that skip signature checking. You can try the AppImage or tar.gz instead, although they have not been checked on Fedora.
  • openSUSE and others: the rpm uses Fedora-style package names, so its dependencies may not resolve (not checked). The AppImage is recommended.
  • RHEL family: RHEL 10 meets the glibc requirement but has not been checked; RHEL 9 cannot run Kitedesk.
  • Service: the rpm also enables and starts a system service when installed.
  • SELinux: on Fedora with SELinux enforcing, Kitedesk's home screen may show a warning card saying SELinux may prevent it from working properly as the controlled side. We don't recommend turning SELinux off.

Run the AppImage

  • 1. Download kitedesk-<version>-x86_64.AppImage and check its SHA-256.
  • 2. Make it executable and run it.
chmod +x kitedesk-*-x86_64.AppImage
./kitedesk-*-x86_64.AppImage
  • 3. If you see an error about loading libfuse.so.2 or "AppImages require FUSE to run", install the FUSE 2 library for your distribution, then run it again. The first line is for Ubuntu 24.04 or later and Debian 13, the second for Fedora (running the AppImage on Fedora has not been checked yet).
sudo apt install libfuse2t64
sudo dnf install fuse-libs

To run it without installing the library, add --appimage-extract-and-run. This unpacks the app every time it starts, so it is slower. AppImage documentation

Run the tar.gz (advanced)

The tar.gz runs from its own folder without installing. It needs system libraries such as GTK 3, GStreamer, PulseAudio, PAM and libXtst to be installed already, and glibc 2.39 or later. It does not register a system service.

tar -xzf kitedesk-*-x86_64.tar.gz
cd kitedesk-*-x86_64/
./kitedesk

The ./kitedesk launcher sets the path to the bundled libraries and starts the app with X11 (GDK_BACKEND=x11).

Notes for a controlled Linux PC

  • Wayland: Wayland support is experimental. When the PC is being controlled, a system dialog asks you to allow screen sharing and remote input. Use an X11 session if you need unattended access. The Wayland login screen is not supported.
  • Check your session: run echo $XDG_SESSION_TYPE in a terminal; it prints x11 or wayland.
  • SELinux: see the SELinux item under Install the rpm (Fedora).

Android

The Kitedesk Android app is not in an app store, so you install the APK file directly.

There is no build for x86 devices. The app declares Android 6.0 as its minimum, but older Android versions have not been checked yet.

Android install steps

  • 1. Download: download the APK in your phone's browser from a link above or from the releases page.
  • 2. Open: when the download finishes, open the APK from the notification or your files app.
  • 3. Allow installs: when Android says it can't install unknown apps from this source, tap Settings, allow installs for the app you opened the APK with (your browser or file manager), and go back. Since Android 8, this permission is given to each app separately.
  • 4. Install: tap Install. If installation is blocked, see "When installation is blocked" below.
  • 5. Turn the permission off again: after installing, we recommend turning off the permission you allowed in step 3.

When installation is blocked

Samsung Galaxy Auto Blocker: when Samsung's Auto Blocker is on, APKs from sources other than the Play Store and Galaxy Store are blocked. It is on by default on devices released with One UI 6.1.1 or later; devices updated from an earlier version keep their previous setting.

  • 1. Turn it off temporarily in Settings > Security and privacy > Auto Blocker.
  • 2. Install Kitedesk.
  • 3. Turn Auto Blocker back on right away.
  • When updating: while Auto Blocker is on, updates to apps installed from outside the stores are blocked too, so you need to repeat these steps for each new APK. Samsung: Auto Blocker

Google Play Protect: Play Protect may show a dialog before installation.

  • App scan recommended: choose to scan the app, and install it after the scan finishes.
  • App blocked to protect your device: Play Protect's enhanced fraud protection (in Korea since 2025-09-04) blocks apps downloaded through a web browser, messaging app or file manager when they request sensitive permissions such as Accessibility, and this dialog has no button to continue. Kitedesk uses the Accessibility permission for remote input, so it falls into this group (we have not yet confirmed whether it is actually blocked on devices in Korea). If you see this dialog, you currently can't install Kitedesk on that device through the browser. If you have a computer, see "Install from a computer (advanced)" below.

Google recommends keeping Play Protect on at all times and does not document that turning off scanning lifts this block, so we don't ask you to turn Play Protect off.

Install from a computer (advanced)

Installing over USB with ADB doesn't go through a browser or file manager. Turn on USB debugging in your phone's developer options, install the Android platform tools (adb) on your computer, and run this in the folder that holds the APK (use the file name of the version you downloaded):

adb install kitedesk-1.4.13-1-aarch64.apk
  • After installing: turn USB debugging off again.
  • Check the signature (optional): the 1.4.13-1 APK's signing certificate is CN=Kitedesk Release, and its SHA-256 fingerprint is F2:98:3A:B6:19:53:BF:1A:C2:29:18:DE:88:11:D0:E8:BF:FD:41:80:E8:AA:F7:70:56:11:12:CC:35:5B:83:62. You can check it with apksigner verify --print-certs; depending on the tool, it may be shown in lower case without colons.

Using a phone as the controlled side (not confirmed yet)

Being controlled as an Android phone or tablet has not been confirmed on 1.4.13-1. In particular, whether screen sharing starts properly on Android 14 and later has not been checked yet, so this guide does not give setup steps for the controlled side for now. The steps will be added here once it is confirmed.

  • Remote-input permission: before remote-input accessibility is enabled, the Kitedesk Android app explains the purpose, the data involved and how to turn it off, and asks for consent. If a stranger asks you by phone or message to turn this permission on, don't.
  • Secure screens: the Kitedesk Android app has no feature that bypasses Android secure screens that block capture (FLAG_SECURE) or the lock screen.
  • Storage: 1.4.13-1 does not request all-files access. To send files from your phone, use Share → Kitedesk in your gallery or file app.
  • Beta testers: if you have tried the phone as the controlled side, send the device model, Android version and what happened through the feedback channel on the beta page (Korean).

Known Android limits

  • Advanced Protection: on Android 16 and later, devices with Advanced Protection turned on block installing apps from unknown sources, so the Kitedesk APK can't be installed.
  • Developer verification: Google's Android developer verification does not yet apply to apps installed directly (sideloaded). Google plans to extend it worldwide from 2027.
  • App stores: Kitedesk is not on Google Play.

iOS

The iOS app is in preparation. No iPhone or iPad build is published.

After the first launch

  • After installation, Kitedesk registers with its default connection server automatically; there is no server address or key to enter. See the user guide (in Korean) for how to connect.
  • Check the ID to give the other person on the home screen. The ID shown in the desktop app's Setup Tour (942 815 304) is a sample value, not your device's ID.
  • When you sign in and have not set your own server, Use Kitedesk Relay is on by default, so remote sessions you start from this device are routed through the Kitedesk relay. You can turn it off with that one switch in Settings > Network, and the choice is kept on this device when you sign in again.

Updates

Kitedesk checks the official release channel when it starts and re-checks periodically while it stays open, showing a card on desktop or a banner on mobile when a new version is available. In 1.4.13-1 an app left open can take close to 12 hours to notice a new version, so if a new version is out and you see no notice, quit the app completely and open it again. To update, download the new file and install it with the same steps on this page.

  • Windows: the SmartScreen warning may appear again for each new version.
  • macOS: the block message may appear again the first time you open it; if permissions look enabled but don't work, see Permission problems after an update.
  • Linux: for the deb, install the new file with sudo apt install ./kitedesk-*-x86_64.deb.
  • Android: on Galaxy devices with Auto Blocker on, you need to turn it off briefly for each install.

If problems continue

  • Your antivirus warns: antivirus software may flag remote-control apps as remote access tools; we have not checked whether this happens with Kitedesk files. Compare the file's SHA-256 with the published value, then tell us which antivirus flagged it and under what name, through the feedback channel on the beta page (in Korean).
  • Connection, input or screen problems: see the FAQ and the help page (in Korean).

Kitedesk is in beta: features and behavior may change without notice, and there may be bugs. During the beta, the default connection server has no availability, speed or capacity guarantee (no SLA). Kitedesk is licensed under the GNU AGPL-3.0-only; the complete corresponding source for each release is available on its release page.

Kitedesk is an independent fork of RustDesk. It is not affiliated with, endorsed by, or sponsored by the RustDesk project.