Files.com accepts FTP and FTPS connections from applications, devices, and trading partners that require FTP compatibility. FTPS encrypts the FTP connection with TLS. Files.com requires encryption by default; plain FTP is an explicit compatibility option for systems that cannot use encryption.

When you can choose the transfer tool, prefer a Files.com app or SDK for parallel transfers and built-in retries. Use FTP or FTPS when the connecting system requires it.

Terminology

In Files.com settings and documentation, FTP covers both plain FTP and encrypted FTPS unless a setting explicitly says otherwise. Explicit FTPS, also called FTPeS, starts a connection and then negotiates TLS. Implicit FTPS begins TLS immediately. Both are supported; Explicit FTPS is the recommended default.

SFTP is a separate protocol that runs over SSH. An SFTP connection requires SFTP settings, not an FTPS security mode.

Connecting an FTP Client

The recommended connection is Explicit FTPS on port 21, or alternate port 3021, with Passive mode. FTP uses separate command and data connections, so a successful login does not by itself confirm that transfers can pass through your firewall. Configure the connection profile with the client operator and network administrator so both connections are permitted.

Administrators and integration developers also need to account for how the client sends files. Transfer mode can affect file contents, and an interrupted upload can leave a partial file. Establish the client's completion behavior before using its uploads as inputs to an automated process.

If Files.com needs to connect to an external FTP or FTPS server, configure an FTP Remote Server.

FTP Service

Files.com operates proprietary FTP server software built and maintained in-house by full-time employees. The service is hosted in eight geographic regions, with a highly available pool of servers in each region rather than a single server assigned to each connection.

RFC Compliance

Files.com implements FTP in accordance with the relevant IETF RFCs, primarily RFC 959 and related extensions. The server is compatible with applicable FTP standards, supports plain FTP and FTPS with Active or Passive data connections, and is tested regularly against popular clients and libraries for interoperability. Some legacy FTP features vary between vendors; the Files.com service follows the defined protocol commands and structures.