WebDAV

Mount a SuperFiles bucket as a network drive in macOS Finder, Cyberduck, or rclone.

WebDAV

SuperFiles exposes a WebDAV endpoint at /webdav. Mount any bucket as a network drive — no additional software needed on macOS.

WebDAV supports DAV class 1 and class 2 (including LOCK/UNLOCK), which is required for full read/write access from macOS Finder.

Mount in macOS Finder

Working URL format

https://api.superfiles.montr.online/webdav/<bucket-slug>/

Replace api.superfiles.montr.online with your self-hosted API domain. The trailing / is required.

1. Open Finder
2. Press ⌘K or go to Go → Connect to Server…
3. Enter the WebDAV URL for your bucket:

   https://api.superfiles.montr.online/webdav/my-bucket/

4. Click Connect
5. When prompted for credentials:
   • Username: anything (ignored — can be your email or just user)
   • Password: your SuperFiles API key (sf_live_...)

The bucket appears as a mounted volume in Finder’s sidebar under Locations.

Tip: To mount at login, add the server to System Settings → General → Login Items after the first successful mount.

Mount with Cyberduck / Mountain Duck

1. Create a new WebDAV (HTTPS) connection
2. Server: api.superfiles.montr.online
3. Path: /webdav/my-bucket/
4. Username: anything
5. Password: your API key (sf_live_...)

Mount with rclone

# ~/.config/rclone/rclone.conf

[sf-media]
type = webdav
url = https://api.superfiles.montr.online/webdav/my-bucket
vendor = other
user = any
pass = <rclone-obscured API key>

Obscure your API key first:

rclone obscure sf_live_xxxxxxxxxxxxxxxxxxxx

Then sync a local folder:

rclone sync ./local-photos sf-media: --progress

Supported operations

Gotchas

API key permissions

The API key used as the password must have write (or admin) permission to upload files. A read-only key works for browse and download but Finder will fail silently when you try to copy a file in.

Team API key vs user token

The WebDAV endpoint uses a team API key (sf_live_...) as the HTTP Basic password. It does not accept personal user tokens (sf_user_...). Create a dedicated API key in Settings → API Keys with the write permission and the specific bucket(s) you want to mount.

Trailing slash

Finder and most WebDAV clients require the URL to end with /:

✅  https://api.superfiles.montr.online/webdav/my-bucket/
❌  https://api.superfiles.montr.online/webdav/my-bucket

Lock persistence

Locks are held in process memory and do not survive API restarts. This is sufficient for macOS Finder compatibility. For collaborative editing workflows use the REST API directly.

Virtual folders

SuperFiles has no real folder entities. Folders visible in WebDAV are derived from /-separated key prefixes. MKCOL (create folder) is a no-op — the folder appears automatically when you upload a file into it.

Large files

PUT streams directly to the blob store with no buffering. There is no practical file size limit other than available disk space and your plan’s quota.

Self-hosted deployment

If the API is running behind a reverse proxy, ensure:

• proxy_request_buffering off; is set in nginx (required for streaming PUT uploads)
• The host allows PROPFIND, LOCK, UNLOCK, MKCOL, COPY, MOVE HTTP methods

API key vs personal user token summary

Use team API keys for programmatic storage access (WebDAV, S3, REST storage API). Use personal user tokens for user-identity API calls (/api/auth/me, /v1/me/teams, etc.).