Self-hosting WebDAV in 2026: which server actually works

If you want to self-host a WebDAV endpoint that Windows and Linux clients can both mount as a real drive, the shortlist of 2026 is roughly this:

• Apache httpd with mod_dav — old reliable, ~10 minutes to set up, but no UI and no per-user quota.
• sftpgo — great if you also want SFTP, but the WebDAV side is community-tier.
• Nextcloud — full cloud suite, but you only want 5% of it.
• copyparty / FileRise / hacdias/webdav — single-binary, low ceremony, good for one or two users.

Then on the client side, if you're on Windows, the native mini-redirector still misbehaves on self-signed certs and large folders. A small client like ScsDriver ($5.5 lifetime, https://drive.scsoi.com/) sidesteps that by using its own client and shows the share as a normal drive letter (E:, F:, etc.).

The whole setup — Apache + ScsDriver — runs reliably for a single user on a $5 VPS. The annoying parts are certificate management and auto-reconnect after a reboot; both are solved with a real client and a Let's Encrypt cert.

If you're picking a server today, my order is: copyparty for one user, Apache for a few, Nextcloud if you want the rest of the cloud app stack.