Clients & Protocols
Files.com gives people, applications, and trading partners access to the same file tree through client apps, APIs, and file-transfer protocols. Choose a connection method based on who initiates the work and what their environment supports. The account's permissions and allowed connection methods determine what it can access.
Native Client Apps
The Web Interface is the starting point for working with files in a browser, sharing content, configuring your site, and reviewing activity. It requires no client installation.
The Desktop App brings Files.com into Windows File Explorer or macOS Finder for opening and editing files in local applications. Its Turbo Transfer Mode handles bulk uploads and downloads, while Sync Mode runs a one-time transfer between a local folder and Files.com. Preferred Apps for File Transfer helps you choose between these modes and other transfer tools.
The Mobile App provides file access on iOS and Android, including uploads of photos and videos captured on the device. The Outlook Add-In sends files as Snapshot Share Links from Classic Outlook for Windows and is included with the Windows Desktop App.
Scripts and Applications
Use the Command Line Interface (CLI) App for shell scripts, batch transfers, and administrative commands on Windows, macOS, or Linux. Use the SDKs and REST API to build file operations and platform administration into your own application. Best Practices for Integrating with Files.com covers these choices alongside iPaaS connectors, Terraform, and the MCP Server.
Other Client Apps covers tools such as Rclone and Arq Backup when they are already part of your workflow.
Protocols
Use a protocol connection when a partner, application, or device requires that interface.
| Connection | When It Fits |
|---|---|
| SFTP | A partner or application requires file transfers over SSH. |
| FTP and FTPS | An existing system requires FTP. Files.com requires encrypted FTPS by default. |
| AS2 | Trading partners exchange business documents using agreed identities, certificates, and Message Disposition Notification receipts. |
| S3-Compatible Endpoint | A tool uses the S3 API and can connect to a custom endpoint. |
| WebDAV | A client requires WebDAV access over HTTPS. For desktop file access on Windows or macOS, prefer the Desktop App. |
SFTP, FTP/FTPS, WebDAV, and the S3-compatible endpoint let clients connect to Files.com. When Files.com needs to connect to storage elsewhere, configure a Remote Server. Use the On-Premise Agent to connect local disks or network shares to Files.com for centrally managed access and recurring transfers.