KDE Connect on Windows: What It Does, How to Set It Up, and the Alternatives

KDE Connect comes from the Linux world, it is genuinely free and open source, and there is a Windows build. So the fair question is whether it is worth installing on a Windows PC, what you actually get, and what to do when it sits there finding nothing. All three are answered below, starting with what it does once the phone and the PC can see each other.

KDE Connect links your phone to a Windows PC over your own Wi-Fi

KDE Connect is not a file-sending app with extras bolted on. It is a link between two devices, and once a phone and a PC are paired you get all of this at once:

• KDE Connect is free open source software from the KDE community, with no account and no paid tier. KDE is the group behind the Plasma desktop on Linux, and they publish the phone apps and the Windows app themselves. There is no trial and no upsell waiting.
• KDE Connect sends files in both directions between a phone and a Windows PC. Share a photo or a document from the phone and it arrives in a folder on the PC, and you can send files back to the phone the same way.
• KDE Connect shares copied text between the paired phone and the PC, so something copied on one can be pasted on the other. A link, an address or a one-time code crosses without you typing it out.
• KDE Connect shows your phone's notifications on the Windows desktop as they arrive. A message pops up on the PC while the phone stays in your bag, and on Android you can answer some of them from the desktop.
• KDE Connect turns the phone into a trackpad and keyboard for the Windows PC. That is genuinely useful when the PC is across the room on a TV, and the same feature gives you next and previous buttons for a presentation.
• KDE Connect can trigger commands on the Windows PC from the phone, once you have defined them on the PC. The command has to be written on the computer first, so the phone can only fire off things you have already allowed.
• KDE Connect also handles media controls, the phone's battery level and ringing a phone you have lost. Pause what the PC is playing from across the room, see the phone's charge on the desktop, and make a misplaced phone ring from your desk.

That list is why people put up with the setup. No single-purpose file sender does most of it.

Camera to Clipboard puts a phone photo on the Windows clipboard

If the thing you actually want from a phone to PC link is a photo out of your phone and into a document, that is the one job KDE Connect leaves half done. It sends you a file. What you wanted was a paste.

• A photo sent from the phone with Camera to Clipboard lands on the Windows clipboard, ready to paste. Press Ctrl + V in the document, the email or the chat. There is no folder to open and no file to attach afterwards.
• Camera to Clipboard sends the photo straight from the phone to the PC over your local Wi-Fi, with nothing uploaded. It works on a network with no internet and on a phone's hotspot, in the same device-to-device way KDE Connect does. The Wi-Fi transfer guide runs through the other ways of doing this over a local network.
• Camera to Clipboard pairs the phone and the PC by scanning a QR code once, which takes about ten seconds. There is no firewall rule to write, because the desktop app asks Windows for what it needs when you install it.
• Camera to Clipboard sends one photo or a whole batch, freshly taken or picked from the camera roll. Videos and scanned documents go across the same way.
• Camera to Clipboard does one job rather than linking everything about the phone to the PC. It does not mirror your notifications and it is not a remote control, so if those are what you came for then KDE Connect is the better answer.

1. Install Camera to Clipboard on the phone and the Windows app on the PC.
2. Pair once by scanning a QR code, about ten seconds.
3. Take or pick a photo on the phone and send it.
4. Press Ctrl + V on the PC.

Free to download and try on both ends.

KDE Connect pairs with a phone once you install it at both ends

Setup is one install on each device and one pairing request. The whole thing takes a few minutes when discovery behaves:

1. Install KDE Connect on the Windows PC, from the Microsoft Store or from the download on the project's own site.
2. Install the phone app: Google Play or F-Droid on Android, the App Store on an iPhone.
3. Put both devices on the same Wi-Fi network, not one on Wi-Fi and the other on mobile data.
4. Open the app on the phone. The PC should appear in the device list. Tap it and request pairing.
5. Accept the pairing request on the Windows PC. The two stay paired until you unpair them.

Four things about pairing are worth knowing before you start, because they explain most of what looks like a fault:

• KDE Connect only pairs devices that can reach each other on the same local network, so a phone on mobile data will never list your PC. There is no server in the middle to introduce them, which is the whole point of the design and also its one hard requirement.
• Pairing a phone and a PC in KDE Connect is a one-time step, and the two find each other again on their own. Come home, join the Wi-Fi, and the link is back with nothing to confirm.
• KDE Connect encrypts what it sends between the paired phone and PC, and nothing you send passes through a company's server. The two devices swap certificates when you pair them and then talk to each other directly, so a file goes from the phone to the PC and nowhere else.
• Every KDE Connect feature can be switched off on its own in the app's plugin list. If you want file transfer but would rather your notifications stayed on the phone, turn that one off at either end and keep the rest.

Windows Firewall blocking KDE Connect is why no device appears

This is the failure almost everyone hits, and it looks like nothing at all: the app opens, the device list stays empty, and neither end shows an error. Here is what is happening and what to allow.

• KDE Connect finds devices by announcing itself across the local network, and Windows Firewall blocks that announcement by default. The phone and the PC are both running and both on the right Wi-Fi, and neither lists the other. Nothing is broken. The announcement simply never arrives.
• KDE Connect needs UDP and TCP traffic on ports 1714 to 1764 to reach the Windows PC. The UDP part is the announcement that makes the two devices find each other, and the TCP part carries the pairing and everything you send afterwards. Block either half and the app looks dead.
• Allowing the KDE Connect program through Windows Firewall is better than opening ports 1714 to 1764 by hand. A rule attached to the app covers whichever port it uses and stops mattering the day you uninstall it, where a bare port rule stays behind and applies to anything else that starts listening there.
• The firewall permission for KDE Connect has to cover private networks, and that is the box people miss. Windows keeps separate permissions for private and public networks, so a rule that only covers public networks does nothing at all on your home Wi-Fi.
• Antivirus suites with their own firewall block KDE Connect even after Windows Firewall is allowing it. Those products replace or sit in front of the Windows rules, so the app has to be allowed a second time in that software.
• KDE Connect usually needs restarting on both the phone and the PC after a firewall change. Discovery announcements go out when the app starts, so give it a fresh start rather than waiting to see whether the device appears on its own.

Marking the network Private lets KDE Connect find your phone

The firewall rule is only half of it. Windows also decides, per network, whether your PC is allowed to be visible to other devices at all, and the default answer is no.

• Windows treats every network you join as either Public or Private, and a network marked Public hides your PC from KDE Connect on the phone. Public is meant for cafes and airports, so it switches off exactly the local discovery that KDE Connect depends on.
• Windows asks whether a network should be discoverable the first time you join it, and the cautious answer is the one that breaks KDE Connect. Saying no marks the connection Public, most people say no, and nothing later reminds you of it. You can change the setting for that connection afterwards in the network settings.
• A Private network setting in Windows applies to that one connection, so making your home Wi-Fi private does not expose the PC anywhere else. Join a hotel network next week and it arrives as Public on its own, with your home setting untouched.
• An office or campus network usually stays Public and blocks KDE Connect whatever you change on the PC. Managed networks keep devices apart on purpose, and that is not something you can undo from the Windows side.
• Connecting the Windows PC to the phone's own hotspot gets KDE Connect working when the Wi-Fi network you are on blocks local discovery. The two devices are then alone on a small network with nothing in between to filter them.

A VPN or a guest network hides the phone from KDE Connect

If the firewall is open and the network is Private and the device list is still empty, the network itself is keeping the two apart. Four causes account for nearly all of it:

• A VPN running on either the phone or the Windows PC sends traffic away from your local network and stops KDE Connect pairing. Turn it off at both ends to pair, then switch it back on and test, because some VPN apps have a setting that lets local network traffic through.
• A guest Wi-Fi network deliberately stops devices talking to each other, so KDE Connect cannot pair a phone and a PC across it. Move both onto the main network. Guest networks exist precisely to prevent what KDE Connect is trying to do.
• Some routers separate wireless devices from each other, which stops KDE Connect finding a phone that is plainly on the same Wi-Fi. The setting is usually called client isolation or AP isolation. Both devices have internet and still cannot see one another, which is what makes it so confusing.
• A Windows PC on Ethernet and a phone on Wi-Fi normally still work with KDE Connect, as long as both sit behind the same router. In most homes they are on one network regardless of how they joined it. Where an extender or a mesh unit creates a second network, they will not see each other.

KDE Connect really does share the clipboard, and it shares text

Clipboard sharing is one of the best reasons to install KDE Connect, and it deserves a straight description rather than a sales one. Here is exactly what crosses and what does not.

• KDE Connect genuinely shares the clipboard between a paired phone and a Windows PC, and it works well. Copy a link, an address or a login code on one device and paste it on the other. No other free tool on this page does that at all.
• KDE Connect's clipboard sharing is built around text rather than images. A copied URL crosses to the other device. A photo is not handed to the Windows clipboard as an image you can paste into a document.
• Android restricts which apps may read the clipboard in the background, so sharing copied text from an Android phone is often a manual send rather than something that happens by itself. That limit is Android's own, not a fault in KDE Connect, and the app gives you a send action to work around it.
• A photo sent from the phone with KDE Connect arrives on Windows as a file in a folder, with a notification. From there you open the folder and attach it or drag it in. That is exactly right when you are keeping the photo, and it is a detour when the photo was only ever going into an email.
• KDE Connect shares the clipboard only between devices you have deliberately paired. Another phone on the same Wi-Fi gets nothing, because pairing is what authorises the link in the first place.

So the distinction worth holding on to is not that one tool has a clipboard feature and the other does not. It is text against images, and which of the two you need.

KDE Connect on Android does more than the iPhone version does

Which phone you have changes what you get, and the gap is wider than most download pages admit. It is worth knowing before you set aside an evening for it.

• The KDE Connect Android app carries the full feature set, including notification mirroring, clipboard sharing, remote input and file transfer. Android allows an app to do all of that, which is why nearly every screenshot of KDE Connect you will find is the Android one.
• The KDE Connect iPhone app is free and real, and it does noticeably less than the Android app. File sharing, remote input and the presentation remote are there. Mirroring iPhone notifications to a PC is not, because Apple does not let another app read them.
• An iPhone limits what KDE Connect may do while it is not the app on screen, so the link to the PC drops when you switch away. In practice you often have to open KDE Connect on the iPhone before the Windows PC will list it, which makes it far less of a background helper than it is on Android.
• Nothing about KDE Connect needs Linux on the computer, despite where the project comes from. The Windows build is a supported part of the project rather than a community side effort, and there is a macOS build as well.

The Windows build of KDE Connect is rougher than the Linux one

This is the part a download page will not tell you, and it is not a criticism of a free project. It is simply where the effort has gone.

• KDE Connect started as a Linux project and the Windows build came later, so Windows tends to get the polish second. Nothing is deliberately held back. There are just far more people running it on Linux and reporting what breaks there.
• Device discovery is the part of KDE Connect that most often fails on Windows and rarely fails on Linux. Many Linux desktops ship with no firewall switched on, so the same app finds the phone straight away there, while on Windows somebody has to write it a rule first.
• Features in KDE Connect that lean on the Plasma desktop are thinner or missing on Windows. Browsing the phone's storage in the file manager and the desktop widgets are Plasma pieces, and the Windows app has no equal for all of them.
• Setting KDE Connect up on Windows asks more of you than a commercial app would. Nobody is paid to smooth over the first run. What you get for the extra ten minutes is software with no account, no advertising and no cloud service in the middle.
• KDE Connect is worth installing on Windows if you want the phone and the PC linked rather than files moved. Notifications on the desktop and the phone as a remote control are things a file-sending tool does not attempt at all.

KDE Connect does more than its alternatives and asks more of you

People searching for a KDE Connect alternative usually want one of two things: the same idea with less setting up, or the one feature KDE Connect stops short of. Four tools cover both, and each gives something up.

• LocalSend is the closest free open source alternative to KDE Connect for moving files between a phone and a PC. It installs on Windows, macOS, Linux, Android and iPhone, finds other copies of itself on the network, and needs no account and no pairing. It does not do notifications, clipboard or remote input.
• PairDrop sends a file between a phone and a Windows PC through the browser, with nothing installed at either end. Open the same page on both devices on one network and drag the file across. That makes it the easiest thing here to try, and there is nothing to keep once you close the tab. The Snapdrop and PairDrop guide covers it properly.
• Microsoft Phone Link is Windows' own version of the KDE Connect idea and mirrors an Android camera roll onto the PC. It handles notifications and messages much as KDE Connect does, needs a Microsoft account, and its photo panel has never worked with an iPhone. The Android to PC guide covers what it does with a camera roll.
• Camera to Clipboard covers the one thing KDE Connect stops short of, an image arriving on the Windows clipboard. It is not a phone link, so it competes with KDE Connect on exactly one task and leaves the rest to it.

KDE Connect suits the whole phone link, not a photo you need now

All five tools above work. Which one you want depends entirely on what you are trying to get from your phone to your PC, so find your case here.

• Install KDE Connect on Windows if you want phone notifications on the desktop and files moving both ways. Nothing else free covers that whole span, and it is worth the firewall rule to get it.
• Install KDE Connect if you specifically want free open source software with no company behind the link. There is no account, no advertising and no server holding your files, and the code is public for anyone to read.
• Use LocalSend rather than KDE Connect if all you want is to send a file between a phone and a Windows PC. It is the same open-source spirit with a fraction of the setup, because there is no pairing step and no plugin list. The phone to PC transfer apps roundup compares the wider field.
• Use Camera to Clipboard when the photo on your phone is going straight into a document, an email or a chat on the PC. It ends in a paste rather than a file, which removes the step every other tool here leaves you with.
• Expect no phone-to-PC transfer tool, KDE Connect included, to work on a managed office or campus network. Those networks keep devices from reaching each other by design, and a phone hotspot is the usual way around it.

Common questions about KDE Connect on Windows

Does KDE Connect work on Windows?
Yes. KDE Connect has an official Windows build from the KDE project and it pairs with the Android or iPhone app over your local network. It is a Linux-first project, so the Windows version is less polished than the Linux one, and device discovery is the part that most often needs help. Windows Firewall is almost always the reason it finds nothing.

Why does KDE Connect not find my phone on Windows?
Almost always Windows Firewall, the network profile, or both together. KDE Connect needs UDP and TCP traffic on ports 1714 to 1764, and Windows switches off local device discovery on any connection marked Public. Allow KDE Connect through the firewall for private networks, set your Wi-Fi connection to Private, and check that no VPN is running on either device.

Does KDE Connect share the clipboard between a phone and a PC?
Yes, for text. Copy text on one paired device and it is available to paste on the other, and that is one of the main reasons people install it. It does not put an image on the computer's clipboard, so a photo sent from the phone arrives as a file in a folder rather than as something you can paste straight into a document.

Is KDE Connect free?
Yes. KDE Connect is free and open source software from the KDE community, with no paid tier, no account to create and no advertising. The Windows app, the Android app and the iPhone app are all free, and the code is public.