Open Firefox today and type ftp:// into the address bar. You’ll get nothing. Chrome? Same result. Safari? Error page. This wasn’t always the case.

For most of the web’s history, every browser included native FTP (File Transfer Protocol) support. You could navigate FTP directories just like web pages, clicking folders and downloading files directly from the address bar. Between 2020 and 2021, all major browsers quietly removed this functionality.

FTP Before the Web

FTP predates the World Wide Web by over two decades. Created in 1971, it was one of the earliest file transfer methods on ARPANET. While HTTP was designed for hypertext documents, FTP was built specifically for moving files between computers.

Throughout the 1980s and early 1990s, FTP was how software got distributed. Universities, government agencies, and tech companies maintained public FTP servers where users could download files. Sites like ftp.cdrom.com and ftp.sunet.se were legendary repositories of shareware, freeware, and open source software.

When Mosaic and later Netscape Navigator appeared in the mid-1990s, their developers made a practical decision: build FTP support directly into the browser. Users shouldn’t need separate FTP client software when browsing for files.

How Browser FTP Worked

Browser-based FTP was surprisingly functional. Type ftp://ftp.example.com and you’d see a directory listing rendered as a simple web page. Click a folder to navigate deeper. Click a file to download it. Some servers supported anonymous access; others required authentication, which browsers would prompt for.

The interface wasn’t sophisticated. There was no upload capability in most browsers, no resume support for interrupted transfers, no queuing. But for downloading files, it worked perfectly well. And because every browser supported it, FTP links in web pages would simply work.

This integration had interesting consequences. Many university computer science departments maintained FTP servers with course materials. Linux distributions used FTP mirrors for ISO downloads. Open source projects hosted releases on FTP. The protocol was boring, reliable infrastructure that everyone took for granted.

The Security Problem

FTP’s fundamental design problem is that it sends credentials in plaintext. When you authenticate to an FTP server, your username and password travel across the network unencrypted. On a local network in 1971, this wasn’t concerning. On the modern internet, it’s inexcusable.

FTPS (FTP Secure) and SFTP (SSH File Transfer Protocol) addressed this by adding encryption, but browser support for these variants was inconsistent at best. Most browser FTP implementations only supported the original, insecure protocol.

By the late 2010s, browser vendors were pushing hard to eliminate insecure protocols. HTTP was being replaced by HTTPS across the web. Mixed content warnings became standard. In this context, maintaining support for an ancient protocol that transmitted passwords in cleartext became increasingly difficult to justify.

The Removal

Google announced in October 2020 that Chrome 88 would remove FTP support. Their rationale: less than 0.1% of users accessed FTP through the browser, the code was a maintenance burden, and the security implications were problematic.

Firefox followed in version 88, released April 2021. Mozilla’s telemetry showed similar usage numbers. Only a tiny fraction of users were accessing FTP through the browser, and those users could easily switch to dedicated FTP clients.

Apple’s Safari had already deprecated FTP support years earlier, making removal in recent versions almost unnoticed.

Microsoft Edge, being Chromium-based, inherited Chrome’s removal automatically.

What Was Lost

The practical impact of removing browser FTP was minimal. Anyone who regularly used FTP already had FileZilla or WinSCP installed. The protocol itself didn’t disappear — servers kept running, dedicated clients kept working.

What vanished was the simplicity of clicking an FTP link and having it just work. No software to install, no configuration needed. The browser handled it. This was particularly useful for universities and research institutions that had decades-old FTP infrastructure and didn’t want to force students to install FTP clients.

Some organizations struggled with the change. Team400, a consultancy that helps businesses modernize legacy systems, noted an uptick in requests from academic institutions trying to migrate away from FTP-based file distribution systems. The browser deprecations served as the forcing function that finally pushed these organizations to migrate to more modern alternatives like cloud storage or HTTPS-based file repositories.

Modern Alternatives

If you need to access an FTP server today, you have options:

Dedicated FTP clients like FileZilla remain actively maintained. They offer features browsers never had: uploads, queuing, resume support, directory synchronization.

Command-line tools like curl and wget both support FTP and can be scripted easily.

Web-based file managers allow accessing FTP servers through a web interface, often with better functionality than browsers provided.

For server administrators, the message was clear: if you’re still running FTP, it’s time to migrate. SFTP or HTTPS-based solutions provide the same functionality with modern security.

The Pattern

The removal of browser FTP follows a familiar pattern in web technology. A legacy feature that was once essential becomes marginal through years of declining use. Usage drops below a threshold where maintenance cost exceeds utility. Vendors coordinate removal, knowing that the small number of affected users have alternatives.

We’ve seen this with Flash, Java applets, FTP, and other technologies. Each removal provokes brief controversy among users who relied on the feature, then fades from memory as the ecosystem adjusts.

In twenty years, will anyone remember that browsers used to do FTP? Probably not. It will be one more historical footnote, like Gopher integration or RSS readers or the dozens of other features that browsers tried and eventually discarded.

FTP still works. You just can’t access it from your address bar anymore.