SMB vs WebDAV vs NFS for Photo Backup: Which Should You Use?
For backing up photos from a phone to a NAS, use SMB on your local network — it is already enabled on nearly every consumer NAS and takes only a host, a share, and a password. Use WebDAV when backups must continue across the internet without a VPN. Use NFS mainly on Linux or macOS clients on a trusted LAN, where it is typically the fastest of the three.
The short answer
SMB is the default for home networks, WebDAV is the one to publish over HTTPS for backups away from home, and NFS is for trusted Linux-to-Linux networks. All three end up as plain files on your NAS — the difference is who can connect, how far the connection reaches, and what protects it in transit.
All three protocols do the same basic job: they let a phone write files into a share on your NAS. The differences show up in three places — how fast large batches move, who can connect without extra software, and how far from home the connection is allowed to reach. The table below compares them on the criteria that matter for photo backup, and each protocol then gets a practical profile.
SMB vs WebDAV vs NFS: comparison table (2026)
Every row below reflects how the protocol behaves in a typical home or small-office photo backup setup. Authentication and remote-access rows are the ones people trip over most often.
| Criterion | SMB | WebDAV | NFS |
|---|---|---|---|
| Speed | Fast on a LAN; SMB2 and SMB3 are built for moving large files | HTTP overhead per file; usually slower than SMB or NFS on the same LAN | Typically the fastest of the three on a trusted LAN, especially with many small files |
| iOS support | Native: the iOS Files app connects to SMB shares directly | Not built into Files; needs an app that speaks WebDAV, such as Pho | No native iOS client; only apps that implement NFS themselves can use it |
| Android support | No built-in client in stock Android, but most file managers and backup apps speak SMB | Common in file managers and backup apps; no built-in client | Rare on Android; used mainly by specialized apps |
| Remote / internet access | VPN only (WireGuard, Tailscale). Never expose SMB to the internet | Native over HTTPS behind a reverse proxy — no VPN needed | VPN only. Never expose NFS |
| Authentication | Username and password (NTLM) | HTTP Basic auth over TLS | Host-based AUTH_UNIX — the network is the trust boundary |
| Encryption | Optional SMB3 encryption; home setups usually rely on the LAN or a VPN | TLS in transit over HTTPS; always publish it with a certificate | None built in; trusted network or VPN only |
| Best for | Home-network photo backup on any NAS brand | Backups that keep running anywhere, without a VPN | Fast Linux-to-Linux transfers on a trusted LAN |
None of the three encrypts the file on disk by itself — they protect the connection, not the bytes at rest. If the share itself must hold ciphertext, use client-side encryption: Pho Pro adds optional AES-256-GCM before upload, the NAS stores .aes files, and the key never leaves your device. For the full picture of pointing an app at hardware you already own, see the guide to backing up photos to an existing NAS.
SMB, WebDAV, and NFS in practice
Each protocol has a personality, and it helps to know which one you are looking at before you type an address into an app.
SMB: the default that is already enabled
SMB is what NAS vendors switch on first, and it is what Finder, Windows Explorer, and most mobile file managers speak. An app authenticates with a username and password over NTLM, and SMB2/SMB3 handle large files efficiently. On an iPhone, the Files app connects to SMB shares natively; on Android, SMB support comes from file managers and backup apps. Keep SMB inside the LAN or reach it through a VPN such as WireGuard or Tailscale — it is not a protocol to expose on a public port.
WebDAV: the one that crosses the internet
WebDAV runs on top of HTTP, which is exactly why it travels well: publish it over HTTPS through a reverse proxy and you can back up from hotel Wi-Fi or a mobile network without a VPN. Synology and QNAP ship WebDAV server packages, and Nextcloud and ownCloud speak it by default. Self-signed certificates are accepted by Pho, so a home-lab TLS setup works without buying anything. The trade-off is overhead: on the same LAN, WebDAV usually finishes a big library more slowly than SMB or NFS.
NFS: the Linux workhorse
NFS was built for Unix networks and shows it. It exports a folder to a network rather than to a user, using host-based AUTH_UNIX instead of per-user passwords, so the network itself is the trust boundary. On a trusted LAN with a Linux-based NAS such as TrueNAS, OpenMediaVault, or unRAID, it is typically the fastest of the three, especially with a library full of small files. Reach it from outside only through a VPN.
One protocol gap is worth knowing: Pho does not support FTP or SFTP. If a device on your network only offers FTP, enable SMB or WebDAV on the NAS and use that instead — SMB is already on almost everywhere. From the phone side, the iPhone-to-NAS sync guide and the Android backup guide walk through the same protocols step by step.
Which protocol should you choose?
Pick with one rule
Start with SMB, add WebDAV only when you need backups to continue away from home without a VPN, and choose NFS only when both ends are Linux and the network is trusted. Most people end up running SMB at home and WebDAV for travel.
Two practical routes from here: configure the storage side with the existing-NAS guide, then check your exact model in the per-brand protocol matrix covering Synology, QNAP, TrueNAS, UGREEN, ASUSTOR, and TerraMaster. If you are still choosing an app, the best NAS photo backup apps comparison puts Pho, PhotoSync, and FolderSync side by side; and if you mainly want to look at the library, start with how to view NAS photos on your iPhone.
Frequently asked questions
SMB is the best default: it is already enabled on nearly every consumer NAS and needs only a host, a share, and a password. Choose WebDAV when backups must continue over the internet without a VPN, and NFS when both the NAS and the clients are Linux-based and the network is trusted.
On a local network, usually yes. WebDAV runs over HTTP, which adds overhead per file, so SMB or NFS typically finishes a large photo library faster on the same LAN. WebDAV earns its place through reach: published over HTTPS, it works from any network without a VPN.
Not safely by default. SMB and NFS are designed for local networks and should be reached from outside only through a VPN such as WireGuard or Tailscale. WebDAV is the protocol built to be published over HTTPS; put it behind a reverse proxy and never expose SMB or NFS ports directly.
It depends on what you are protecting against. WebDAV over HTTPS encrypts traffic in transit; SMB can enable SMB3 encryption but home setups usually rely on the LAN or a VPN; NFS has no transport encryption and belongs on a trusted network. None of the three encrypts files at rest, so if the share itself must hold ciphertext, use client-side encryption: Pho Pro adds optional AES-256-GCM before upload, and the key never leaves your device.
No. Pho writes the same plain, date-based structure — originals in YYYY/MM/DD folders with thumbnails mirrored in .thumbnail — no matter which protocol carries the bytes. A library written over SMB can be browsed over WebDAV or NFS later with no conversion.
Related reading
- Photo backup to an existing NAS: protocol matrix, setup, and first-party evidence
- NAS brand protocol matrix: Synology, QNAP, TrueNAS, UGREEN, ASUSTOR, and TerraMaster
- How to sync iPhone photos to NAS over SMB, WebDAV, and NFS
- Android photo backup to NAS: background upload and app comparison
- Best NAS photo backup apps for iPhone and Android (2026)
- How to view NAS photos on your iPhone
Ready to back up photos over SMB, WebDAV, or NFS?
Download Pho, point it at the share you already own, and let background sync handle the rest.