WebDAV

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

WebDAV

SuperFiles exposes a WebDAV endpoint at /webdav. You can mount any bucket as a network drive — without installing any additional software on macOS.

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

Mount in macOS Finder

Open Finder
Press ⌘K or go to Go → Connect to Server…
Enter your WebDAV URL:

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

For self-hosted installations, use your API’s public URL:

https://superfiles-api.example.com/webdav/my-bucket/

Click Connect
When prompted for credentials:
- Username: anything (e.g. your email)
- Password: your SuperFiles API key (sf_live_...)

The bucket will appear as a mounted drive in Finder and in the Locations sidebar.

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

Mount with Cyberduck / Mountain Duck

Create a new WebDAV (HTTPS) connection
Server: api.superfiles.montr.online (or your self-hosted host)
Path: /webdav/<bucket-slug>/
Username: anything
Password: your API key

Mount with rclone

Configure an rclone remote:

# ~/.config/rclone/rclone.conf

[superfiles-media]
type = webdav
url = https://api.superfiles.montr.online/webdav/media
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 superfiles-media: --progress

Supported operations

Operation	Support
Browse / list files	✅
Download files	✅
Upload files	✅
Delete files	✅
Create folders	✅ (virtual)
Copy files	✅
Move / rename	✅
Lock files (macOS write)	✅ (in-memory stub)

Notes

Virtual folders — SuperFiles has no real folder entities. Folders visible in WebDAV are derived from /-separated key prefixes. Creating a folder via MKCOL is a no-op; the folder appears automatically when you upload a file into it.
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 instead.
Large files — PUT streams directly to the blob store with no buffering. There is no practical file size limit other than available disk space.