Try transferring a couple of files between your laptop and mobile phone using the same Wi-Fi network and see that No device appears, and the progress bar doesn't move. It's one of those minor technological annoyances that can drive anyone crazy. LocalSend, Warpinator, or even web-based alternatives like PairDrop promise fast transfers over the local network without touching the cloud, but in practice, many users end up struggling with firewalls, router settings, or Android permissions.
In this scenario, compare calmly. LocalSend vs Warpinator It makes perfect sense: it's not just about seeing which one is "prettiest", but about understanding which platforms they work best on, what typical problems they have (Flatpak, access point isolation, local network permissions, PWA on Android…) and what settings you need to check so you can stop relying on luck when you want to send photos, videos or entire folders between your devices.
What is LocalSend and why do so many people prefer it?
LocalSend is an application free, open source and cross-platform Designed to send files and short messages between devices connected to the same local network, without using the internet or external servers. There's no cloud, no accounts, no intermediaries: everything travels directly from one device to another within your home or office LAN.
On a technical level, LocalSend exposes a Proprietary REST API that works over HTTPSEach device dynamically generates its own TLS/SSL certificate, so communication is encrypted without relying on any public certificate authority. This means your files never leave your network and are transmitted encrypted, making it extremely difficult for anyone to eavesdrop on the traffic, even if they're connected to the same Wi-Fi network.
The philosophy of the project is to offer a very direct experience: you open the app on your mobile phone, laptop, desktop PC or Mac, wait a few seconds for it to load automatically discover on the local network From there, you can send files or messages with just a couple of taps or clicks. There's no registration, no login required, and no artificial file size limits beyond what your network and hardware can handle.
This approach is a great fit for those coming from heavier solutions, like sync suites or cloud-centric workflows, who just want something that, literally, “open it and it works” within its own network without giving away data to third parties or depending on external services.
Platforms compatible with LocalSend and basic requirements
One of LocalSend's strengths is the wide range of operating systems it supports, making it especially interesting for homes and offices where very different mobile phones and computers coexist. The idea is to offer a consistent experience across Android, iOS, Windows, macOS, and Linux.
On Android, LocalSend works from version 5.0 onwards, and is available for download from both official stores and alternative repositories. This allows for reuse. older phones and tablets that no longer receive updatesThis is very practical if you use them as secondary devices for multimedia or backups.
On iOS, compatibility begins with iOS 12.0, integrating seamlessly into Apple's existing ecosystem without any extra configuration. Thanks to this, an iPhone or iPad can participate in the same local file-sharing flow as your PC or Android device, something that... Many cross-platform tools continue to stumble.
For macOS, the recommended starting point is macOS 11 Big Sur or later. However, some users with older Macs resort to solutions such as OpenCore Legacy Patcher to run recent versions, so they can share files on the local network with more modern Windows or Linux computers.
On Windows, official support begins with Windows 10, while the last known version that works on Windows 7 is 1.15.4. There are even community-maintained backports, allowing for the inclusion of PCs that have not yet upgraded to the latest versions provided the firewall rules are properly configured.
In Linux, there is no mandatory distribution, but there are certain dependencies that shouldn't be overlooked. Packages such as xdg-desktop-portal and its specific variants (xdg-desktop-portal-gtk for GNOME-like desktops or xdg-desktop-portal-kde for KDE Plasma) are essential for managing file selection dialogs, permissions, and notifications. Without them, it's relatively common for LocalSend to fail to open the file selection window or for notifications to not appear correctly.
LocalSend in daily use: installation, firewall and network configuration
On paper, setting up LocalSend is almost trivial: you install it on your mobile phone and laptop, both connected to the same Wi-Fi network, open the app, and in a few seconds they should be working. automatically detect and appear to each otherIn many simple home networks, this is exactly what happens... until an aggressive firewall or a poorly configured guest network comes into play.
One of the most common scenarios involves a Windows or Linux laptop and an Android phone where everything seems fine (same SSID, good Wi-Fi coverage, app working), but neither appears in the list of nearby devices. Sometimes they had even connected before and were saved as favorites, but suddenly they disappear. They cease to be detected for no apparent reason.That's where it's usually discovered that some change in the firewall or network type has blocked the port that the application needs.
According to the project's own documentation, LocalSend requires that the system allow incoming TCP and UDP traffic on port 53317In addition to outgoing TCP and UDP traffic to any destination port, if incoming traffic on that port is filtered or silently dropped, the machine becomes invisible to other LocalSend devices, even if it's connected to the same network and the application is open.
The usual solution involves creating explicit firewall rules to open port 53317, but it's important to do this carefully. Don't fall into the temptation of opening ports recklessly.Nor should you allow all incoming traffic on all interfaces "just in case," because that greatly increases the attack surface. It's best to limit this openness to your home or office network and only to the protocols and ports that the app actually needs.
The other major culprit when LocalSend behaves erratically is the router configuration. Many models, especially those provided by ISPs, include an option to “access point isolation” or AP isolationThis is very common in guest networks. When this setting is enabled, each Wi-Fi connected device can reach the router and even the internet, but cannot communicate with other devices on the same network.
On a network with AP isolation enabled, no local transfer application will work miracles: no matter how many ports you open in your laptop's firewall, the router will still be blocking access. preventing the mobile phone and the computer from seeing each otherThe LocalSend developers recommend ensuring that this feature is disabled on the network where you will be using the app, or moving your devices to an SSID where there is no client isolation.
Common LocalSend problems on Android and laptops (including Flatpak)
Among the user comments, there is a fairly common complaint: “No matter what I do, my Android device won’t communicate with my laptop.”People claim that it used to work, that they added both devices to favorites, and that one day the detection stopped working as if something had broken without explanation.
When LocalSend is installed as a Flatpak on Linux, another layer of complexity comes into play. The Flatpak format is designed to isolate applications from the system and the network, which is fantastic for security, but can lead to... network and firewall permissions more sensitive than normalIt's not uncommon for someone to start tampering with ingress and egress rules in the system's firewall, guided by threads that also warn of the risk of over-configuring, and ultimately back down out of caution.
If you recognize yourself in that profile (LocalSend in Flatpak on the Linux laptop or standard installation on Windows, and Android app on the same SSID), before throwing in the towel it's worth following a short basic checklistFirst, check that both devices are indeed on the same non-guest network and, if in doubt, find out the IP address of the devicesIt is more common than it seems for the laptop to be on the main Wi-Fi and the mobile phone on the guest network of the same router, which cancels peer discovery.
Then, check your router settings again to make sure that AP isolation or any similar client isolation option It's disabled on the network you're using with LocalSend. If it's enabled, you can temporarily disable it (if you understand the implications) or move the devices to another internal network where clients can see each other.
On your laptop, make sure the firewall allows incoming TCP and UDP connections on port 53317 and that outgoing connections aren't overly restricted. On Windows, LocalSend usually works much better when the network is marked as "Private" rather than "Public," as the system It considerably strengthens the firewall on public networksChanging the profile to private when appropriate usually unlocks listening on the required port without needing to perform any complicated procedures.
macOS and iOS have an extra layer of privacy in the form of permissions. “Local network” within Settings > PrivacyIf access to LocalSend was ever denied, device discovery and transfers will fail without a clear message within the app. Checking and enabling this permission usually saves a lot of time. network diagnostics on Mac.
In addition to connection problems, LocalSend acknowledges in its own documentation a performance issue in Android related to the component flutter-cavalry/saf_streamIn some models, this can result in quite slow transfer speeds, especially when handling large videos, full photo galleries, or mobile backups. In other words, you might be able to get your phone and PC to display perfectly, but if you're on a congested 2,4 GHz Wi-Fi network and your device is experiencing this issue, the actual speed will be much lower than expected unless you switch to a cleaner 5 GHz network.
Warpinator: how it works, its benefits, and common headaches
Warpinator is another tool Free and open source, created by the Linux Mint teamIt allows you to share files and entire directories over your local network. Originally focused on the Linux desktop, versions and ports for other platforms, including Android, have emerged over time, making it an interesting option for transferring data between your PC and mobile device at home.
One of Warpinator's biggest draws is the possibility of accept files automatically without asking for confirmation with each transfer. In a trusted environment (your personal computers at home, your laptop and your mobile phone, etc.) this is incredibly convenient: you drag an entire folder from the file explorer to the target in Warpinator and, after a while, you see the folder appear on the other device with the same structure.
The combination of dragging and dropping entire directories and automatic acceptance of transfers is something that Pure web applications hardly replicate Nowadays, for those who frequently copy folders of photos, documents, or projects between machines, eliminating the step of accepting file by file represents a significant time saving on a daily basis.
However, Warpinator has also gained a reputation for being "fussy." Some users bluntly describe it as a “headache” due to its device detection failuresConnections that sometimes work and sometimes don't, or transfers that freeze without clear messages. Sometimes a minor change in the network triggers a test session that ends with more questions than answers.
These frustrating experiences are precisely what lead part of the community to seek alternatives like LocalSend, hoping to find more consistent behavior in mixed environments where Linux, Windows, macOS and all kinds of mobile devices are connected to the same network.
Performance and speed: local network, 2,4 GHz vs 5 GHz and Ethernet cable
When comparing LocalSend and Warpinator, it's easy to focus on the interface or advanced features, but the reality is that Raw transfer speed depends much more on the local network than on the appA 5 GHz Wi-Fi network with good coverage and little interference can make a world of difference compared to a 2,4 GHz network saturated by neighbors' routers and all sorts of connected devices.
Whenever possible, it's worth connecting at least one end, usually the desktop PC or laptop, to the router using Ethernet cable and apply the router Wi-Fi trickA wired link eliminates the typical signal drops, micro-interference, and access point changes that affect Wi-Fi, and allows for a more stable data flow when moving several gigabytes between machines.
LocalSend, being built with Flutter to offer the same interface across many systems, introduces additional layers of abstraction compared to a native tool more closely tied to a single desktop environment. These layers greatly facilitate cross-platform maintenance, but in return, they can lead to... specific features per platform, such as the aforementioned saf_stream problem in Android which, in certain cases, acts as a bottleneck.
Warpinator, being more closely tied to traditional Linux desktop environments, tends to leverage the system's network stack very directly. When device discovery is working and the link remains stable, Warpinator can move complete directory trees very smoothlyespecially if at least one end is connected by cable to the router.
That said, neither is immune to the same limitations: congested Wi-Fi, router AP isolation, an overly aggressive firewall, or a poorly configured subnet will affect both LocalSend and Warpinator. Many of the "random crashes" that people attribute to the application actually originate from network details or operating system permissions that have not been reviewed.
Portable mode and advanced options in LocalSend
Beyond the basic use of opening and sending files, LocalSend incorporates a series of advanced features geared towards users who want better control where settings are stored and how the application startsThese are details that can make all the difference if you move between many teams or carry your tools on a USB drive.
One of these features is portable mode. To activate it, simply create a file called settings.json in the same folder as the executable from LocalSend. The file's contents can be empty; what matters is its existence, which tells the application to save and read the configuration in that file instead of scattering it across the operating system's standard configuration paths.
With this simple trick, you can carry LocalSend and your customized preferences on a USB drive and run it on different computers without leaving a trace. For those who maintain a portable “toolkit”This way of working is especially convenient.
Another interesting option is the ability to launch LocalSend hidden in the system tray or notification area. Since version 1.15.0, if the application is launched with the parameter -hidden (or -hidden)For example, from a shortcut in Windows, the app will start in the background, without showing its main window, but will be ready to receive files at any time.
In versions prior to 1.15.0, similar behavior existed by combining the system's autostart option with an internal "hidden startup" setting. In any case, these possibilities make it easier for LocalSend to be always available in the background on your PC without taking up desktop space, which is handy if you frequently receive files from your mobile or other devices.
Community, translations and development of LocalSend
LocalSend is not a static project, but an application that evolves quite frequently thanks to a very active community of users and developersNew versions usually bring bug fixes, interface improvements, and additional features born directly from feedback from those who use it daily.
The platform is used to translate the interface into different languages. WeblateThis system allows translators to coordinate their work without having to touch the source code. Through a web interface, text strings can be proposed, reviewed, and approved, maintaining language consistency and making it easy for non-technical users to contribute.
Those who prefer a more manual approach can clone the project repository and directly edit the translation files in the folder app/assets/i18nThere you'll find resources like _missing_translations_ .json o strings_ .i18n.jsonwhich contain the strings visible in the application. It is important to respect comments marked with @, as they are explanatory notes to provide context for translators and they don't need to be translated or modified.
On the development side, anyone who discovers a bug is encouraged to open an issue and, if possible, prepare a pull request with a clear description of the problem and the proposed solution. For more ambitious changes or new features, maintainers usually appreciate it if the idea is first raised in an issue. discuss its fit into the roadmap and prevent several people from working on the same thing at the same time without knowing it.
The project's contribution guide details the technical steps for compiling LocalSend from source code: installing Flutter (often using tools like fvm), preparing Rust, cloning the repository, and running flutter pub get to download dependencies and finally, Flutter Run to release a development build. This documentation significantly lowers the barrier to entry for anyone wanting to review the code, adjust behaviors, or add support for new platforms and distribution formats.
LocalSend vs Warpinator and the role of web solutions like PairDrop
Putting LocalSend and Warpinator side by side and declaring an outright winner doesn't make much sense. They both share the idea of Take advantage of the local network to move files privately, without going through the cloud.but they point to slightly different environments and priorities.
LocalSend shines when what you need is extensive multi-platform coverageAndroid, iOS, Windows, macOS, and Linux all share the same interface and use HTTPS encryption with certificates generated on each device. Because it doesn't rely on external servers, accounts, or centralized logs, it's very attractive in contexts where privacy and simplicity are more important than deep integration with a single desktop.
Warpinator, on the other hand, is especially interesting if your world revolves primarily around Linux desktops And you're used to moving entire folders between a small set of trusted devices. Automatic file acceptance, combined with the ability to drag and drop entire directories, greatly reduces friction in recurring data copying or project synchronization tasks between desktop computers and a well-integrated Android mobile device.
Meanwhile, browser-based alternatives such as PairDrop They're trying to fill another niche: sharing files occasionally without installing anything. On paper, the promise is attractive: you open a URL, pair the devices, and start sending files. In practice, especially on Android, things go awry. PWA integrations are often half-baked, and there are reports of users installing PairDrop as a PWA, opening it, pairing it with their PC, receiving a notification that a PDF has arrived, clicking "Download"... and the browser (for example, Firefox) It simply opens its homepage without saving any files..
These types of failures clearly illustrate the current limitations of web apps for tasks like bulk transfers without confirmation. Convenient features such as accept files automatically The ability to drag and drop entire folders and see them replicated exactly on the other device is very well done in native tools like Warpinator, but it is difficult to reliably reproduce in PWAs, especially on mobile devices where access to the file system and background activity are very restricted.
That's why it's not uncommon to find users who, after struggling with Warpinator and then encountering problems with LocalSend (especially in Android + Flatpak combinations), consider switching to other apps or tinkering with internal settings. In many cases, however, the deciding factor isn't the chosen tool, but the real-time network status and system security configuration: AP isolation enabled on the router, public network profiles on Windows, xdg-desktop-portal components missing on Linux, local network permissions disabled on Apple, etc.
A sensible strategy involves trying LocalSend, Warpinator, and, when appropriate, a web-based option like PairDrop, but doing so on your real network and with your own devices, following a short mental checklist: confirm they are using the same non-guest SSID, that AP isolation is disabled, that the specific ports for each tool are open sparingly in the firewall, that local network permissions are granted, and that, if you are going to move large files, Do you prioritize 5 GHz Wi-Fi or wired connection? compared to a saturated 2,4 GHz band. When that terrain is well prepared, the "luck" factor almost completely disappears, and you can evaluate each app based on its interface and features.
With a properly configured network, adjusted firewall rules, and aligned system permissions, both LocalSend and Warpinator can turn the "drama" of transferring files between mobile and laptop into a quick, predictable, and private routineWhile web options like PairDrop remain a good fallback for specific situations where installing software is not an option, don't expect the same reliability as well-tuned native applications.