FTP, FTPS, and SFTP

ZenTransfer accepts uploads over plain FTP, FTPS (FTP over TLS), and SFTP (SSH File Transfer Protocol). Each protocol has tradeoffs around camera support, security, and network compatibility.

Quick comparison¶

Plain FTP¶

The original protocol. No encryption — credentials and file contents traverse the network in plaintext.

When to use: when the camera does not support encrypted variants. Most pre-2018 cameras only do plain FTP.

Risks: anyone on the same network can intercept credentials. ZenTransfer mitigates this by issuing upload-only temporary passwords — even if intercepted, the password cannot read your settings or download files from your account. Still, prefer FTPS or SFTP where possible.

Configuration:

• Host: ftp.zentransfer.io
• Port: 21
• Username: from your dashboard
• Password: from your dashboard
• Mode: passive

FTPS¶

FTP over TLS. Two flavours:

Explicit (FTPES) — the connection starts as plain FTP on port 21, then upgrades to TLS via AUTH TLS. Most cameras use explicit.

Implicit — the connection is TLS from the first byte, on a separate port (990).

Configuration:

• Host: ftps.zentransfer.io
• Port: 21 (explicit) or 990 (implicit)
• Username / password from dashboard
• Mode: passive
• Encryption: TLS

Certificate warnings on cameras. Some older camera firmware ships with outdated root certificate stores and rejects modern TLS certs. If your camera refuses to connect to FTPS:

• Update the camera firmware
• Check the manufacturer's site for a downloadable root CA bundle
• Fall back to SFTP or plain FTP if neither helps

See the FAQ entries on FTPS certificates for specific camera workarounds.

SFTP¶

SSH File Transfer Protocol. Not "FTP over SSH" — a different protocol that uses SSH for both transport and operations. Single port, encrypted, firewall-friendly.

Configuration:

• Host: sftp.zentransfer.io
• Port: 2222
• Username / password (or key) from dashboard
• Mode: not applicable (no separate data channel)

Best for: networks behind aggressive firewalls (some venues, corporate guest Wi-Fi). SFTP is one TCP connection on one port — much less to go wrong than FTP/FTPS's control + data channel split.

Limitation: fewer cameras support SFTP than FTP/FTPS. Check your camera manual.

Choosing on the day¶

Picking a protocol at the venue, in priority order:

1. SFTP if your camera supports it — most resilient to firewalls
2. FTPS if your camera supports it and accepts the cert
3. Plain FTP as fallback when nothing else works

The dashboard credentials are the same across all three protocols — only the host and protocol change.

Edge node hostnames¶

You can lock onto a regional edge for any protocol. See Edge nodes.

The default ftp.zentransfer.io / ftps.zentransfer.io / sftp.zentransfer.io route via DNS to the nearest healthy node.

Outbound FTP destinations¶

The protocol choice also applies when configuring outbound FTP destinations under /u/ftpservers — pick the protocol the recipient's server supports. See FTP destinations.

Common mistakes¶

• Camera set to active mode behind NAT — uploads hang
• FTPS implicit on port 21 — should be 990 for implicit
• Plain FTP on a network that intercepts it — credentials exposed
• Wrong hostname for the protocol — ftps.zentransfer.io is FTPS-only; SFTP needs sftp.zentransfer.io

Related reading¶

• Connecting on location
• Supported cameras
• Edge nodes