● Camera networking / 002
FTP vs FTPS vs SFTP for cameras: what actually changes?
Compare camera FTP, FTPS, and SFTP encryption, ports, passive data connections, certificates, SSH host keys, and model-specific support.
- Published
- Reading time
- 10 minutes
- Source policy
- Primary / official
The practical answer
Use SFTP when the exact camera supports it and field testing confirms the host-key flow. Use explicit FTPS when SFTP is unavailable but the body supports FTP over TLS. Keep unencrypted FTP as a narrowly controlled compatibility path—not the default for credentials or media sent across the public internet.2,4,6
Similar menu labels hide different transports.
FTP is the original file-transfer protocol with separate control and data connections. FTPS adds TLS to FTP through the extensions defined by RFC 4217. SFTP is a different file-transfer protocol carried over SSH; it is not “FTP with SSH turned on.”1,4,6
| Protocol | Typical control port | Encryption | Network behavior | Camera-side trust |
|---|---|---|---|---|
| FTP | 21 | None by default | Separate control and data connections; passive data ports matter | Username and password |
| Explicit FTPS | 21 | TLS negotiated with AUTH TLS | Keeps FTP’s separate data connection model | TLS certificate behavior varies by camera |
| SFTP | 22 | SSH transport | One SSH connection carries file operations | SSH authentication / host-key behavior varies by camera |
FTP-family ingest is a firewall problem as well as a login problem.
The FTP specification separates the control connection from the data connection that carries directory listings and files. In passive operation, the server supplies an address and port for the client to open. A production gateway therefore needs a deliberate passive-port range, public address advertisement, firewall rules, and per-session isolation.1,3
FTPS protects FTP rather than replacing its connection model. RFC 4217 defines AUTH TLS and protection levels for the data connection, so testing must confirm both authentication and the actual media channel are protected.4
Encryption is only one part of a safe ingest endpoint.
The IETF’s FTP security guidance documents password guessing, credential capture, bounce attacks, and port theft among the protocol’s risks. TLS or SSH protects transport, but the service still needs unique credentials, rate limits, upload quotas, safe filenames, media validation, tenant-scoped storage, and revocation.2
Per-source credentials
Do not share one event-wide login across freelancers. A leaked password should revoke one source, not the entire production.
Upload-only permissions
The camera should not list or read another source’s files. Treat path traversal and filename collisions as hostile input.
Short retention
Staging is a delivery buffer. Set lifecycle deletion and surface failed routes before media expires.
Audit the data channel
A successful FTPS login does not prove the transfer channel used the intended TLS protection level.4
Read the exact body and firmware guide.
Canon documents FTP, FTPS, and SFTP choices on the EOS R5 Mark II. Nikon documents FTP, FTPS, and SFTP server types on the Z6III. That evidence applies to those models and documented firmware—not to every body from the brand.7,8
Some camera menus also impose protocol-specific setup: passive mode, root certificates, SSH login choices, proxy settings, or a fixed sequence for entering the server and port. The safest rule is simple: select the protocol the official manual names, then reproduce it against the production endpoint before assignment day.7,8
Frequently asked questions
01Are FTPS and SFTP the same thing?+
No. FTPS is FTP secured with TLS. SFTP is the SSH File Transfer Protocol carried over SSH. They use different negotiation, trust, and server implementations.4,6
02Which ports do camera FTP, FTPS, and SFTP use?+
FTP and explicit FTPS commonly begin on TCP port 21; SFTP commonly uses the SSH port, TCP 22. FTP and FTPS also negotiate a separate data connection. Always use the custom port issued by the endpoint when one is provided.1,4,5
03Is plain FTP acceptable for a camera?+
Only as a constrained compatibility mode where the network and risk are understood. FTP does not protect credentials or content by default, and the IETF documents multiple protocol-level security concerns. Prefer SFTP or FTPS when the body supports them.2
Official sources
Sources were reviewed on August 26, 2026. Vendor interfaces and documentation can change; follow the linked source and re-test the exact production workflow.
- 01IETF / RFC EditorRFC 959 — File Transfer Protocol ↗
- 02IETF / RFC EditorRFC 2577 — FTP Security Considerations ↗
- 03IETF / RFC EditorRFC 2428 — FTP Extensions for IPv6 and NATs ↗
- 04IETF / RFC EditorRFC 4217 — Securing FTP with TLS ↗
- 05IETF / RFC EditorRFC 4253 — The Secure Shell (SSH) Transport Layer Protocol ↗
- 06IETF DatatrackerSSH File Transfer Protocol, draft-ietf-secsh-filexfer-13 ↗
- 07
- 08