Clients & Protocols

Files.com gives people, applications, and trading partners access to the same file tree through client apps, APIs, and file-transfer protocols. The right connection method fits the work and the environment doing it: someone editing a document on a laptop has different needs from a scheduled integration or a trading partner exchanging business records.

For people working with files, the choice affects how they open, edit, and transfer content. A browser needs no installation, while a desktop connection brings files into local applications. Moving a large collection of files also calls for different tools from opening one file at a time. Preferred Apps for File Transfer helps you choose a tool for that transfer work.

For developers and administrators connecting another system, start with what that system supports and who initiates the connection. An application built around an existing protocol may need to keep using it; a new integration can use the API or an SDK for file operations and site administration. The account's permissions and allowed connection methods determine what the connection can access.

These choices concern clients connecting to Files.com. When Files.com needs to connect to storage elsewhere, configure a Remote Server. Keeping that direction clear helps you choose the right setup instructions and identify which system needs credentials and network access. Use this section to establish a working connection, understand its behavior, and resolve problems in the client or protocol your workflow uses.