A Short History of Sending a File From One Computer to Another
"Sending a file" is such an ordinary phrase by now that it's easy to forget how many genuinely different mechanisms have hidden behind it over the decades — and how each one traded something away, or brought something back, rather than simply being a faster version of the last.
Sneakernet: the original file transfer
For a long stretch, moving a file from one computer to another meant moving physical media by hand — a floppy disk, later a CD or a USB drive, carried across a room or mailed across a country. It's since earned the half-joking name "sneakernet." Slow and manual, yes, but it needed no network connection at all between the two machines, a trade-off that's easy to overlook in hindsight and genuinely useful to notice.
FTP and the first networked transfers
File Transfer Protocol — one of the internet's oldest standards, still in use today — let two computers move files directly over a network for the first time, no physical media required. It was a genuine leap forward. It also demanded real technical comfort from whoever used it: server addresses, login credentials, a dedicated client application. Not something an ordinary person would reach for casually.
Email attachments made it casual
Attaching a file to an email brought file-sending to anyone who could already send an email — which, by the time it became common, was most people. The cost was the size ceiling this blog has covered elsewhere in detail, baked into email's original design for carrying text messages, not multi-megabyte files.
Peer-to-peer had its own, separate first act
Worth distinguishing from what came later: file-sharing networks in the early 2000s were also, technically, peer-to-peer — but built around public swarms of unknown participants sharing files broadly, not a private, deliberate connection between two specific people. That's a meaningfully different shape of system from the one-to-one, pair-with-a-specific-device model this blog has also covered, even though both get called "peer-to-peer."
Cloud storage centralized everything
Services built around a stored, shareable copy — upload once, hand out a link to anyone — solved the size problem convincingly and added real persistence: the file is just there, waiting, whenever someone gets around to downloading it. The cost was a copy of the file now living somewhere else indefinitely, by default, whether or not that persistence was actually needed for the task at hand.
Direct browser-to-browser transfer closes the loop
Modern peer-to-peer tools return to something closer to the original sneakernet idea: the file goes straight from one device to the other, with nothing in between holding a copy. But now it travels over a network instead of physical media, with no size ceiling to work around and no server-side copy left behind afterward — the convenience of a network transfer, without the persistence that cloud storage made the default.
The shape keeps changing, not just the speed
Each step in this history wasn't simply "faster than the last one." Each one traded away or deliberately brought back something specific — physical presence, a size limit, persistent storage, an account requirement. It's worth remembering, next time "just send it" sounds like a completely solved, unremarkable problem, that the mechanism behind those three words is still quietly evolving.
Related reading
Peer-to-Peer vs Client-Server: How File Sharing Actually Moves Your Data Cloud Storage vs Direct Transfer: Where Does Your Data Actually Go The Case for Ephemeral File Sharing: Nothing Left Behind