Files.com supports WebDAV file access over HTTPS for legacy applications and workflows that specifically require the protocol. We do not recommend WebDAV for most uses. For everyday desktop access and bulk transfers on Windows or macOS, use the Files.com Desktop App, which provides native file-browser integration and dedicated transfer tools.

The client determines how files are mounted, how credentials are supplied, and which operations and file sizes it can handle. Confirm those requirements before relying on an operating system's built-in client.

These connections let a client access files on Files.com. If Files.com needs to connect to an external WebDAV server, configure a WebDAV Remote Server.

Limitations

WebDAV file actions can require several round trips between client and server, making latency significant when browsing folders, editing files in place, or transferring many files. Native operating-system clients also impose their own limits. Review the Windows client requirements before choosing a native Windows mount.

Some WebDAV clients write files incrementally to support resuming transfers. A file can be visible while its contents are still arriving, and an interrupted transfer can leave that partial file in place. Use a completion-based handoff before automated processing picks up these uploads.

Connection Information

Use your site's HTTPS URL, https://SUBDOMAIN.files.com/, or its custom domain. Connecting by IP address is not officially supported.

Files.com offers WebDAV over HTTPS on port 443 only. Select WebDAVS or WebDAV (HTTPS) if your client asks for a protocol. Your client must support TLS 1.2 or later.

A firewall can allow ordinary HTTPS traffic while blocking WebDAV methods. If the connection fails, check network access and login settings.

Account Preparation

Before connecting with a username and password, sign in to the Files.com web interface and complete any required password change or initial two-factor authentication (2FA) setup. WebDAV clients cannot perform those enrollment steps. If 2FA is required, confirm that your method supports WebDAV and follow the protocol authentication instructions for supplying the code with your password.

For an unattended application, the same guide explains API key authentication, which does not require interactive 2FA. For everyday desktop access, use the Desktop App to complete supported sign-in methods through your browser.

Upload Completion and Workflow Handoffs

WebDAV clients that save a file across several requests rely on Files.com preserving the data received so far. This allows the client to resume without sending the entire file again. An empty or partially written file can therefore be visible during a normal upload. File presence alone does not establish completion, unlike an atomic upload.

An Automation, Sync, or Folder Setting can act on the saved data before the remaining writes arrive. GPG processing may receive an incomplete encrypted file, a transfer may deliver only part of the contents, or automatic renaming may assign a final name before the upload finishes.

Use a separate upload folder without automatic renaming or content processing, and exclude it from downstream transfers. Once the client confirms that the upload is complete, move the finished file into the pickup folder for the next workflow step. Configure that step to respond to the completed-file handoff, and have the producer stop changing the file once it is ready for pickup.

If the client supports temporary filenames, another option is to upload as report.csv.partial and rename it to report.csv only after all data is saved. Configure the consuming Automation or Sync to select the final name and exclude temporary names. The client must keep the temporary name until completion; a filename filter cannot determine completion on its own. A fixed scheduled delay also cannot establish completion, because an upload may take longer than expected or be interrupted.

For desktop uploads that need atomic delivery into a processing folder, use the Files.com Desktop App. If the destination uses external storage, review the Remote Mount limits on atomic uploads when designing the handoff.

WebDAV Server Details

Files.com tests its WebDAV implementation with the Litmus WebDAV test suite.