The traditional approach to distributing photos to multiple recipients means uploading the same file more than once: once for each wire service and possibly once for your own backup. Each upload is a separate operation that takes time and requires manual attention.
ZenTransfer inverts this. Every file that arrives — whether from your camera's FTP or from the desktop app — is forwarded to every active destination in parallel from a single upload. You configure the destinations once and control which are active from your phone.
Destination types
FTP servers — add any number of FTP destinations by hostname, port, credentials, and target folder. Most wire services and newsrooms receive photos over FTP. ZenTransfer forwards to all active FTP destinations in parallel as soon as each file is processed.
Cloud storage — native integrations with Google Drive, Dropbox, OneDrive, Amazon S3, Azure Blob Storage, Google Cloud Storage, and Adobe Lightroom. Each cloud destination can be toggled independently.
Email recipients — for editors and clients who do not operate an FTP inbox, ZenTransfer sends a notification email with a traceable download link to the full-resolution file. Downloads are logged. You can configure multiple email recipients, each controllable independently.
Zapier — files trigger a Zapier webhook on arrival, opening any of Zapier's 5,000+ connected apps as a downstream destination.
Toggling destinations from your phone
All destinations in ZenTransfer can be enabled or disabled from any browser, including your phone. This matters in practice because your destination list changes by assignment.
Working a game that goes to three wire services and your personal archive? Enable all four. Filing a single exclusive to one client? Disable everything else. Switching mid-assignment is immediate — no need to touch the camera settings or the desktop app.
A typical destination configuration might look like:
- Agency ingest server — enabled when shooting for the agency
- Reuters/Getty/AP/Etc/Etc FTP — enabled for accredited events, disabled otherwise
- Editor email — enabled when working a specific freelance commission
- Customer FTP server - for exclusive assignments
- Google Drive personal archive — always enabled
The camera profile never changes. You manage the routing from your phone while the camera runs exactly the same FTP configuration it always does, wherever you are in the world.
Simultaneous delivery to newsdesks
Wire photography works under deadlines where the difference between first and second can determine whether a photograph is used. ZenTransfer's delivery is parallel, not sequential: all active FTP destinations receive the file at the same time, not one after another. There is no queue where the third destination waits for the first to finish.
This means you are not choosing which desk gets the file first. Every active destination gets it simultaneously.
Email delivery and traceable links
When ZenTransfer delivers to an email recipient, the notification includes a traceable download link. The link points to the full-resolution file and is unique to that delivery. When the recipient clicks and downloads, the event is logged against your account.
This gives you a record: which editor downloaded which file, and when. For freelance work involving rights-managed images, that log is useful documentation.
Email delivery integrates with the same destination toggle system as FTP and cloud. You can have a standing list of commissioning editors configured and enable or disable any of them per assignment without changing the configuration.
Using the desktop app for bulk delivery
When working from a laptop — in a press room, a media zone, or after returning from the field — the ZenTransfer Desktop App provides drag-and-drop delivery through the same destination system. Drop a folder of selects into the app, and ZenTransfer forwards every file to every active destination with the same metadata embedding that applies to camera uploads.
The desktop app is free and open source, and can also be used without the ZenTransfer.io service. Your destination and metadata configuration is shared between the camera FTP relay and the desktop app — configure once, use from anywhere.
A game-day example
A photojournalist covering a football match might configure ZenTransfer for the assignment as follows:
- Getty editorial FTP — enabled
- Reuters editorial FTP — enabled
- Personal Google Drive archive — enabled
- Client email (the sponsoring brand's PR contact) — enabled for the post-match session only
During the match, the camera transmits to ZenTransfer over a 5G hotspot. Every frame that crosses ZenTransfer is immediately forwarded to Getty's FTP, Reuters' FTP, and the personal archive simultaneously. At half-time, the photographer reviews the card on the phone — no action needed; the delivery is already running.
After the final whistle, during the post-match session, the client email destination is enabled from the phone. From that point, files also go to the brand contact. After the post-match session ends, the email destination is disabled, and the archive-only configuration continues for any cleanup uploads.
No laptop involved. No FTP client opened. No new FTP username or password to enter into the camera.
From $3.75 per month
Camera-to-cloud delivery for photojournalists. No laptop required.
