How to Backup Photos to Existing NAS Hardware (2026 Guide)
Your NAS is already a file server. Here is how to send photos from your phone straight into a share you own — with no new hardware, no container stack, and no vendor lock-in.
The short answer
Yes, you can back up photos to an existing NAS with no new server. A NAS already runs file-sharing services such as SMB, WebDAV, or NFS, and Pho connects to those services directly over your local network or a VPN. Nothing needs to be installed on the NAS — the sync engine is embedded in the phone app.
Most NAS photo apps expect you to adopt their ecosystem first. This guide takes the opposite approach: use the NAS you already own as plain file storage, keep the folder structure readable by any device, and avoid adding a database, a container platform, or a second computer to the photo path.
Why your existing NAS is enough
Most people searching for a photo backup server do not actually need one. A NAS is already a file server with RAID, snapshots, and a backup routine you have paid for. Putting a second computer, a database, or a container platform in front of it increases the number of systems that can fail without making your photos any safer. A backup app only has to speak the file-sharing protocol your NAS already exposes and write files into a share.
That is the difference between an app like Pho and server-based photo platforms. Immich, PhotoPrism, and Nextcloud are strong options, but each one expects a host to run on. Pho takes the direct path: the phone talks to the NAS, the NAS stays a NAS, and your photos remain plain files that any device can read.
Protocol matrix: SMB vs WebDAV vs NFS and cloud targets
The matrix below maps every target Pho can write to, in the order most people should consider them when they already own a NAS. Protocol support is implemented in the app itself, so the only requirement on the NAS side is an enabled file service.
| Protocol | Typical support on NAS | Authentication | Best for | Remote use |
|---|---|---|---|---|
| SMB/CIFS | Built into Synology DSM, QNAP QTS, TrueNAS, OpenMediaVault, unRAID, plus Windows and macOS shares | Username and password (NTLM) | Simple backup on your home network for every NAS brand | Through a VPN such as WireGuard or Tailscale |
| WebDAV | Server package on Synology and QNAP; built into Nextcloud, ownCloud, and many Linux NAS setups | HTTP Basic auth over TLS | Backing up when you are away from home without a VPN | Works over HTTPS with a reverse proxy |
| NFS | Linux-based NAS and servers: TrueNAS, OpenMediaVault, unRAID, most Linux distributions | Host-based AUTH_UNIX, designed for trusted networks | Fastest transfer on a trusted local network | VPN only |
| S3-compatible | Object storage rather than NAS shares: AWS S3, Backblaze B2, Cloudflare R2, MinIO | Access key and secret key; region detected automatically or set by hand | An off-site copy that survives local hardware failure | Native over HTTPS |
| Google Drive | Your existing Google account, no NAS hardware involved | OAuth sign-in | A second off-site copy for photos already on your NAS | Native over HTTPS |
| Baidu Netdisk | Baidu account with a dedicated app folder | OAuth sign-in | Users already invested in the Baidu ecosystem | Native over HTTPS |
Which one should you pick?
For a first setup on a home network, choose SMB: it is already enabled on nearly every consumer NAS and takes a host, a share, a username, and a password. Add WebDAV if you want backups to continue when you are away from home without a VPN, and use NFS only on a trusted LAN where both devices speak Linux.
Setting it up on common NAS brands
Menu names differ between vendors, but the shape of the setup is the same on Synology, QNAP, TrueNAS, OpenMediaVault, unRAID, or a home-built Linux server: enable a file service, create a folder and a user for the phone, then enter those details in the app once.
SMB: the default choice on most NAS brands
SMB is the protocol NAS vendors enable first, and it is what Finder, Windows Explorer, and most file managers speak. Enable SMB sharing in the NAS admin panel, create a shared folder for photos, and grant one user read and write access. In the app, add the NAS address, the share name, and that user's credentials. Pho handles NTLM authentication directly, so no extra client software or mount step is required on the phone.
WebDAV: backup when you are away from home
Enable the WebDAV server package on your NAS, or point the app at a WebDAV endpoint you already run, such as Nextcloud. Publish it over HTTPS through a reverse proxy, then add the URL and credentials in the app. Self-signed certificates are accepted, so a home-lab TLS certificate works without extra purchases.
NFS: maximum speed on a trusted LAN
Export a folder from a Linux-based NAS or server to your phone's network, then add the host and export path in the app. NFS uses host-based AUTH_UNIX instead of per-user passwords, so keep it inside a trusted local network and reach it from outside only through a VPN.
If you also want an off-site copy, add an S3-compatible bucket (AWS S3, Backblaze B2, Cloudflare R2, or MinIO) or Google Drive as a second target. Object storage is not a NAS replacement, but it covers the case where local hardware is lost, stolen, or damaged.
First-party evidence: what Pho implements itself
Everything described above is implemented in Pho itself rather than assembled from separate tools. The sync engine is a Go backend compiled into the app with gomobile; it starts on a loopback port between 10000 and 20000, so there is no companion server, container, or daemon running on the NAS. Every target is a native client: SMB with NTLM authentication, WebDAV with Basic auth and self-signed TLS support, NFS over AUTH_UNIX, an S3 client whose region is detected automatically when left blank, plus Google Drive and Baidu Netdisk. Pro adds optional client-side AES-256-GCM encryption: files are written with a .aes suffix and a PHO1 header, the key never leaves your device, and encrypted videos still support HTTP Range requests for seeking. Legacy AES-128-CFB files remain decryptable, while every new upload uses GCM.
- Protocol support: SMB, WebDAV, NFS, S3-compatible object storage, Google Drive, and Baidu Netdisk are all first-party implementations — no plugins and no helper binaries.
- Zero-server: the app writes to the NAS directly, so you avoid the maintenance and the attack surface of an always-on middleware process.
- File layout: originals land in date folders such as YYYY/MM/DD with thumbnails in a .thumbnail mirror, so the library stays portable and readable without Pho.
Frequently asked questions about backing up to an existing NAS
Can I back up photos to an existing NAS without a new server?
Yes. A NAS already runs file-sharing services such as SMB, WebDAV, or NFS, and Pho connects to those services directly. Nothing is installed on the NAS itself: there is no companion server, virtual machine, or Docker container anywhere in the photo path.
Which protocol should I choose: SMB, WebDAV, or NFS?
SMB is the best default for most people: it is already enabled on nearly every consumer NAS and works on the local network with a simple username and password. Choose WebDAV when you want backups to continue over the internet without a VPN, and NFS for Linux servers on a trusted LAN where you want maximum throughput.
Does Pho need Docker or a companion app installed on the NAS?
No. The sync engine is a Go backend compiled into the Pho app itself, and it listens on a local port on your phone. Your NAS only needs its normal file service enabled, which is usually a single toggle in the NAS admin interface.
Will my photos stay as normal files I can browse on the NAS?
Yes. Photos are stored as untouched originals in date folders such as YYYY/MM/DD, with thumbnails mirrored in a .thumbnail folder. You can open, copy, or reorganize them with any SMB, WebDAV, or NFS client, and nothing depends on Pho or a proprietary catalog.
How does background backup work when the iPhone is locked?
On Android, Pho runs a periodic background sync timer. On iOS it uses a background processing task, and the same sync logic also runs headless when iOS wakes the app. iOS decides the exact timing, but uploads typically complete within a few hours of a photo being taken.
What happens if I later switch to a different NAS brand?
Your library keeps working. Pho writes plain files into date-based folders on whatever target you choose, so moving to another NAS is a normal file copy. There is no vendor account, database, or proprietary catalog to migrate or rebuild.
Does Pho encrypt photos before they reach my existing NAS?
Pro adds optional client-side AES-256-GCM encryption before upload, so the NAS stores .aes ciphertext and the key never leaves your device. Encrypted videos still support HTTP Range requests for seeking, and files encrypted by older Pho versions with AES-128-CFB remain readable.
Is Pho free to use when I already own the NAS hardware?
Basic sync to your own storage is free. Pro adds client-side encryption and parallel uploads, and is available as a subscription at $1.99 per month or $19.99 per year, or as a one-time $39.99 lifetime license.
Related reading
Ready to back up photos to the NAS you already own?
Download Pho, point it at your NAS over SMB, WebDAV, or NFS, and let background sync handle the rest.