What FileZilla locks behind its paid tier

FileZilla has been free for over twenty years, and that has produced a fair amount of confusion about what free means now. There is a free client, a paid client with a similar name, a subscription product that mounts servers into the Finder, a separate command line tool, and a server product on top of that. Searching for the free one returns all five.

The line between them is clean once seen, and it is not the line most people assume. It is not a feature ladder where the free tier is crippled. It is a protocol boundary, and everything else follows from it.

What free covers in the client itself

The free FileZilla client is open source. As of release 3.70.0 in April 2026 it is distributed under the GNU General Public License version 3 or later, having moved up from version 2 or later. The current stable release is 3.71.1, published on 26 August 2026. There is no trial period, no account, no device limit and no nag screen inside the application.

The published feature list is what surprises people who assume free means basic. It includes a tabbed interface, a site manager with bookmarks, a transfer queue, resume and transfer of files larger than 4GB, directory comparison, synchronised directory browsing, remote file search, remote file editing, filename filters, IPv6, proxy support and logging to file. It also includes the feature most often assumed to be paid:

Configurable transfer speed limits Source: filezilla-project.org

Speed limits are set under Edit, then Settings, then Transfers, where a checkbox enables them and separate download and upload figures apply. A button in the status bar toggles the whole thing on and off. That is the free client, not an upgrade.

Builds are published for Windows in 32 and 64 bit, Linux in 32 and 64 bit, macOS on Intel, macOS on Apple Silicon, and source. Localisation is broad, with the vendor describing the interface as available in over 50 languages. None of that is gated.

The protocol boundary is the whole paid line

What the free client does not do is speak to object storage or consumer cloud drives. Its protocol list is FTP, FTP over SSL/TLS, and SSH File Transfer Protocol. That covers web hosts, NAS boxes and anything with a traditional server behind it. It does not cover a storage bucket.

The vendor states the boundary in plain terms.

FileZilla Pro adds cloud storage: Amazon S3, Google Drive, Microsoft OneDrive, Dropbox, Box, Backblaze B2, Azure, and more, all from the same interface you already know. If your transfers are FTP/SFTP only, the free client is sufficient. Source: filezillapro.com

The full paid protocol list runs to Amazon S3, Backblaze B2, Box, Dropbox, Google Cloud, Google Drive, Microsoft Azure, OneDrive, OneDrive for Business, SharePoint, OpenStack Swift and WebDAV. WebDAV is the one worth flagging, because it is an old and widely deployed protocol that many people assume every client speaks. In this family it is on the paid side.

Notice what is not on the paid side. No speed unlock. No connection count unlock. No removal of a watermark. Someone whose work is entirely FTP and SFTP gains nothing from paying, and the vendor says so directly rather than implying otherwise.

What the paid tier costs

Pricing on the macOS tab of the purchase page lists two client licences and one subscription product.

Product	Price as listed	Scope
FileZilla Pro, single device	Starting at 12,99 €	macOS only, one device
FileZilla Pro, multiple devices	Starting at 29,99 €	macOS, Windows, Linux, up to 3 devices
FileZilla Pro RemoteDrive	Yearly subscription, 12,99 €	macOS only, mounts storage into the Finder
FileZilla Pro CLI	Sold separately	Command line, scripted and scheduled transfers

Two of those rows need reading carefully. RemoteDrive is a different product from the client, sold through the App Store, and it is what mounts remote servers and cloud storage as volumes rather than showing them in a two pane window. And the CLI is not included with the desktop licence. The desktop application expects a person at the keyboard, and unattended transfers are a separate purchase.

Trials are narrower than the pricing page suggests at a glance. A seven day run is available if the purchase is made through the App Store or the Microsoft Store. Direct purchases are covered by a 30 day money back guarantee instead. There is no downloadable time limited build outside those two stores.

Perpetual, with a footnote on updates

The most consequential detail is not on the pricing table. It is in the licensing notes, and anyone budgeting a paid licence as a single line item should read it before deciding.

Your license is perpetual, but activation now governs access to FileZilla Pro's online services, including new versions of the app. Source: filezillapro.com

The practical reading: the copy on the disk keeps working after the subscription lapses, and new versions do not arrive. The vendor advises against staying on the expired build, on the grounds that it stops receiving security updates and that cloud provider API or authentication changes will eventually break functionality. That last point is specific to this product category. An S3 or OneDrive integration is only correct until the provider changes something, so a frozen cloud client has a shorter useful life than a frozen FTP client.

For the free client, none of this applies. Updates keep arriving and there is nothing to activate.

How the free side is funded

Free software still has costs, and it is reasonable to ask where they land. Three places, all visible.

The project website carries advertising. Loading any page on the download or features side of the site renders a sponsor block and an advertisement block alongside the content, served from the project's own ad host. That is the funding model for the free client, and it is on the website rather than inside the application.

Second, the Windows installer. The vendor addresses the antivirus warnings it triggers directly, describing them as follows:

a false positive caused by the bundled installer format, not malware Source: filezillapro.com

That matters less on a Mac, because the macOS distribution is not an installer at all. It is a compressed archive of an application bundle, downloaded as a .app.tar.bz2 file and dragged into place. Nothing is bundled with it and nothing runs during installation. Mac users reading Windows era warnings about the installer are reading about a different package.

Third, the paid products themselves subsidise the free one. That is the ordinary open core arrangement, and it is the reason the free client keeps getting releases rather than quietly stopping.

Security work lands on the free side too

A reasonable worry about free software is that the security fixes go to the paying customers first. The published version history is the place to test that, and it does not support the worry.

Release 3.70.5 in May 2026 is listed under fixed vulnerabilities, with the official binaries relinked against GnuTLS 3.8.13. Release 3.69.6 in February 2026 did the same with GnuTLS 3.8.12, and release 3.69.2 in July 2025 with GnuTLS 3.8.10. These are the free client's own release notes. The transport library that protects FTPS and certificate validation is kept current there, not only downstream.

Platform specific fixes arrive the same way. The most recent release addresses a crash that only some Mac users would ever see:

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 free client fix for a problem affecting anyone running the interface in a language other than English on a current version of macOS. Eleven releases went out in the six months to the end of August 2026. Whatever the reasons for looking at the paid tier, an under maintained free client is not among them.

Documentation follows a similar pattern. The knowledge base covering both editions is public and readable without a licence, while the vendor also sells collected manuals for anyone who prefers them. Nothing needed to configure the free client sits behind that.

Three settings worth changing in the free client

Most of what people go looking for in a paid client is already present and switched off by default. Three items are worth ten minutes.

Speed limits are the first, and not only for slowing things down. A limit set once on a hotel connection stays set, silently capping every transfer afterwards, and the toggle in the status bar is easy to leave in the wrong position. Checking Edit, then Settings, then Transfers, is the first move whenever throughput looks wrong.

Synchronised directory browsing is the second. It keeps the local and remote panes walking the same tree, so moving into a subfolder on one side moves into the matching subfolder on the other. On a site with a deep structure it removes most of the clicking, and it is in the free client rather than the paid one. Directory comparison sits next to it and marks what differs between the two sides before anything transfers.

Filename filters are the third. Without them, every listing carries .DS_Store, .git and node_modules, and an accidental recursive upload carries them to the server. A filter set written once applies to every site in the site manager.

Where the free client still costs time

Zero purchase price is not zero cost, and the honest accounting looks at where the hours go.

One item is fixable in a minute. The macOS download page defaults to the Intel build, labelled as such, requiring macOS 10.13.2 or newer. The Apple Silicon archive exists in the same release but appears only under the additional download options link. Anyone who has been updating in place since an Intel machine is running the translated binary and paying for it in throughput. Checking the Kind column in the Activity Monitor settles it.

The larger item is not fixable by any transfer client. A transfer client shows a remote tree and a local tree, and local work still happens somewhere else. The Finder handles browsing and renaming, a terminal handles everything neither window can do, and the day is spent moving between three places. Multiplied across a year, that round trip costs more than any of the licences on the table above. Where that is the real complaint, the answer is a different category of tool, and the comparison page sets those against the transfer clients rather than against each other. Interface language is a related consideration for anyone not working in English, which the languages page covers.

What to check first

Confirm which architecture the current build is, because that costs nothing and explains a surprising share of complaints. Then answer one question: does the work involve a storage bucket or a cloud drive. If it does not, the free client is the complete product and the paid tier adds nothing. If the friction turns out to be the three window shuffle rather than a missing protocol, the pricing page for Atriens is the comparison to make instead.