A Global News Organization Replaced Its Photo Desk’s FTP Server With Files.com Without Pausing Production or Changing Its Publishing Pipeline

A global news organization runs a newsroom that spans bureaus around the world and produces thousands of stories a day for its own platforms and hundreds of syndicated publications. The visual side of that operation is a business in its own right: an international network of photographers whose images are licensed by media companies around the world.

News photography is deadline work. A frame from the field is only worth having while the story is still live, so the organization's photographers transmit directly from the camera. And because the newsroom runs around the clock across the Americas, EMEA and APAC, the path from camera to newsroom has to work at any hour, wherever in the world the duty photo editor happens to sit.

The Photo Desk Ran Its Own Inbound FTP Server

For years that path was a server the news organization ran itself. Photographers in the field transmitted images from their cameras over FTP directly into the newsroom's in-house storage. Every photographer account was set up by hand, one at a time. Delivery was coordinated manually. And the newsroom carried the operating burden of an externally facing file server that could never be down: a transmission problem during coverage on another continent was the photo desk's problem to triage, at whatever hour it surfaced.

Three facts made the obvious fixes unavailable. Cameras dictate the protocol: a Sony A9 transmits over FTP, and there is no client to install or portal to open on a camera body, so whatever received those files had to speak FTP, FTPS and SFTP natively. The systems behind the server could not be disturbed: images flow from the inbound servers into Photo Mechanic and the newsroom's asset management system on their way into articles and video, and that publication pipeline had to keep running. And there was no window for a synchronized cutover, because there is no moment when a global newsroom's photographers are all idle at once.

As the roster of transmitting photographers grew, hand-built accounts and hand-coordinated delivery stopped scaling. What the news organization needed was a managed inbound layer: something that accepted native camera protocols, handed every file to the existing internal servers unchanged, could be adopted one photographer at a time, and came with round-the-clock support so the newsroom stopped being its own file-transfer operations team. The organization's visual media team selected Files.com to be that layer.

A Managed Perimeter in Front of an Untouched Pipeline

Files.com became the perimeter, and the newsroom's own infrastructure stayed the backend. The team connected its internal SFTP servers to Files.com as a Remote Server mount, making a folder on Files.com a live window onto the same storage the newsroom had always used. Nothing was migrated, and nothing downstream moved.

Each photographer now has an individually assigned folder with write-only permission. A photographer can transmit into that folder and do nothing else: no browsing, no downloading and no view of anyone else's work, so a credential lost in the field exposes nothing. Cameras connect over FTP, FTPS or SFTP exactly as they did before, with nothing new installed in the field.

The moment a file lands, a Files.com Automation moves it through the mount onto the newsroom's internal servers, renaming it with a prefix that records how it arrived. The file disappears from the intake folder and becomes immediately available to Photo Mechanic and the asset management system, exactly where those systems have always picked it up. The prefix lets editors distinguish images arriving through Files.com from those reaching the newsroom's servers by other routes.

The same per-user template eliminated hand-built onboarding. The team cloned a template user carrying the correct root folder and write-only permission, then used Files.com's bulk CSV import to create photographer accounts, with each folder created automatically.

Cut Over One Photographer at a Time, During Live Coverage

The migration ran during live production, because it had to. The team first tested the mount, preliminary folder structure and a live FTP upload from a camera with one photo editor. Photographers then moved individually, each switching as they were ready.

When the team later standardized the workflow around individual folders and origin prefixes, it again validated the design on a single account before rolling it out across every photographer. Configuration changes were scheduled off-hours to avoid interrupting active camera sessions, and the old shared permissions came away only after the last photographer had moved. Production never paused.

Proven on the State of the Union, Four Weeks After the Prototype

With the Files.com workflow in production, the news organization replaced a self-run inbound perimeter with a managed transmit path, and the difference showed up in weeks rather than quarters.

• Photo transfers for State of the Union coverage ran on the new workflow in March 2024, roughly four weeks after the first prototype was built. The system was production-proven on one of the biggest nights of the political photo calendar.
• The self-managed FTP server is retired. A duty photo editor on another continent no longer inherits a server problem in the middle of the night. The round-the-clock burden of keeping an externally facing file path alive moved off the newsroom and onto Files.com, whose support is staffed 24/7 to match a photo desk that never closes.
• All three regional desks, in the Americas, EMEA and APAC, now run on the same path.

The Newsroom Got Out of the File Server Business

Today a photographer raises a camera at a live event, transmits, and the frame is on the newsroom's own servers moments later, with Files.com doing the receiving, routing and renaming in between. Nobody hand-builds an account when a new photographer joins.

The lesson travels. An externally facing file server can be retired without touching anything behind it. Files.com mounted the newsroom's existing internal servers as the backend and took over the perimeter, so the publication pipeline never noticed the change. And because photographers moved one at a time, neither did the news.