What is FTP and what replaced it?
FTP is a decades-old protocol for transferring files between a client and a server. It still works, but it requires software, credentials, and server maintenance, which is why most organisations now use browser-based transfer services instead.
How FTP works
A server exposes a directory, users connect with a dedicated client application and credentials, and files are copied in either direction.
It is efficient for bulk automated transfers, which is why it survives in engineering, print, and broadcast workflows.
Why organisations move away from it
- every external partner needs credentials and a client application
- plain FTP is unencrypted, and secure variants require correct configuration
- the server has to be maintained, patched, and backed up
- access rights are managed at the server level, not per delivery
- there is no simple link to send to a client who is not technical
What replaced it
| Requirement | FTP | Transfer service |
|---|---|---|
| Software on the recipient side | FTP client | Web browser |
| Credentials for each partner | Yes | No, a link is enough |
| Encryption | Only in secure variants | Standard, with optional end-to-end |
| Server maintenance | Yours | None |
| Per-delivery expiration | No | Yes |
| Collecting files from outsiders | Account per partner | Shared folder or upload link |
Keeping the FTP workflow without the server
The common FTP pattern is a place where partners drop material and where you collect it. That pattern maps directly onto a shared folder with write access, or onto a custom upload domain.
On MyAirBridge, a custom subdomain is available from the Pro plan, so clients upload at your own address and benefit from your paid transfer speeds without registering.
FAQ
Is FTP still used?
Yes, mainly in automated and legacy workflows. For human-to-human delivery it has largely been replaced by browser-based transfer services.
Is FTP secure?
Plain FTP transmits data without encryption. Secure variants exist but require correct server configuration, whereas transfer services encrypt by default.
What is the simplest FTP alternative for receiving client files?
A shared folder with write access, or your own upload address on a custom subdomain, so clients upload without accounts or software.
Summary
FTP still works but carries the cost of servers, credentials, and client software. Browser-based transfer with shared folders, upload links, and custom domains covers the same workflows with encryption by default and nothing for partners to install.