Ports Used by Files.com
Files.com uses a standard set of ports that users and systems use for connecting. Which ports are used depends upon the type of connections being made. Any API or web connections will use port 443, while protocol-based access uses different ports depending upon the protocol.
If your network restricts inbound or outbound access by port, refer to the table below when configuring connectivity. Each protocol uses specific ports for control and data channels.
| Protocol / Service | Port(s) | Direction | Description |
|---|---|---|---|
| HTTPS / API / Web Interface | 443 | Inbound | Used by the Files.com web app, Desktop App, CLI, SDKs, and REST API |
| FTP(S) (Control) | 21 | Inbound | Standard FTP command channel |
| FTP(S) (Data) | 40000–50000 | Inbound | FTP data passive channel range |
| FTPS (Implicit) | 990 | Inbound | Implicit FTPS control channel |
| FTPS (Alternate) | 3021 | Inbound | Alternate explicit FTPS command port |
| FTPS (Implicit Alternate) | 3990 | Inbound | Alternate implicit FTPS command port |
| SFTP | 22 | Inbound | Secure File Transfer Protocol (SFTP) command and data channel |
| SFTP (Alternate) | 3022 | Inbound | Alternate SFTP port |
| AS2 (HTTP / HTTPS) | 443 | Inbound | Used for AS2 connections |
| WebDAV | 443 | Inbound | WebDAV access via HTTPS |
| Outbound Connections (all protocols) | Dynamic | Outbound | Used by Files.com for Remote Servers, SMTP, LDAP, and Webhooks |
If your firewall inspects or limits outbound connections, configure it to allow traffic for the ports listed above.
Get The File Orchestration Platform Today
4,000+ organizations trust Files.com for mission-critical file operations. Start your free trial now and build your first flow in 60 seconds.
No credit card required • 7-day free trial • Setup in minutes