Who Created Downloading on the Internet? The Origins of File Transfer Technology

Downloading is so fundamental to how we use the internet that it's easy to forget it had to be invented. Every time you save a photo, install an app, or stream a song, you're benefiting from decades of protocol design, network engineering, and a few key moments in computing history. The answer to who "created" downloading isn't a single name — it's a layered story of protocols, institutions, and individuals building on each other's work.

Downloading Didn't Start With the Web

Most people associate downloading with browsers and the modern internet, but the underlying mechanics predate the World Wide Web by decades. Downloading, at its core, means transferring a copy of data from a remote system to a local one. That process was already happening in the early days of ARPANET, the U.S. Department of Defense-funded network that became the foundation of today's internet.

In the late 1960s and early 1970s, researchers on ARPANET were regularly transferring files between mainframe computers at universities and research institutions. This wasn't glamorous — it was scientists moving data between machines — but it established the core concept.

FTP: The Protocol That Formalized File Transfer 🖥️

The first major formal standard for downloading files over a network was FTP (File Transfer Protocol). Developed by Abhay Bhushan, a researcher at MIT, FTP was first specified in 1971 as part of ARPANET's growing toolkit. Bhushan published the original specification — RFC 114 — which described how two computers could establish a connection and move files reliably between them.

FTP wasn't a single invention so much as a formal agreement: a set of rules that different computers and operating systems could follow to exchange files. Subsequent versions were refined throughout the 1970s and into the 1980s, with the version most people still reference — RFC 959 — published in 1985 by Jon Postel and Joyce K. Reynolds.

Key things FTP introduced to downloading:

• Authentication — users could log in with credentials to access files
• Directory navigation — you could browse a remote file system
• Transfer modes — support for both binary files and plain text
• Client-server model — the machine you're on requests files from a machine hosting them

This client-server model is still the conceptual backbone of nearly every download you perform today.

ARPANET, TCP/IP, and Making Downloads Reliable

FTP needed something to run on. That "something" became TCP/IP — the Transmission Control Protocol / Internet Protocol, developed primarily by Vint Cerf and Bob Kahn in the early 1970s, with their landmark paper published in 1974.

TCP/IP solved a fundamental problem for downloading: how do you send data reliably across an unreliable network? The answer was to break files into small packets, route them independently across the network, and reassemble them at the destination — retransmitting any that were lost or corrupted. Without TCP/IP, large file downloads would frequently fail or deliver corrupted data with no error handling.

Cerf and Kahn are often called the "fathers of the internet," and their protocol work is arguably the most important technical foundation for everything downloading depends on.

The World Wide Web Changed Who Could Download

Understanding that downloading existed long before most people used it matters, because the World Wide Web — invented by Tim Berners-Lee at CERN in 1989–1991 — is what made downloading accessible to ordinary users.

Berners-Lee created HTTP (HyperText Transfer Protocol), which is fundamentally a download protocol. When your browser loads a webpage, it's downloading HTML, images, CSS, and scripts from a server. When you click a download link, HTTP handles the transfer.

Before the Web, downloading required knowing FTP commands, having an account on a remote server, and understanding directory structures. The Web abstracted all of that behind clickable links and browsers — which is why most people think of downloading as a 1990s invention when it's actually much older.

Other Contributors to the Download Ecosystem 📡

The full picture includes several other technologies and their creators:

Bram Cohen's BitTorrent deserves specific mention because it fundamentally changed how large files are distributed. Instead of downloading from a single server, BitTorrent splits files across many peers simultaneously — reducing load on any one source and making large downloads dramatically faster and more resilient.

What "Downloading" Actually Means Technically

Every download today still follows the same conceptual steps Bhushan's FTP laid out:

1. Your device sends a request to a server
2. The server breaks the file into packets
3. Packets travel across the network via routers
4. Your device reassembles the packets into the complete file
5. Error-checking ensures the file arrived intact

The differences between downloading a file in 1973 versus 2024 are largely speed, scale, encryption, and user interface — not fundamental architecture.

The Variables That Affect Your Downloads Today

Knowing who invented downloading matters less day-to-day than understanding what affects download performance in your specific situation. The factors that determine real-world download experience include:

• Your internet connection type — fiber, cable, DSL, cellular, and satellite all have different bandwidth ceilings and latency profiles
• Server-side capacity — a slow or overloaded server limits speed regardless of your connection
• Protocol being used — HTTP/2 and HTTP/3 handle connections differently than older standards
• File size and type — compressed files, chunked transfers, and CDN delivery all affect speed
• Hardware — your router, network card, and storage write speeds all play a role
• Network congestion — both on your local network and across the wider internet path to the server

The same 100 Mbps internet plan can deliver very different real-world download speeds depending on which of these variables is the bottleneck in any given situation — and identifying which one applies to your setup is a different exercise for every user.