LocalSend APK turns an Android phone and a computer on the same local network into a direct file-transfer pair. It works with Windows, macOS and Linux, needs no account, and does not upload your files to a cloud server. You still need both devices connected to the same Wi-Fi or local network.

The app is free and open source. Its official Android package is org.localsend.localsend_app, and the project publishes Android builds through Google Play, F-Droid and GitHub. That gives you real choices, but it also creates an easy mistake: downloading the wrong processor build from GitHub or installing a direct APK and forgetting that it will not update itself.
Recommended starting point: open the official LocalSend download page. Choose Android there, then use Google Play or F-Droid unless you specifically need the developer’s GitHub APK.
LocalSend APK information
| App detail | Verified information |
|---|---|
| App name | LocalSend |
| Category | Local file sharing |
| Android package | org.localsend.localsend_app |
| Developer | Tien Do Nam and LocalSend contributors |
| Source code license | Apache License 2.0 |
| Latest GitHub release checked | 1.17.0 |
| Release date | February 20, 2025 |
| Minimum Android version | Android 5.0 |
| Supported desktop systems | Windows 10+, macOS 11+ and Linux |
| Connection | Same local network or Wi-Fi |
| Account required | No |
| Internet required for transfer | No, after the apps are installed |
| Official Android sources | Google Play, F-Droid and GitHub Releases |
| Modified APK hosted by APKWala | No |
The project currently calls version 1.17.0 its latest LocalSend APK release. “Latest” can change, so check the release badge and date before downloading rather than trusting a version number copied into an old blog post.
See APKWala’s Pakistan Android apps section for more official-source guides.
What we verified
We checked LocalSend’s official website, GitHub repository, latest GitHub release and F-Droid listing on August 2, 2026. The project documentation lists Android 5.0 as the minimum, identifies TCP and UDP port 53317 for incoming local traffic, and warns that direct app downloads do not auto-update.
We did not transfer a private reader’s files or test every router sold in Pakistan. Router menus, Windows firewall prompts and Android permission names differ by device. The troubleshooting below follows the project’s published setup details and separates confirmed requirements from likely local-network causes.
How to download LocalSend APK safely
You have three verified Android routes:
- Google Play: easiest for automatic updates and device compatibility checks.
- F-Droid: suitable if you already use the open-source Android repository.
- GitHub Releases: useful for direct APK files and processor-specific builds.
The LocalSend project recommends an app store or package manager because the app has no built-in auto-update. A direct GitHub installation is legitimate, but you must check for later releases yourself.
Whichever route you choose, confirm the package name org.localsend.localsend_app. Avoid websites that add “Pro,” “Premium Mod,” “unlimited speed” or advertisements to the name. LocalSend is already free and has no paid speed tier to unlock.
Which LocalSend APK file should you choose on GitHub?
The version 1.17.0 release contains several Android files:
android-arm64v8.apkfor most modern 64-bit Android phonesandroid-arm32v7.apkfor older 32-bit ARM devicesandroid-x64.apkfor x86-64 Android hardware or some emulatorsandroid-google-play.apk, a larger general build associated with Play distribution
Do not guess if you are unsure. Google Play or F-Droid can select a compatible build for you. Installing the wrong architecture usually produces an installation error rather than improving speed.
GitHub marks the 1.17.0 release commit as verified and lists the files under the official localsend/localsend repository. Use the official LocalSend GitHub releases page instead of a re-uploaded attachment from a forum or video description.
How to use LocalSend from Android to PC
Install LocalSend on both devices. The Android app alone cannot send to a PC that is not running LocalSend or its supported web-sharing flow.
- Connect the phone and computer to the same Wi-Fi network.
- Open LocalSend on both devices.
- On Android, tap Send.
- Choose files, media, text, an app or a folder as supported by your device.
- Tap the computer’s generated device name.
- Accept the request on the computer.
- Wait for the transfer to finish before closing either app or changing networks.
Received files normally go to the destination selected in LocalSend settings. If you cannot find one, open the Receive history and use the option to show the file in its folder.
LocalSend can move data between Android and Windows without mobile data, but the router still provides the local connection. Turning the internet subscription off does not necessarily stop the transfer. Turning Wi-Fi off does.
For another locally relevant Android guide, see our SIMOSA app download and login guide.
Does LocalSend work offline?
Yes, with a specific meaning. LocalSend does not need an external server or working internet connection for a transfer. Both devices still need a shared local network where they can reach each other.
A home Wi-Fi router can provide that network even during a broadband outage. A phone hotspot may also work if the connected devices are allowed to communicate with one another. Some hotspots isolate clients or treat the hotspot phone differently, so discovery can fail even though each device shows a Wi-Fi connection.
The files remain on the local path between the devices. LocalSend’s project documentation says communication uses HTTPS with certificates created on the devices. This is useful protection, but you should still confirm the receiving device name and transfer request before accepting private files.
LocalSend APK not finding device
Both apps can be open and still show an empty device list. Most cases come down to the local network, firewall or Android background restrictions.
Check these in order:
- Confirm both devices show the same Wi-Fi network name.
- Keep LocalSend open in the foreground on both devices.
- Turn off mobile data briefly on Android so the route is unambiguous.
- Disconnect any VPN on both devices for one test.
- Avoid a guest Wi-Fi network.
- Allow LocalSend through the computer firewall on private networks.
- Restart LocalSend, then restart the router if other checks fail.
Do not disable the whole firewall permanently. Add an allow rule for LocalSend on the trusted private network instead.
Roman Urdu device discovery help
Agar LocalSend mein doosra device show nahi ho raha, dono devices ko aik hi Wi-Fi par connect karein. VPN temporary band karein, app dono taraf open rakhein aur guest Wi-Fi use na karein. Windows Firewall prompt aaye to LocalSend ko sirf Private network par allow karein. Public network par bina zaroorat access na dein.
Fix Windows Firewall blocking LocalSend
LocalSend’s setup documentation says incoming TCP and UDP traffic uses port 53317. Outgoing TCP and UDP traffic must also be allowed.
On Windows:
- Open Windows Security.
- Go to Firewall & network protection.
- Choose Allow an app through firewall.
- Find LocalSend and allow it on Private networks.
- Reopen LocalSend on the PC and Android phone.
If LocalSend is missing from the list, reinstall it from the official Windows download or add the installed executable through the firewall dialog. Corporate laptops may enforce rules that you cannot change. In that case, ask the administrator instead of downloading a firewall-bypass tool.
Port-forwarding on the internet router is not needed. LocalSend works inside the LAN. Do not expose port 53317 to the public internet merely to fix nearby discovery.
Router AP isolation and guest Wi-Fi
AP isolation, client isolation or wireless isolation prevents devices on the same Wi-Fi from talking to one another. Guest networks often enable it by default. Internet access works, but LocalSend discovery does not.
Move both devices to the main trusted Wi-Fi. If you control the router, look for AP isolation under wireless or guest-network settings. Disable it only on a network where you trust the connected devices.
On university, hostel, hotel and office Wi-Fi, isolation may be intentional. A personal hotspot or home router is often the practical alternative. Make sure its client-sharing policy permits local connections.
LocalSend device appears but transfer fails
Discovery and file transfer are separate steps. If the device appears but the progress stays at zero or stops midway:
- Keep both screens awake for a test.
- Remove Android battery restrictions for LocalSend.
- Check free storage on the receiving device.
- Send one small image before testing a large video or folder.
- Stay close enough to the router for a stable signal.
- Stop VPN, proxy and third-party firewall software temporarily.
- Check whether the receiver rejected or timed out the request.
If small files work but large files fail, storage, Wi-Fi stability or background suspension is more likely than device discovery. Do not repeatedly send the same folder until you check whether a partial copy already exists.
Roman Urdu transfer help
Agar device show ho raha hai lekin file send nahi ho rahi, pehle aik choti photo bhej kar test karein. Receiving device ki storage check karein aur dono screens kuch dair awake rakhein. Bari video fail ho to router ke qareeb aa kar dobara try karein. Adhoori file pehle delete ya rename kar lein taake duplicate ka confusion na ho.
LocalSend permissions on Android
Android may request access to photos, videos, files, nearby devices or notifications depending on the OS version and the feature you use. Give access needed for the files you intend to select. A permission denial can make a folder appear empty even when discovery works.
If selection fails:
- Open Android Settings and find LocalSend under Apps.
- Review Permissions.
- Allow the relevant photos, videos or files category.
- Return to LocalSend and select the file again.
LocalSend should not require accessibility-service control to send normal files. Treat a separately downloaded build that asks for unrelated SMS, call-log or accessibility permissions with suspicion.
LocalSend APK not installing
An “App not installed” message may mean the APK uses the wrong processor architecture, Android is older than 5.0, the download is incomplete or an installed copy has a different signing certificate.
Try the store version first. If you need GitHub, download one build from the official release, wait for it to finish and open it from Android’s Downloads screen. Grant “Install unknown apps” only to the browser or file manager used for that installation, then turn the permission off again.
A signature conflict can happen when switching between distribution channels. Back up anything important, check the project’s current instructions and avoid overwriting a trusted installation with a LocalSend APK from an unknown site.
How LocalSend updates work
Google Play and F-Droid manage updates through their own clients. A LocalSend APK installed directly from GitHub does not update automatically, according to the project documentation.
For a manual installation:
- Check the official Releases page.
- Compare the latest tag with the installed version shown in LocalSend settings.
- Read the release notes, especially security and Android fixes.
- Download the matching Android architecture from the official repository.
- Keep the signing source consistent where possible.
Version 1.17.0 fixed a path-traversal issue when saving files and added a network-interface filter. Those are good reasons to avoid older builds when your device supports the current release.
Is LocalSend APK safe?
LocalSend has public source code and publishes through recognized stores as well as its own GitHub repository. F-Droid describes it as open source, ad-free and without tracking by the app, while noting that the operating system may still collect usage information.
Open source helps independent review, but the download source still matters. A modified file on another domain does not inherit the trust of the official code repository. Use the official site, Play Store, F-Droid LocalSend listing or verified GitHub repository.
When receiving a file, read the sender name and filename before accepting. Local encryption does not make a malicious file harmless after it arrives. Scan unexpected executable or APK files before opening them.
For higher-risk account apps, our JazzCash APK safety guide explains why source verification matters even more.
LocalSend APK FAQs
What is the latest LocalSend version?
GitHub showed version 1.17.0 as the latest release when checked on August 2, 2026. Verify the release page before downloading because this number can change.
Can LocalSend transfer files without internet?
Yes. It sends files over the local network without a cloud server. Both devices still need to share a Wi-Fi, router or compatible hotspot connection.
Does LocalSend work between Android and Windows?
Yes. Install LocalSend on Android and Windows, connect both to the same local network, open both apps and select the PC from the Android Send screen.
Why is my PC not visible in LocalSend?
Check that both devices use the same non-guest Wi-Fi. Then allow LocalSend through Windows Firewall on private networks and make sure router AP isolation is off.
Which port does LocalSend use?
The official setup guide lists incoming TCP and UDP port 53317. Allow the app locally in the firewall; do not create public internet port forwarding.
Is LocalSend available on F-Droid?
Yes. The official project links to its F-Droid package, org.localsend.localsend_app.
Do I need the APK on my PC too?
No. APK is the Android format. Download the Windows EXE, macOS package or appropriate Linux build from the official LocalSend site for the computer.
Start with the store build if you want automatic updates. Use GitHub only when you understand the architecture choice, and solve discovery problems on the local network rather than cycling through unofficial APK files.








