SFTP for newsrooms: large-file intake for media teams
The short version
- A newsroom's raw material arrives as enormous files: photo archives and video from contributors in the field, print-ready packages to the printer, advertising assets from agencies, and finished packages out to partners. Mail systems and upload forms fail on exactly these files.
- One SFTP endpoint gives every flow a lane: a drop folder per contributor, a delivery folder per printer and partner, resumable transfers that survive field connections, and webhooks that alert the desk the moment a file lands.
- On managed SFTPGo hosting the endpoint is €9 a month with unlimited accounts, so the whole contributor roster files through one flat-priced host instead of a rotation of consumer file-sharing links.
- The web client covers contributors without software: a browser, a login, their drop folder, and a multi-gigabyte upload that resumes when the hotel wifi drops.
The intake problem newsrooms actually have
Deadlines make file intake violent. A contributor returns from an assignment with forty gigabytes of video and RAW photography on cards that need formatting tomorrow. The printer's imposition system wants tonight's edition as one PDF that no email system will relay. An agency delivers a campaign's assets at 5 p.m. and the traffic desk needs them ingested before the morning run. And somewhere a partner expects today's finished packages on schedule, every day, without exception.
The consumer-grade answers fail in turn: mail systems cap attachments at megabytes, browser upload forms time out on gigabytes and restart from zero on failure, and consumer file-sharing links expire exactly when the archive needs the file. Professional media solved this decades ago in the broadcast and print backbone with scheduled, resumable, logged transfer, and that machinery is now available to any newsroom at any size.
The newsroom's exchange map
| Flow | Direction | Counterparty | Typical size |
|---|---|---|---|
| Assignment media: photos, video, audio | In, one folder per contributor | Staff, stringers, agencies | Hundreds of MB to tens of GB |
| Print-ready editions and inserts | Out, per printer | Print providers | Multi-GB PDFs |
| Advertising assets | In, per agency or advertiser | Agencies, direct clients | Spots, banners, rich media |
| Finished content packages | Out, per partner | Syndication partners, subscribers | Scheduled, structured |
| Masters and editions for archive | Internal, to the archive folder | Your own archive | Everything, forever |
One endpoint models all five flows with one account per counterparty. Contributors see only their drop folder; the printer sees only its delivery lane; agencies drop into their own directories; and the desk's virtual-folder view maps every lane into one pane with exactly the permissions each role should have.
Field transfers that survive reality
The protocol's quiet superpower for journalists is resumability. An SFTP transfer that drops at 80 percent on a congested press-room connection resumes at 80 percent, rather than restarting the way browser uploads do. For a contributor on hotel wifi pushing a 12 GB video package, that is the difference between filing before the deadline and missing the edition. Combined with per-contributor quotas and bandwidth that a small endpoint handles comfortably, the field-to-desk lane becomes boring, which in a newsroom is the highest praise.
Contributors without any software use the web client instead: browser open, login, drag the card's folder into their drop zone. The upload is chunked and resumable, the desk gets an alert when it completes, and nobody burns an afternoon to a progress bar. For sources and one-off senders who should not hold accounts, secure share links with passwords, expiry, and download limits cover the sensitive handoff.
Print delivery and partner lanes
Print providers and syndication partners are the scheduled counterparties: the edition PDF goes out on a timetable, the partner package lands on theirs. These lanes reward exactly what a structured endpoint provides: a stable folder the printer maps once, credentials that do not rotate with staff changes, an audit trail that answers "we sent the inserts at 23:40" with a timestamp, and webhooks that notify the desk when a partner's daily pickup has actually happened. The service-level conversation stops being a scroll through sent-mail folders.
Handling sensitive material honestly
Newsrooms carry material that matters: embargoed editions before release, advertiser assets under contract, and sometimes source-related files whose protection is an ethical obligation. The endpoint's contribution is precise and worth stating precisely: transfers are encrypted in transit, storage can be encrypted at rest, access is per account and per folder, every action is logged, and two-factor authentication covers the human logins. What it does not do is substitute for a source-protection protocol; if sources face adversary-grade threats, that is a specialist conversation the endpoint supports but does not replace.
The cost side for a publishing operation
A newsroom's account count is its contributor roster plus its partners, and that roster is exactly what per-user file services bill. The flat lane prices the host: €9 a month, unlimited accounts, 30 GB included with storage metered beyond it. Text and package traffic is trivial; the photo and video months meter, the ordinary months largely do not, and the whole file backbone costs less than one freelance photo assignment. The market's pricing models compared tier by tier are in managed file transfer pricing compared, and what running the underlying server costs on every path is the real cost of running SFTPGo.
Media teams already running open-source infrastructure will recognize the neighbors: the newsroom stack of publishing, editing, and coordination tools has a managed lane for each, and the file backbone is the missing one. The stack walkthrough is the open-source newsroom stack, and for one-off sends rather than recurring exchange, the ad-hoc send toolkit is the companion piece. Hands-on setup lives in the SFTPGo knowledge base.
Frequently asked questions
What does SFTP give a newsroom?
A single host for every large-file flow: contributors filing photos and video into their own drop folders, print editions going out to printers on schedule, advertising assets arriving from agencies, and finished packages delivered to partners. Every transfer is resumable, logged per account, and visible to the desk the moment it lands.
How do photographers file from the field?
With any SFTP client or the web client in a browser: they connect, see only their own drop folder, and upload the assignment. The transfer resumes where it left off if the connection drops, which is what makes multi-gigabyte field files deliverable from hotel and press-room connections.
Can a print-ready PDF be delivered this way?
Yes, that is one of the oldest uses of the pattern: the imposition-ready file, often multiple gigabytes, transfers to the printer's lane on schedule with no attachment ceiling and a logged delivery time. Print providers standardized on file transfer with their clients long ago.
How do agencies deliver advertising assets?
Each agency or direct advertiser gets their own inbound folder and credentials: spots, banners, and rich media land where the traffic desk expects them, with a per-account log replacing the hunt through email threads. Webhooks can notify the desk on arrival.
Is the endpoint suitable for embargoed material?
For embargo discipline, yes: access is per account and per folder, transfers are encrypted, and every download is logged, so an embargo breach leaves a trail. The endpoint supports source-protection practices, but a source facing a serious adversary needs a specialist protocol on top, not just secure transport.
What is the largest file the endpoint accepts?
There is no protocol ceiling: SFTP moves files of any size, resumably. The practical limit is the quota you set per account, which is the right place for a newsroom to cap a contributor's archive dump while leaving the edition PDFs unlimited.
Can one-off senders deliver without an account?
Yes, through secure share links generated in the web client: the sender receives a link that can carry a password, an expiry date, and a download limit, and the file lands in your intake without creating a permanent account. Recurring contributors get real logins instead.
How do syndication partners receive daily packages?
Each partner gets a delivery folder mapped once: your export job places the daily package on schedule, the partner's system or staff picks it up, and the log confirms the pickup. The lane never changes when your staff does, which is why partners prefer it over emailed attachments.
Do transfers survive bad connections?
That is the core advantage over browser uploads: SFTP resumes interrupted transfers at the point of failure, in both directions. On field connections this is the difference between a filed assignment and a refought upload, and it is why the protocol outlived every replacement attempted since.
Where do masters and editions get archived?
In archive folders on the same endpoint or, better, streamed to object storage: the server's S3-compatible backend can place each master directly into the archive bucket, keeping the endpoint light while the archive grows without bound.
How is a newsroom's file infrastructure priced?
On the flat managed lane, €9 a month with unlimited contributor and partner accounts and 30 GB included; heavy photo and video months meter storage beyond it. Per-user services instead bill the contributor roster, which grows with the newsroom's reach rather than its storage.
Who keeps the endpoint running overnight?
The managed lane exists for exactly that: updates, backups, monitoring, and human support are the provider's job, on a schedule newsrooms will recognize. Self-hosting the same open-source software is free, but then the 3 a.m. page belongs to the desk; every path is priced in the linked comparison.
How does this differ from a shared cloud drive?
The drive is a library; the endpoint is a loading dock. Intake lanes need per-counterparty credentials, completion events, resumable multi-gigabyte transfers, and delivery logs, and newsrooms use both: the drive to browse and collaborate, the endpoint to receive and deliver on deadline.
Sources
- Feature set: resumable transfers, per-user isolation, quotas, web client sharing, event webhooks, S3-compatible backend: github.com/drakkan/sftpgo README (viewed October 2026)
- Media file-exchange pattern (contributor intake, print delivery, partner distribution over scheduled transfer): standard publishing-industry practice, observed October 2026
- Pricing and inclusions: danian.co/sftpgo and danian.co/pricing
