Can someone explain what a WebDAV server is and how it’s used?

Mac
1

I keep seeing references to WebDAV servers when setting up remote file access and I’m confused about what they actually do compared to regular file servers or cloud storage. I’m trying to decide if I should use WebDAV for sharing and editing files across different devices and apps, but I’m not sure about the benefits, security implications, or real‑world use cases. Could someone break down in simple terms what a WebDAV server is, how it works, and when it makes sense to use it?

2

What WebDAV is

WebDAV sounds more complicated than it is. The long name is Web Distributed Authoring and Versioning, but I’ve always thought of it as “FTP over normal web connections.”

In simple terms, it lets you work with files on a remote server through a normal HTTPS connection, kind of like those files sitting on your own machine.

So instead of just downloading files from a website, WebDAV lets you:

  • open files
  • edit them
  • upload new ones
  • rename things
  • delete things
  • move folders around

It’s been around since the late 90s and stuck around because it works over normal web ports (like HTTPS), which means it usually gets through firewalls that might block FTP.

What people actually use it for

In my experience WebDAV tends to show up in places people don’t realize.

For example:

  • Nextcloud and ownCloud use it for file access
  • some CMS platforms expose files this way
  • teams mount shared folders from remote servers
  • remote editing workflows where files stay on the server

One nice thing compared to FTP is file locking. If someone opens a file to edit, it can prevent someone else from overwriting it at the same time. That matters more than people think once multiple people touch the same files.

If you’ve ever connected to a shared folder over the internet and it behaved kind of like a network drive, there’s a decent chance WebDAV was behind it.

How it works in practice

From the user side it’s pretty simple.

You get a URL from whoever runs the server (usually something like https://server.com/webdav), plus a username and password. You connect with a client, and the remote files show up like a folder.

From there you just:

  • open files
  • drag files in
  • rename stuff
  • organize folders

The big difference from just downloading through a browser is the connection stays active. You edit a file and save it, and it goes right back to the server.

Both macOS and Windows have built-in WebDAV support but honestly I’ve always found it a bit unreliable. It works in a pinch but I usually recommend a dedicated client if you’re going to use it regularly.

FTP clients worth knowing about

These are the ones I usually mention when someone is getting started.

FileZilla

FileZilla is the free option most people know. It supports WebDAV along with FTP and SFTP, which is nice if you deal with different server types.

Classic two-panel layout:

  • local files on the left
  • server files on the right

It runs everywhere and works fine. Downsides are mostly that it looks pretty dated and it’s purely a transfer tool. Also on Windows just pay attention during install because of past bundled extras.

If someone wants to be free and functional, it’s still a reasonable starting point.

Commander One for Mac

If you’re on Mac and deal with remote files often, I usually suggest looking at Commander One. It’s more of a full file manager that also handles WebDAV, FTP, SFTP, and cloud storage. So instead of thinking “FTP app” and “file manager” separately, it’s just one workspace.

Feels like a proper Mac app too, which makes daily use nicer. Tabs, built-in file viewer, multiple connections open at once. Not free, but if this is part of your daily work it earns its keep.

CloudMounter for Mac and Windows

CloudMounter takes a different approach. Instead of a transfer interface, it just mounts your WebDAV server like a normal drive. Shows up in Finder or File Explorer like any other disk or network share.

You just browse it like a normal folder:

  • open files
  • move things around
  • copy stuff

No separate client window.

It also mounts FTP, SFTP, and cloud storage the same way (Google Drive, Dropbox, OneDrive, S3, etc.), which is nice if you’re dealing with a mix of storage types.

I usually suggest this to people who don’t want to “manage transfers” and just want the server to behave like another folder on their computer.

How to get started with WebDAV

The basic starting point is simple: First you need a WebDAV URL from whoever manages the server. If you’re setting it up yourself, platforms like Nextcloud can provide one.

Then you pick a client, enter the URL, enter your credentials, and connect.

One important thing: make sure it uses HTTPS. If it’s plain HTTP your login info travels unencrypted, which is not something you want outside of testing.

If you deal with remote files beyond basic FTP, WebDAV is worth knowing about. Especially if you want to open and edit files directly on a server instead of constantly downloading and re-uploading.

That’s how I usually explain it to people starting out.

1 Like
3

Think of WebDAV as “HTTP file sharing with edit support,” not a whole new type of storage.

What a WebDAV server is
You run a normal web server (Apache, Nginx, IIS) with WebDAV turned on.
It exposes a folder over HTTP or HTTPS so clients treat it like remote files.
Underneath, the data still sits on a regular filesystem, NAS, or whatever you use.
WebDAV is a protocol layer on top, not a storage system.

What it does compared to other options

  1. Versus a “regular” file server on a LAN
    Typical LAN shares: SMB (Windows shares) or NFS.
    They work great inside a local network, often poor over the public internet.
    Firewalls often block SMB. Latency hurts. Security is harder to get right.

WebDAV uses HTTP or HTTPS on port 80 or 443.
So it goes through most firewalls, works fine over VPNs, and integrates with web auth.
You get simple operations: list, upload, download, move, delete, lock.

Downside:
SMB has better locking, notifications, and performance on a LAN.
WebDAV over a high latency network feels slower, especially for many small files.

  1. Versus cloud storage (Google Drive, OneDrive, Dropbox, etc.)
    Cloud services give you:
    Sync clients.
    Version history.
    Sharing links.
    Trash, web UI, mobile apps.

WebDAV gives you a remote folder over HTTPS.
No sync client by default. No versions unless the backend system adds them.
Some cloud services expose WebDAV endpoints though, like Nextcloud or some S3 gateways.

If you want “edit live on server” workflows, WebDAV fits.
If you want offline sync and version history for non technical users, cloud storage wins.

Where I agree and disagree a bit with @mikeappsreviewer

I agree:
It behaves a lot like “FTP over HTTPS.”
It is handy for remote editing, and many users do not even know they use it.
Native WebDAV in Windows and macOS is flaky.

I disagree slightly on usage style.
I would not treat WebDAV as your daily “mount this like a local drive and forget” tool for heavy work.
For lots of small file operations or folder trees, it becomes slow and sometimes corrupt on unstable networks.
For heavy duty remote work, I prefer either:
SFTP in a proper client, or
WebDAV through a good mounting tool plus some local caching.

When to use WebDAV

Good use cases:
You host something like Nextcloud or ownCloud and want users to open and edit files from Office or similar apps.
You have a web server already, want simple remote file access without exposing SMB.
You need something that works through corporate firewalls with minimal network changes.
You edit website content or configs directly on a remote server in a controlled way.

Avoid or rethink WebDAV if:
You need high performance large file sync for many users.
You want strong version control and collaboration like Google Docs or Git.
You have users with unreliable internet.
In those cases, sync clients or a VCS work better.

How you would use WebDAV in practice

On the server side:
Enable WebDAV module in Apache, Nginx, or IIS.
Point it at a folder.
Secure it with HTTPS and proper auth.
Optionally put it behind a reverse proxy or VPN.

On the client side:
You get a URL, username, and password.
Then either:
Use a dedicated file transfer tool that supports WebDAV.
Or mount it as a network drive.

This is where CloudMounter is useful.
CloudMounter mounts WebDAV as a drive on Windows or macOS.
So you see the WebDAV server in Finder or File Explorer and work with it like a local folder.
It also talks to other protocols like SFTP, plus cloud services, in the same interface.
For non technical users, this is simpler than dealing with WebDAV quirks in the OS.

How to decide if WebDAV fits your remote file access

Use WebDAV if:
You already have a web server.
You want simple shared remote folders.
You prefer open protocols over vendor specific sync “magic.”
You do not need complex sharing logic and versions.

Use pure cloud storage if:
You need quick sharing links, permissions, and version history with minimal admin.
Your users are not technical and expect Drive or Dropbox style workflows.

Use SMB or NFS over VPN if:
All users are inside the same company.
You need fast access to big datasets.
You control the network and clients.

So if your goal is “I want to open and save files on my home or office server from outside,” WebDAV with HTTPS plus something like CloudMounter is a solid, boring choice. If you want sync, collaboration features, and nice web UI, go with a cloud platform or Nextcloud and treat WebDAV as the protocol under the hood, not the product you sell to users.

4

WebDAV is basically “speak HTTP like it’s a filesystem.” Not magic storage, not a new cloud. Just a protocol that lets clients treat a folder on a web server kind of like a mounted drive.

A few angles that haven’t been hit as hard yet:

1. What WebDAV actually adds on top of plain HTTP

Regular HTTP:

  • GET: download file
  • PUT/POST: upload file (usually via web forms or APIs)
  • DELETE: maybe delete, but rarely used directly by users
  • No concept of “this is a folder, list it” in a user-friendly way

WebDAV extends that with:

  • PROPFIND: give me metadata and directory listings
  • MKCOL: create “collections” (folders)
  • MOVE / COPY: server-side moves and copies
  • LOCK / UNLOCK: “I’m editing this file, don’t let someone else stomp on it”

So instead of abusing a web app or half-baked upload page, WebDAV provides a standard way for a client to browse directories and manipulate files over HTTP/HTTPS.

Under the hood, it’s still just files on disk or whatever your backend is. Like @mikeappsreviewer and @stellacadente said, it’s a protocol layer, not a storage engine.

2. How it feels compared to SMB/NFS and cloud sync

Rough, biased overview:

SMB/NFS (LAN file shares)

  • Great inside a fast local network
  • Feels like using a local drive
  • Terrible idea to expose directly to the internet
  • Better locking and notifications, stronger semantics

WebDAV

  • Works over HTTPS on port 443, so it survives firewalls and hotels, etc.
  • Good for “remote drive over the internet,” but latency hurts
  • Every tiny file operation is an HTTP round-trip, which can get ugly

Cloud storage (Drive/Dropbox/OneDrive)

  • Local sync folder + background sync
  • Version history, sharing links, recycle bin
  • Less control over where exactly the data lives, vendor lock-in vibes

In practice:

  • WebDAV is nice when you want direct remote access without full sync.
  • Cloud sync is better for “normal” users who just want stuff to work offline and not think about protocols.

I slightly disagree with the idea that WebDAV is always just “FTP over HTTPS.” That’s a useful mental model, but WebDAV tries harder to be a proper filesystem protocol with locks and richer metadata. It’s just… the implementation quality varies a lot, especially in OS-native clients.

3. When WebDAV is actually a good idea for you

Use WebDAV if:

  • You control a server (home lab, VPS, office server) and want a simple remote filesystem over HTTPS
  • You like open standards and not being tied to a single cloud vendor
  • You need something that will work from random networks where SMB/VPN is a pain
  • You mostly work with documents, configs, web content, not millions of tiny files

Probably don’t use WebDAV as your main tool if:

  • You have users with flaky connections who will rage-quit when saves timeout
  • You need heavy collaboration, comments, version history, conflict resolution
  • You’re pushing huge data sets or zillions of small files constantly

For those cases, a sync-based tool or SMB/NFS over VPN is usually saner.

4. How to actually live with WebDAV on the client side

Native WebDAV in Windows and macOS technically works, but “technically works” is doing a lot of work there. It can:

  • randomly drop connections
  • be very slow listing large folders
  • choke on weird characters or long paths

This is where a proper client is worth it. Since you mentioned remote file access and “should I use WebDAV,” I’d look at how you plan to interact with it daily:

  • If you’re fine with a “two‑pane” transfer tool (local left / remote right), SFTP and WebDAV clients are great.
  • If you want the remote stuff to just show up as another drive in Finder or File Explorer, something like CloudMounter is a lot nicer.

CloudMounter sits in between:

  • Mounts WebDAV as a network drive
  • Also does SFTP and various clouds in the same way
  • Lets you keep using your normal file manager instead of juggling separate transfer windows

That solves a big part of the “WebDAV is annoying” story without changing the server at all.

5. How to decide for your setup

Given what you wrote, I’d choose based on this:

  • You want: remote access to your home/office files from anywhere, minimal setup, no full sync.
    → WebDAV over HTTPS, mounted via something like CloudMounter, is a solid choice.

  • You want: share links, version history, web UI, mobile apps for non‑technical users.
    → Use a cloud platform (or Nextcloud / ownCloud) and treat WebDAV as the backend protocol, not something users need to know about.

  • You want: high performance shared storage for a team on the same network.
    → SMB/NFS through VPN, WebDAV only as a backup option when you’re outside the network.

If you post your specific scenario (home server vs business, number of users, typical file sizes, need for sync or not), you’ll get more targeted “do this, skip that” advice. Right now, WebDAV is probably either exactly what you need or a complete overkill, depending on whether you actually want live remote filesystem access or just “my files are everywhere” cloud-style sync.

5

Think of WebDAV like this: it turns a folder on a web server into something that pretends to be a network drive, but it is not trying to be a full “cloud platform” like Google Drive.

A few points that complement what was already said:

  1. Conceptual role

    • @stellacadente leans on the “HTTP filesystem” idea, which is accurate, but I’d add: WebDAV is surprisingly “dumb” about higher level features.
    • No built‑in versioning, sharing UI, recycle bin or collaboration logic. Those only exist if your application (Nextcloud, etc.) adds them.
    • Compared to a “regular” file server, WebDAV trades rich semantics and performance for easier access across the internet.

  2. Where it quietly shines

    • Access from “locked down” networks where only 80/443 are allowed.
    • Simple “I need this one remote folder to behave like a drive” scenarios.
    • Integrations where apps speak WebDAV under the hood (some note apps, document editors, etc.).

  3. Where people overestimate it

    • I partially disagree with the idea of treating it like a general-purpose remote filesystem for everything.
    • Large developer repos, massive photo libraries, or build artifacts over WebDAV are usually pain. SFTP or SMB over VPN tends to be less frustrating here.
    • Latency is killer. Listing a huge tree of small files can feel awful compared to SMB on a VPN.

  4. Deciding whether you should use it
    Ask yourself:

    • Do you want “live edit on the server” more than offline sync and versions?
    • Are you OK with some slowness but want simple HTTPS access from anywhere?
    • Are the users relatively technical and able to cope with occasional quirks?

    If “yes” to most of those, WebDAV is a decent fit. If your mental model is “Dropbox, but self hosted,” then something like Nextcloud (using WebDAV internally) plus a sync client is closer to what you want.

  5. About clients and CloudMounter specifically
    Built‑in WebDAV in Windows / macOS is exactly as flaky as @cacadordeestrelas and @mikeappsreviewer hinted. For serious use, a dedicated client matters.

    CloudMounter is worth calling out here because it attacks the real usability problem: it mounts remote storage as a drive, so you just use Finder or File Explorer.

    Pros of CloudMounter in this context:

    • Treats WebDAV as a normal drive without juggling a separate transfer UI.
    • Also speaks SFTP and various cloud APIs, so you get a unified way to access “home server via WebDAV” plus “cloud stuff” in one place.
    • Per‑service encryption option can help a lot if you do not fully trust every endpoint.
    • Integrates nicely into daily workflows for non technical users: “here is your new drive, work in it like any other folder.”

    Cons to be aware of:

    • It is not a sync tool; if you wanted Dropbox‑style local mirroring with offline access and auto versioning, this is not that.
    • Performance still ultimately depends on WebDAV and your network. CloudMounter can smooth some rough edges, but it cannot turn WebDAV into LAN‑speed SMB.
    • It adds another proprietary layer between you and the raw protocol. Not usually a big deal, but worth noting if you prefer minimal stacks.

    Alternatives mentioned by others in spirit:

    • Classic two‑pane clients that support WebDAV and SFTP are great if you are happy with “manual transfer” workflows.
    • Other file managers with protocol support can work well, but they often feel less integrated than a drive‑mount approach.

  6. Practical take

    • Use WebDAV if your primary goal is “secure remote folder over HTTPS that I can open directly from apps.”
    • Wrap it with something like CloudMounter if you want that folder to behave like a native drive and avoid the OS’s clunky built‑in WebDAV.
    • If your real need is “easy sharing, versions, and offline copies,” you are looking for a sync platform first, protocol second. In that case you can let WebDAV exist quietly behind the scenes and not think of it as the main feature.