KDE Connect
KDE Connect 26.04.3 is an open-source cross-device companion that sends files and links, syncs selected notifications and clipboard text, controls media and pairs computers with Android or iOS devices.
What KDE Connect provides
KDE Connect joins a computer and mobile device through explicit pairing. It can send files and links, show battery status, mirror selected notifications, share text, control media and use a phone as a touchpad or presentation remote. It is not cloud backup, a device-management platform or an unattended public remote-control service.
Version and platform boundaries
Desktop 26.04.3 is paired with platform-specific Linux, Windows and macOS builds, while Android and iOS have their own application release cycles. Version numbers do not need to match across platforms, and plugin availability follows each platform's permission model.
Plugins, permissions and network
Notifications, clipboard, SMS, file browsing, remote input and custom commands are separate capabilities. Discovery normally requires devices to communicate directly on a trusted local network; guest isolation, VPNs and firewalls can interfere. A manual IP solves a routing discovery issue but does not replace bidirectional pairing confirmation.
Maintenance note
Review date: 2026-08-06. The page covers stable desktop pairing, manual IP behavior, Bluetooth and Android clipboard limits, non-Plasma desktop differences and license boundaries.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave KDE Connect to this cloud drive
Baidu Netdisk
Save KDE Connect to this cloud drive
KDE Connect 26.04.3 installation, pairing and permission guide
Install the matching components on a computer and phone, pair them on a trusted network, then enable file sending and battery checks before adding notifications, clipboard or remote input.
Before you start
- Put the computer and phone on a trusted local network and remove guest isolation that blocks device-to-device traffic; use a controlled private network across subnets.
- Record the desktop and mobile versions separately, and decide which notifications, folders, clipboard actions and remote controls are actually needed.
- Clear passwords, tokens and private content from the clipboard before enabling clipboard sharing.
Installation steps
- 01
Install the matching components
Use the package for the desktop operating system and the Android or iOS app for the phone, checking architecture and release channel on each platform.
- 02
Allow necessary local-network traffic
Permit discovery and connections only on a private network and grant the mobile local-network permission; do not expose the service port directly to the public internet.
- 03
Confirm pairing in both directions
Send a pairing request, check the device name on the other screen and accept only a request you recognize; then review the enabled plugin list.
Quick start
- 01
Test a harmless file and link
Send a small file without sensitive information in both directions, confirm the receive folder and filename, and check storage before transferring a larger item.
- 02
Enable notifications and clipboard selectively
Mirror only the application notifications you need and test ordinary text. Newer Android versions may require an explicit send action because of background clipboard limits.
- 03
Configure remote input last
Test the touchpad, media or presentation controls, and make custom commands read-only or non-destructive before considering broader automation.
Usage tips
- The desktop program and mobile application have different plugins, permissions and release schedules; verify the exact platform pair in use.
- VPNs, enterprise Wi-Fi, guest isolation and VLAN boundaries can break automatic discovery. Manual IP addressing does not remove the need for pairing.
- Clipboard, SMS, accessibility and file permissions can expose sensitive data. Enable only the plugins needed for the current workflow.
Troubleshooting and uninstall
Why can I send files but not notifications or clipboard text?
Check the corresponding plugin on both devices, mobile permissions, background limits and battery optimization. Test one capability at a time rather than granting every permission.
Why did devices go offline after changing the router?
Confirm that both devices have reachable addresses, remove stale manual IP settings and check that the firewall network profile is private. Re-pair when the old device record can no longer be verified.
- Unpair and revoke plugin permissionsUnpair the devices, disable notification, file, SMS, accessibility and local-network permissions, and remove custom commands that are no longer needed.
- Remove components and firewall rulesUninstall the app or distribution package and delete only the startup entries and firewall rules created for KDE Connect; confirm that the old device is no longer discoverable.
Frequently asked questions
Does KDE Connect require KDE Plasma?
No. Desktop components can run on other Linux desktops, and Windows and macOS have builds, although tray integration and file browsing may differ outside Plasma.
Why are paired devices invisible on the same Wi-Fi?
Guest isolation, firewall rules, VPN routing or different subnets can block discovery. Confirm direct connectivity first, then use a manual IP in the app while keeping the network private.
Does KDE Connect automatically copy every notification and clipboard item?
Only enabled plugins and granted system permissions can do so. Newer Android releases restrict background clipboard access, so use an explicit send action and avoid keeping credentials in a shared clipboard.