LocalSend NAS

An unofficial LocalSend node for NAS that sends files from host-mounted shares to nearby LocalSend devices and receives files into chosen shares via a web UI,…

  • Network Services
  • Tools & Utilities
An unofficial LocalSend node for NAS that sends files from host-mounted shares to nearby LocalSend devices and receives files into chosen shares via a web UI, without clients browsing the NAS or round-tripping through a laptop.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

46/100 Fair

Maintained
74last commit 62 days ago
Popular
102 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 25 days ago

GitHub stars
2
Open issues
0
Last commit
2026-09-19
Latest release
v0.2.2
Activity
stale

Checked 8 days ago - source: GitHub (alexindigo/localsend-nas)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Open the LocalSend transfer port Find the port (a numbered connection point) LocalSend advertises (the docs show 53317 as an example) and open it in your NAS/router firewall (the rule set that allows or blocks traffic). Other devices connect to that port for file transfers, so if it is blocked, downloads will fail. source
  • Let the network see LocalSend Allow UDP multicast (a network message sent to many nearby devices at once) on your home network. LocalSend sends a short announcement when it starts so phones and computers can find it; if that is blocked, the NAS will not show up in their device list. source
  • Use the same PIN if one is required If LocalSend asks for a PIN (a short password) when sending files, enter the same PIN on the receiving device. A missing or wrong PIN causes the receiver to be rejected, making the transfer look broken. source
  • Networking Keep the Unraid template on host networking; LocalSend discovery uses multicast UDP 53317, which Docker bridge/NAT can break. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does the Docker template require host networking?

LocalSend discovery relies on multicast UDP port 53317. Docker bridge or NAT networking can break that discovery, so the template intentionally uses host networking.

What happens if I do not accept an incoming transfer in the web UI?

The UI shows a 30-second countdown by default. If a dropbox share is configured, the files are auto-accepted there; otherwise the request is rejected.

How can I make the node send-only?

Start it with --read-only or set LOCALSEND_NAS_READ_ONLY=1. In that mode it refuses receiving with a 403 response.

Do received files overwrite existing files in the same share?

No. Received files keep their folder structure and are deduplicated with names like name (1).ext.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads