Destinations

FTP Servers

Configure wire-service, newsroom, or client FTP inboxes as automatic delivery targets.

Last updated 2026-05-25

On this page

ZenTransfer can deliver to any standard FTP, FTPS, or SFTP server you have write credentials for. This is how files reach wire services, newsroom desks, agency archives, and client inboxes that expose an FTP endpoint.

What you need

For each destination:

  • Hostname
  • Port
  • Protocol (FTP, FTPS, or SFTP)
  • Username and password (or key, for SFTP)
  • Target folder / path on the destination
  • Active or passive mode preference (most destinations are passive)

These are supplied by the recipient — the wire's tech desk, the newsroom's photo editor, or the client's IT.

Setup

Step 1: Add an outbound FTP server

  1. Log in to your Dashboard
  2. Navigate to FTP Servers at /u/ftpservers
  3. Click Add server
  4. Fill in the connection fields: - Friendly name (e.g. "Reuters - Sports Desk") - Hostname and port - Protocol - Username / password - Folder path (leading slash if absolute) - Passive mode toggle
  5. Save

Step 2: Test the connection

Use the Test button on the server detail page (/u/ftpserver/<id>). The test attempts a small file upload — confirm it succeeds before relying on the destination for a live job.

Step 3: Enable the destination

Each FTP server has an enable toggle. When enabled, the destination receives every file that passes through auto-transfer (camera FTP, Desktop, mobile, browser, guest, HTTP, API).

You can also leave it disabled for auto-transfer and select it manually in the Browser's Transfer panel.

Active vs passive mode

Most modern destinations use passive mode. Active mode requires the destination to open a connection back to ZenTransfer, which usually fails through NAT.

If the recipient's documentation says "active mode required," set the toggle accordingly. If unsure, try passive first.

Loopback restriction

ZenTransfer blocks outbound FTP that points back at ZenTransfer's own hostnames. This prevents accidental loops where one ZenTransfer account routes to another's upload server.

Protocol notes

ProtocolWhen to use
FTPWhen the recipient only supports plain FTP
FTPS (explicit)Default if the recipient supports it — encrypted; easier through firewalls
FTPS (implicit)When the recipient explicitly requires implicit mode (port 990)
SFTPSingle-port encrypted protocol over SSH; favored by security-conscious desks

Folder layout

The folder you specify is where ZenTransfer writes the file. Most wire desks require a specific path — get this from their tech contact. Use a leading slash for an absolute path (e.g. /ingest/freelance/<your-name>/).

Filename behaviour

The processed filename (after rename, if configured) is written to the destination. Some desks expect specific filename patterns — set the rename template accordingly per wire.

Common mistakes

  • Wrong port — FTPS implicit uses 990, not 21
  • Missing passive mode when the destination is behind NAT — uploads time out
  • Folder path missing trailing slash when the destination interprets the last segment as a filename
  • Stale credentials — wires rotate access keys occasionally; the test button surfaces failures fast
  • Active mode chosen when the destination is passive-only — connection establishes but transfer hangs

Bulk wire configuration

If you file to many wires, set up each as a separate FTP server, then toggle them on/off per assignment. The dashboard transfer stats give you per-destination success/failure breakdowns.

See News agency workflow for the operational pattern.

Related articles