Why FTP Won't Die

Somewhere in your estate, a batch file older than everyone on the team logs into a server at two in the morning. It sends a password in the clear and works. FTP was born on a small, trusting network before the web existed. It predates most of the people who administer it. It has been declared dead more often than any protocol in networking. It is still running in the firmware of the device in the wiring closet and in a partner's mainframe job. It is in the nightly job nobody wants to touch because it has never failed. Understanding why is not nostalgia. It is the difference between managing the protocol and being managed by it.

This series takes the long view. It offers a short history of FTP told without a single date. It covers the honest reasons FTP persists (economics, mostly, not ignorance) and what that persistence quietly costs. It includes the family tree that settles the FTP, FTPS, SFTP confusion for good. It explores what the future of file movement looks like once the slide decks are put away. It also covers how to live with the FTP you cannot retire yet without it living with you.

Articles in This Series

• A Short History of FTP, Told Without Dates
  The article traces FTP's birth on a small, trusting network before the web existed. It covers the design choices that made sense then and the additions that patched them - passive mode, extensions, TLS. It also covers the separate lineage that gave us SFTP.
• Why FTP Persists: The Honest Reasons
  The article covers installed base, embedded devices, universal client support, and sheer simplicity. It also covers the it-works inertia of jobs nobody wants to touch. It explains persistence as economics, not ignorance.
• What FTP's Persistence Costs Organizations
  The article covers cleartext credentials, firewall pain, audit findings, support burden, and the migration debt that grows quietly. It measures these honestly so the retirement case is made with numbers rather than fear.
• The FTP Family Tree: FTP, FTPS, SFTP, and What Came After
  The article clears the naming confusion once and for all. It covers what each protocol inherited, what it fixed, and where the industry converged. It explains what the names on a partner's connection sheet actually mean.
• What the Future of File Movement Really Looks Like
  The article states the durable trends structurally: identity-centric access, APIs and object storage beside the old protocols, managed layers, event-driven flows. It covers what will still be true a decade from now: files, batches, and the need to move them.
• Living With FTP Responsibly While It Lasts
  The article covers containment for the FTP you cannot retire yet: internal-only exposure, segmentation, monitoring, and credential hygiene. It includes the migration plan kept ready on the shelf. This is the working admin's practical stance.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.