LocalSend for QNAP brings fast, private and local file transfers directly to your NAS, without relying on cloud services, external accounts or third-party storage.
The package provides a headless LocalSend-compatible transfer engine together with a dedicated HTTPS Web interface designed for QNAP NAS environments.
Main Features
- LocalSend-compatible file transfers over the local network
- No cloud service required
- No external account required
- HTTPS communication
- Dedicated QNAP Web interface
- Custom receive folder selectable directly from the Web UI
- Browse QNAP shared folders under
/share - Automatic validation of the selected destination
- Write-access verification before applying a new destination
- Free-space verification
- Persistent receive-folder configuration
- Automatic daemon restart after configuration changes
- LocalSend service remains separated from the administration Web UI
- Automatic architecture detection at startup
- Multi-architecture package:
- x86_64
- aarch64
- ARMv7 / armhf
- Static binaries built with
CGO_ENABLED=0 - No runtime dependency on the NAS glibc
- Suitable for QTS systems using glibc 2.21 or newer
- UPX-compressed binaries
- QTS event-log integration
- Persistent runtime configuration
- Dedicated logs, PID files, cache and temporary directories
- Upgrade-safe configuration handling
Web Interface
The integrated Web interface provides a simple way to manage the LocalSend service from a browser.
Default Web UI:
https://NAS_IP:15327
From the interface you can:
- View the LocalSend daemon status
- Check the daemon PID
- Check service uptime
- View the active LocalSend protocol port
- Select the destination folder for received files
- Browse available QNAP shares
- Check free disk space
- View LocalSend logs
- Apply configuration changes without restarting the whole QPKG
The Web interface is protected by an administrator token generated during the first startup.
The token is also reported through the QTS system log for easy retrieval.
LocalSend Protocol
The LocalSend-compatible transfer service runs independently from the Web administration interface.
Default LocalSend protocol endpoint:
https://NAS_IP:53327
This port is used by LocalSend clients on the local network and is not intended to display a Web page.
The administration interface runs separately on port 15327.
Receive Folder
By default, received files can be stored inside the LocalSend application directory.
The destination can then be changed from the Web interface to any authorized QNAP shared folder under /share.
Example:
/share/Public/LocalSend
or:
/share/Download/LocalSend
The selected destination is validated before being activated.
LocalSend verifies that:
- the path is located under
/share - the destination exists or can be created
- the directory is writable
- enough free disk space is available
The selected path is stored persistently and survives service restarts and package upgrades.
HTTPS Support
The package automatically attempts to reuse an available QTS or myQNAPcloud certificate.
If no suitable certificate is available, LocalSend can use a locally generated self-signed certificate.
This allows HTTPS to remain available without requiring manual certificate preparation.
Supported Architectures
The same package archive can contain binaries for:
- Intel / AMD 64-bit —
x86_64 - ARM 64-bit —
aarch64 - ARMv7 —
armhf
At startup, the package automatically detects the NAS architecture and launches the appropriate binary.
Runtime Compatibility
The LocalSend service and Web interface are compiled as static Go binaries with:
CGO_ENABLED=0
This means they do not require the NAS glibc at runtime.
The package is therefore suitable for older QTS environments using glibc 2.21 as well as newer QTS versions.
Security
The package includes several security measures:
- HTTPS communication
- Administrator-token protection for the Web interface
- QTS event logging
- Receive-folder path validation
/sharepath restriction for user-selected storage- Write-access verification
- Persistent TLS configuration
- Separate LocalSend and administration services
- Static binaries with minimal runtime dependencies
- No Docker requirement
Quick Start
- Install the LocalSend QPKG.
- Start the package from QTS.
- Retrieve the Web administrator token from the QTS system log.
- Open:
https://NAS_IP:15327
- Authenticate using the administrator token.
- Open the destination-folder configuration.
- Select the QNAP shared folder where received files should be stored.
- Save the configuration.
- Open LocalSend on another device connected to the same local network.
- Your QNAP NAS can then receive LocalSend transfers directly into the selected share.
Default Ports
LocalSend protocol:
53327 / HTTPS
Administration Web UI:
15327 / HTTPS
Both ports can be customized in the package configuration.
Source Projects
LocalSend is based on the LocalSend protocol and ecosystem.
Official LocalSend project:
https://github.com/localsend/localsend
The QNAP headless implementation uses a Go-based LocalSend-compatible engine adapted for NAS usage.
Why LocalSend on QNAP?
Running LocalSend directly on a QNAP NAS makes the NAS a convenient local transfer destination for desktops, laptops, tablets and mobile devices.
Files can be sent directly to a shared folder on the NAS without uploading them to an external cloud provider.
This is especially useful for:
- quickly transferring photos from a phone
- moving documents between computers and the NAS
- receiving large files directly into shared storage
- keeping transfers entirely on the local network
- reducing dependency on cloud-storage services
LocalSend for QNAP combines the simplicity of LocalSend with the storage capacity, availability and centralized management of a QNAP NAS.
Last update: 27 September 2026
