FileZilla in practice: the three things people keep mentioning

FileZilla is old enough that most reviews of it are really reviews of a memory. Someone used it in 2014, formed an opinion, and the opinion outlived several rewrites of the underlying transfer engine. Meanwhile the application changed licence, changed its SSH implementation, gained a paid sibling and a subscription product, and quietly kept shipping releases every few weeks.

What follows is grounded in the published record: the feature list, the version history, the download page and the vendor's own pricing and support pages, all as they stand today. Three themes come up over and over in that record, and they are the three things worth knowing before installing it or before replacing it.

First, what it actually is

Precision here prevents most disappointment. FileZilla is a transfer client. It shows a remote filesystem on one side and a local filesystem on the other, and it moves files between them. It is not a local file manager, and the local pane exists to give the transfer somewhere to come from.

Its protocols are FTP, FTP over SSL/TLS, and SSH File Transfer Protocol. The published feature list beyond that is longer than most people expect:

Supports resume and transfer of large files >4GB Source: filezilla-project.org

The same list carries a tabbed interface, a site manager with bookmarks, a persistent transfer queue, directory comparison, synchronised directory browsing, remote file search, remote file editing, filename filters, configurable transfer speed limits, IPv6, proxy support for HTTP/1.1, SOCKS5 and FTP proxies, and logging to file. Builds exist for Windows in two architectures, Linux in two, macOS on Intel, macOS on Apple Silicon, and source.

Two items on that list carry more weight than their position suggests. Synchronised directory browsing keeps both panes walking the same tree, so descending into a folder on one side descends into the matching folder on the other. Directory comparison marks the differences between the two sides before anything moves. On a site with a deep structure those two together account for most of the speed people describe, and plenty of more attractive clients have neither.

Second, the maintenance record

Reviews frequently describe FileZilla as neglected. The version history says otherwise, and this is checkable in a minute.

Eleven releases went out in the six months to the end of August 2026. The current stable version is 3.71.1, published on 26 August 2026. Three of the releases since April 2025 are listed under fixed vulnerabilities, each relinking the official binaries against a newer GnuTLS, which is the library behind FTPS encryption and certificate validation. Release 3.70.0 in April 2026 moved the project to the GNU General Public License version 3 or later.

The more telling signal is the content of those releases. The 3.70 series rebuilt the SSH File Transfer Protocol layer on a new library, and every release since has carried compatibility work against servers that break the specification: servers sending malformed authentication packets, servers reporting invalid bits in file attribute flags, servers with invalid names in directory listings. One of those shipped as a facility rather than a patch, adding a compatibility flags page to the site manager so an awkward host can be accommodated per site.

Mac specific work appears too. The most recent release addresses something only some Mac users would ever hit:

macOS: Work around a bug in macOS 27 where setting the locale to non-English triggers crashes in AppKit Source: filezilla-project.org

That is a crash inside an Apple framework, triggered by running the interface in a language other than English, worked around in the client. Whatever else is true of this application, an abandoned project does not ship that fix.

Third, what people rate it on

The vendor publishes App Store reviews for the paid client on its own product page and states an average of 4.5 out of 5. Published quotes are short and land on the same point repeatedly. One reads "The only FTP client that works out of the box!" and another "Fast, Reliable, Simple". The vendor describes the whole thing as a 22 year journey.

Treat a vendor's own selection of reviews as what it is. Still, the consistency of the theme is informative. Nobody in that selection praises the appearance. The praise is for connecting and finishing, which matches what the release notes spend their effort on. An application that spends four consecutive releases on servers that violate the SSH specification is optimising for exactly that.

The other side of the same coin is that the interface is functional rather than pleasant. Four panes of information, dense toolbars, a message log at the top and a queue at the bottom. Everything is visible, nothing is graceful. For anyone connecting to a server a few times a week to push a site, that trade favours the user. For anyone whose day is mostly local work, it does not, because the application was never built for that side.

Where it stops, and what the paid tier adds

The boundary is a protocol boundary, not a feature ladder. The free client does not speak object storage or consumer cloud drives. The vendor is direct about it.

If your transfers are FTP/SFTP only, the free client is sufficient. Source: filezillapro.com

The paid client adds Amazon S3, Backblaze B2, Box, Dropbox, Google Cloud, Google Drive, Microsoft Azure, OneDrive, OneDrive for Business, SharePoint, OpenStack Swift and WebDAV. Pricing on the macOS tab lists a single device licence starting at 12,99 € and a three device licence starting at 29,99 €. A separate subscription product, RemoteDrive, mounts remote storage into the Finder for 12,99 € a year through the App Store, and a separate command line product handles scheduled or scripted transfers, because the graphical application expects a person at the keyboard.

One licensing note belongs in any honest assessment. The licence is described as perpetual, while activation governs access to online services including new versions, and the vendor advises against running an expired build because cloud provider API changes will eventually break it. That is a subscription in effect for anyone relying on cloud connections, whatever the licence is called.

The Mac specific rough edges

Three of these, all verifiable, and none of them appear in the application itself.

The download page defaults to the Intel build. Its heading says so, and the file offered is the x86 archive requiring macOS 10.13.2 or newer. A native build is published in the same release but appears only after following the link to additional download options:

FileZilla_3.71.1_macos-arm64.app.tar.bz2 Source: filezilla-project.org

Nothing announces this, and nothing in the update path switches architecture, so an installation carried forward from an Intel Mac runs translated indefinitely. A fair share of complaints about the application becoming slow resolve at this one step.

The second is the distribution format. On macOS the download is a compressed application bundle, a .app.tar.bz2 archive dragged into place, rather than an installer package. That has one pleasant consequence and one unpleasant one. Nothing runs during installation and nothing is bundled alongside it, which is why the antivirus warnings associated with the Windows installer do not apply here. But nothing replaces the previous version either, so two copies accumulate easily, and the official troubleshooting guidance names that as the cause of an application that asks to update immediately after updating.

The third is the website rather than the software. Pages on the project site carry sponsor and advertisement blocks, which is how the free client is funded. Worth knowing so that a download is taken from the correct button.

Two settings that decide whether it feels fast

Speed complaints about this application cluster around two settings and one binary, and none of the three are obvious from the interface.

Speed limits come first, because they are a documented feature rather than a bug and they persist. The configuration lives under Edit, then Settings, then Transfers, where a checkbox enables them and separate download and upload figures apply, with a toggle in the status bar. A limit set once on a constrained connection stays set on every connection afterwards, and the status bar toggle is easy to leave in the wrong position for months.

The second is a setting that no longer exists, which matters because older advice still points at it:

*nix, macOS: Remove custom send buffer option, rely on operating system auto-tuning Source: filezilla-project.org

For years the standard answer to slow uploads on a Mac was to adjust that buffer by hand. It was removed in the 3.70 series and the tuning now belongs to the operating system. Any forum thread recommending it predates the current builds, and searching the settings for something that was deliberately deleted wastes an evening.

What the feature list does not mention

One absence shapes the whole experience and appears nowhere in the published list, because a feature list only says what is present.

There is no shell. Remote file editing exists, and it works by handing the file to an external editor and writing it back, which is genuinely useful. But anything requiring a command, whether that is unpacking an archive on the server, fixing permissions recursively, or checking a checksum, happens somewhere else. So does most local work, because the local pane is a transfer source rather than a file manager: no batch rename, no tagging, no preview beyond what the operating system provides in the Finder.

The practical result is a three window day. The Finder for local browsing and renaming, this application for the remote side, a terminal for everything neither can do. Nothing about that is a defect. It is the consequence of the application being precisely what it claims to be, and it is the single largest hidden cost of using it, because it is paid in small amounts continuously rather than once.

Who it fits

It fits anyone whose remote work is FTP or SFTP and whose local work happens somewhere else. For pushing a site to a shared host, moving a database dump off a server, or maintaining a few dozen client sites from one site manager, it is difficult to justify paying for an alternative. The features that save real time are in the free version, the maintenance is active, and the licence is GPL.

It fits less well in two situations. If the work involves a storage bucket or a cloud drive, the free client cannot reach it, and the paid path costs money with a renewal footnote attached. And if the actual friction is the shuffle between a Finder window, a transfer client and a terminal all day, a better transfer client does not touch it, because the local half of the job was never what this application was for. That is a different category of tool, which the comparison page sets against the transfer clients rather than against each other.

What to do next

Install the free client and check the architecture in the Activity Monitor Kind column before forming any opinion about speed. Turn on synchronised directory browsing and set up filename filters on the first day, because those two account for most of what people mean when they call it fast. If the remaining friction turns out to be the local side rather than the remote side, the features page for Atriens covers what folding the shell into the same window removes from the day.