How to Use a Web Browser as an FTP Client

Not everyone has (or wants to install) a dedicated FTP client. Fortunately, web browsers have historically supported the FTP protocol natively, letting you browse and download files from an FTP server using nothing but a URL — no special software required. This article explains, from first principles, how browser-based FTP access works, how to use it, its current state across modern browsers (many of which have removed native support), and the best alternatives.

How FTP URLs Work

Just like http:// and https:// identify web protocols, ftp:// identifies the File Transfer Protocol in a URL. The general format is:

ftp://[username[:password]@]host[:port]/path

ftp://[username[:password]@]host[:port]/path

Examples:

ftp://ftp.example.com/
ftp://ftp.example.com/pub/documents/
ftp://anonymous@ftp.example.com/
ftp://myuser:mypassword@ftp.example.com/private/

ftp://ftp.example.com/
ftp://ftp.example.com/pub/documents/
ftp://anonymous@ftp.example.com/
ftp://myuser:mypassword@ftp.example.com/private/

sequenceDiagram
    participant Browser
    participant FTP Server
    Browser->>FTP Server: Connect using ftp:// URL
    FTP Server-->>Browser: Directory listing (HTML-rendered)
    Browser->>FTP Server: Click a file link
    FTP Server-->>Browser: File download begins

When you type an ftp:// URL into a browser’s address bar, the browser opens a control connection to the server on port 21, authenticates (anonymously by default if no credentials are given), and requests a directory listing, which it renders as a simple clickable HTML-style page.

Browsing an FTP Server

Simply type the address:

ftp://ftp.example.com/

ftp://ftp.example.com/

The browser will display the contents of the root FTP directory as a list of folders and files, similar to a basic file listing page. Clicking a folder navigates into it; clicking a file typically downloads it (browsers generally don’t “preview” FTP files the way they do for http:// content).

Providing Login Credentials

For a server requiring authentication (not anonymous), you can embed credentials directly in the URL:

ftp://username:password@ftp.example.com/

ftp://username:password@ftp.example.com/

Security warning: Including a password directly in a URL is insecure — it may be logged in browser history, autocomplete data, or even accidentally shared if you copy/paste the URL. Use this only for testing or low-security scenarios, and prefer a dedicated FTP client with encrypted credential storage for anything sensitive.

If you don’t include credentials, most browsers will prompt for a username and password via a login dialog when you visit an authenticated FTP URL (in browsers that still support FTP at all — see the next section).

Important: Native FTP Support Has Been Removed From Most Modern Browsers

This is a crucial, current fact for anyone reading this in 2026: Google Chrome removed native FTP support starting in Chrome 95 (around late 2021), and Mozilla Firefox removed it starting in Firefox 90 (2021). Microsoft Edge, being Chromium-based, followed Chrome’s lead as well.

This means that, on most modern, up-to-date browsers, typing an ftp:// URL will either:

• Fail to load at all, or
• Trigger a download prompt via an external handler, or
• Simply show an error page

This is why, in practice, “using a browser as an FTP client” today usually means one of two things: using a browser extension that re-adds FTP capability, or using a file manager that supports FTP as a “location” (like GNOME Files/Nautilus, or Windows File Explorer, which still support ftp:// addresses in the address bar even though the web browser itself does not).

Alternative 1: Using a File Manager (GNOME Files / Nautilus)

On Linux desktop environments like GNOME, you can connect to FTP servers directly from the file manager, which behaves much like a browser did in the FTP-support era:

1. Open Files (Nautilus)
2. Press Ctrl+L to open the location bar
3. Type: ftp://ftp.example.com/
4. Press Enter, and provide credentials if prompted

This gives you drag-and-drop file transfer, just like a native FTP client, integrated into your desktop.

Alternative 2: Using a Browser Extension

Some browser extensions restore basic FTP browsing capability inside Chrome or Firefox, essentially acting as a bridge that fetches FTP content and renders it as a web page. These vary in quality and trustworthiness — always check reviews and permissions carefully before installing any third-party extension that will handle your file transfer credentials.

Alternative 3: Command-Line or Dedicated GUI FTP Clients

For anything beyond casual browsing, a dedicated tool is more reliable:

sftp user@host          # secure alternative, built into OpenSSH<br>ftp ftp.example.com     # classic command-line FTP client (see our other article)

sftp user@host          # secure alternative, built into OpenSSH<br>ftp ftp.example.com     # classic command-line FTP client (see our other article)

Popular graphical alternatives include FileZilla, which supports FTP, FTPS, and SFTP in one unified interface, and works consistently across Windows, macOS, and Linux.

A Practical Example (For Legacy/Internal Browsers That Still Support FTP)

Suppose your organization still runs an older browser internally (e.g., in a locked-down kiosk environment) that retains FTP support:

Step 1: Type the URL:

ftp://reports.internal.example.com/daily/

ftp://reports.internal.example.com/daily/

Step 2: If prompted, log in with your credentials.

Step 3: Click a file (e.g., sales-2026-07-24.csv) to download it directly to your Downloads folder.

Step 4: Navigate into subfolders by clicking them, just like browsing a website.

Comparison: Browser FTP Access vs. Dedicated Clients

Real-World Use Case: Quick One-Off Download From a Public Mirror

If you just need to grab a single file from a public, anonymous FTP mirror and your browser still supports it (or you’re using a file manager instead):

ftp://ftp.gnu.org/gnu/

ftp://ftp.gnu.org/gnu/

Navigate to the desired package and click to download — no client installation needed. On a modern browser where this doesn’t work, the equivalent command-line approach is:

wget ftp://ftp.gnu.org/gnu/some-package.tar.gz

wget ftp://ftp.gnu.org/gnu/some-package.tar.gz

wget and curl both still support the ftp:// scheme directly and are excellent lightweight alternatives when a browser won’t cooperate:

curl -O ftp://ftp.example.com/pub/file.zip

curl -O ftp://ftp.example.com/pub/file.zip

Best Practices

• Don’t rely on browser-native FTP support for anything beyond legacy/internal use — it’s been removed from all major modern browsers.
• Never put real passwords directly in ftp:// URLs that might end up in browser history, bookmarks, or shared links.
• Use wget or curl as lightweight, scriptable alternatives when you just need to grab a file via FTP from the command line.
• Prefer SFTP/FTPS clients like FileZilla for anything involving uploads, credentials, or resumable transfers.
• Use your desktop file manager’s “Connect to Server” feature (GNOME Files, KDE Dolphin) as a convenient, GUI-based FTP browsing option on Linux even without a browser.

Troubleshooting

Problem: ftp:// URL does nothing or shows an error in Chrome/Firefox/Edge

This is expected — native FTP support has been removed. Use wget/curl, a file manager, or a dedicated FTP client instead.

Problem: Credentials in the URL don’t work

Special characters in the password (like @ or :) need to be URL-encoded, or better, avoid embedding credentials in the URL entirely and use a proper login prompt or dedicated client.

Problem: File manager can’t connect to the FTP server

Check that the server is reachable and the correct port is used:

telnet ftp.example.com 21

telnet ftp.example.com 21

Problem: Download starts but fails partway through

Browsers (even where FTP is supported) generally can’t resume interrupted FTP downloads. Use wget -c (continue) instead:

wget -c ftp://ftp.example.com/largefile.zip

wget -c ftp://ftp.example.com/largefile.zip

Conclusion

Using a web browser as an FTP client was once a simple, universal way to browse and download files without any special software — but as of 2026, native ftp:// support has been removed from all major modern browsers (Chrome, Firefox, Edge, Safari) for security and maintenance reasons. Today, the practical equivalents are desktop file managers with “Connect to Server” features, command-line tools like wget and curl, and dedicated GUI clients like FileZilla. Understanding this history helps explain why so many organizations are migrating away from FTP entirely, toward more modern, secure, and universally supported protocols like SFTP and HTTPS-based file sharing.

Further Reading

• Chrome Platform Status: FTP support removal
• Mozilla: FTP protocol removal
• wget manual
• curl manual
• FileZilla project
• RFC 959 — File Transfer Protocol