How to Access an FTP Server from the Browser

The short answer: in 2026, you don't. Every modern web browser has dropped native FTP support. Chrome removed it in version 88, Firefox in version 90, Edge inherited the Chromium removal, and Safari has been FTP-free for years. Typing ftp://server/ into the URL bar no longer connects to anything — the browser will either show a download dialog for a single file, prompt to open an external client, or refuse entirely.

That leaves three paths for accessing an FTP server today, all of which are faster, more secure, and better-behaved than the old browser shortcut ever was:

1. A dedicated FTP client — FileZilla, WinSCP, Cyberduck, or any of a dozen others. Free, runs on every OS, handles FTP, SFTP, and FTPS protocols natively.
2. Your operating system's file manager — Windows Explorer and macOS Finder both let you map an FTP server as a network location for drag-and-drop access.
3. A cloud-hosted file-transfer platform — services like Files.com expose FTP, SFTP, and FTPS endpoints in front of a web-based file manager, so the "browser FTP" experience comes back — just through a modern interface instead of a raw protocol handler.

Which one is right depends on whether the FTP server is a one-off you need to log into occasionally, or a piece of infrastructure your business depends on. The rest of this post walks through each path, the trade-offs, and the modern equivalents that make the "FTP in the browser" question feel obsolete.

Why browsers dropped FTP

For 20 years, every desktop browser supported the ftp:// URL scheme. You typed an address, the browser connected, you saw a directory listing, you clicked files to download. It worked, more or less.

The reasons it had to go:

• No encryption. Plain FTP sends usernames, passwords, and file contents over the network in cleartext. Modern browsers treat HTTPS as the floor for any transmitted credential; a protocol that defaults to plaintext auth doesn't meet that bar.
• Two ports, hostile firewalls. FTP's control connection runs on port 21 and the data connection opens a separate ephemeral port. Active-mode FTP needs the server to call back to the client — broken by every NAT router in the last 25 years. Passive mode helps but adds its own firewall complications.
• Usage cratered. Chrome's metrics put FTP traffic at under 0.1% of all browser requests before removal. Maintaining a niche protocol stack to serve a fraction of a percent of users wasn't defensible against the security maintenance cost.

None of which means FTP itself is dead. The protocol is still actively used for B2B file exchange, vendor data drops, regulated workflows, EDI feeds, and a long tail of legacy systems that won't be replaced soon. The browser stopped being a viable client; the protocol kept going.

The modern way: a dedicated FTP client

The default answer for one-off access is a desktop FTP client. Three that cover ~95% of the market:

• FileZilla — free, open source, Mac / Windows / Linux. Speaks FTP, SFTP, and FTPS. The most widely installed FTP client in IT shops.
• WinSCP — Windows-only, free, focused on SFTP and FTP. Scripting and command-line support is strong; the GUI is functional rather than polished.
• Cyberduck — Mac and Windows, free with a donation prompt. Cleanest UI of the three, supports a wide range of cloud-storage backends alongside FTP/SFTP.

All three follow the same connection pattern: enter a hostname, choose a protocol (FTP, SFTP, or FTPS), enter a port (21 for FTP, 22 for SFTP, 990 for implicit FTPS), enter username and password, and connect. The server side responds with a directory listing, and the client handles the upload, download, and rename UI from there.

What you need before connecting

Whichever client you pick, the server admin needs to give you:

• Hostname — either a domain (ftp.example.com) or an IP address.
• Protocol — plain FTP, SFTP (FTP over SSH), or FTPS (FTP over TLS). If the admin says "FTP" with no qualifier, ask: assuming plain FTP in 2026 is rarely the right call.
• Port — 21 for FTP, 22 for SFTP, 990 for implicit FTPS, 21 with TLS upgrade for explicit FTPS. If the server uses a non-standard port, the admin should specify.
• Username and password — or, for SFTP, an SSH key. Anonymous FTP still exists for public download mirrors but is uncommon for business use.

The other modern way: mount FTP as a network drive

For frequent access — vendors who drop files daily, EDI feeds, regular partner exchanges — mapping the FTP server as a network drive in Windows Explorer or macOS Finder removes the "open the client, enter credentials, navigate" ceremony. The server shows up alongside your local drives, and files copy with the same drag-and-drop UI you use for everything else.

On Windows: right-click This PC, choose Add a network location, paste the FTP URL, and follow the wizard. Windows supports plain FTP natively but not SFTP. For SFTP on Windows, third-party tools like ExpanDrive mount SFTP as a real drive letter.

On macOS: Finder > Go > Connect to Server, paste the ftp:// or ftps:// URL. macOS's native support is read-only for FTP but works for browsing and downloads. SFTP again needs a third-party tool for full read/write drive-letter access.

The cloud-hosted way: get the browser experience back

The reason "how to access an FTP server from a browser" is still a frequent search isn't nostalgia for an old protocol; it's that browser access was convenient. No client to install. No credentials buried in a settings dialog. Open a URL, see your files, click to upload or download. That convenience didn't go away — it moved to cloud-hosted file-transfer platforms that put a modern web UI in front of FTP, SFTP, and FTPS endpoints.

The modern cloud answer is Files.com — the File Orchestration Platform from the company that now owns ExaVault. It runs SFTP, FTP, and FTPS endpoints against your own subdomain, lets your trading partners connect with any FTP client they already use, and exposes the same files through a web-based file manager that anyone with a browser can hit.

That gets you:

• FTP / SFTP / FTPS support on a hostname you configure, with per-user credentials, SSH key auth, and per-folder permissions.
• Web-based file manager in a modern browser — the closest thing today to the old "FTP in the URL bar" experience, but with HTTPS, sessions, MFA, and proper access logs.
• Share links — send a partner a single URL to upload or download a specific folder, no account needed on their side.
• Automations — rules that fire when a file lands (forward to S3, send a notification, kick off a webhook), so the FTP endpoint becomes a pipeline trigger instead of an inbox someone has to babysit.
• SOC 2 Type II, HIPAA, GDPR on the underlying platform — compliance posture that you'd otherwise spend a year building in-house.

You can read the full FTP/SFTP feature breakdown on Files.com, or start with the homepage at files.com. The free trial runs without a credit card.

If you specifically need an on-prem FTP appliance

For organizations that can't put file-transfer infrastructure in a multi-tenant cloud — air-gapped environments, strict data-residency mandates, regulated industries with on-prem-only policies — ExaVault ships an on-prem managed-file-transfer appliance as a VMware OVA, an AWS Marketplace image, and a Google Cloud Marketplace image, with the same FTP / SFTP / FTPS / WebDAV protocol surface that ExaVault customers have been running since 2008. That's a real but narrow buyer profile; most teams asking "how do I access FTP from a browser" are better served by the cloud platform.

FAQ

Does FTP still work in Chrome or Firefox?

No. Chrome removed FTP support in version 88 (early 2021). Firefox followed in version 90. Microsoft Edge inherited the Chromium removal. Safari had been FTP-free for years before any of those. Pasting an ftp:// URL into a modern browser's address bar will not open an FTP session.

How do I access an FTP server with just a username and password?

Install an FTP client (FileZilla, WinSCP, or Cyberduck), open it, enter the server's hostname and port, type your username and password, and connect. The server presents a directory listing; uploads and downloads happen via drag-and-drop in the client's file panes. Alternatively, host the server on a cloud platform like Files.com, which gives you a web file manager alongside the FTP endpoint.

Can I connect to an FTP server with just an IP address?

Yes. FTP clients accept either a hostname or a raw IP. Enter the IP address in the host field (e.g., 192.168.1.100), set the port (21 for FTP, 22 for SFTP), and authenticate. If the server is behind NAT, you may need passive mode — most clients enable this by default, but check the connection settings if the directory listing hangs.

Why can't I access an FTP site?

Three usual causes: (1) the client is set to active mode and your firewall is blocking the inbound data connection — switch to passive mode; (2) the server requires SFTP or FTPS and you're trying plain FTP; (3) the server has IP-allowlist restrictions and your network isn't on the list. If you control both ends, run an FTP client with verbose logging enabled and read the protocol exchange — the actual error usually shows up in the first 10 lines.

Is FTP secure?

Plain FTP is not. Credentials and file contents transmit in cleartext. SFTP (FTP over SSH, port 22) and FTPS (FTP over TLS, port 990 implicit or 21+upgrade explicit) are the secure alternatives. In 2026, any new FTP deployment should default to SFTP — broad client support, single port, real encryption, key-based auth. The phrase "FTP" in business contexts usually means SFTP unless someone explicitly says otherwise.

What's the difference between FTP, SFTP, and FTPS?

FTP is the original protocol from 1985: two connections (control + data), no encryption, ports 21 + ephemeral. FTPS wraps the same protocol in TLS (port 990 implicit, or port 21 with a STARTTLS-style upgrade for explicit FTPS). SFTP is a completely different protocol that runs inside an SSH session over port 22 — same shape as ssh and scp. SFTP is simpler to firewall (one port), more secure by default (cert-based auth available), and the de-facto default for any modern FTP-style deployment.