FileZilla in practice: the three things people keep mentioning
The short verdict: FileZilla is a capable, actively maintained FTP and SFTP client that costs nothing, and on a Mac most of the worries attached to it either do not apply or can be checked in two minutes. Read across the pages that rank for this search and three themes keep returning. Is the download safe? Is the project still alive? And is the free version enough, or does the real work need the paid FileZilla Pro? This review answers each one from the vendor's own pages as they stood on 9 October 2026, then adds the Mac specific checks that the rankings mostly skip.
The safety question, answered for Mac
Most of what turns up under "is FileZilla safe" is about the Windows setup program. Forum threads, a university security notice and a long privacy community discussion all circle the same worry: people download an installer from the wrong place, or click through an offer screen without reading it. That history explains why the question exists. It does not describe what a Mac user receives today.
On macOS there is no setup program at all. The official download list offers two Mac files for version 3.71.1, one per processor type, and both are compressed application bundles ending in .app.tar.bz2. Double clicking the archive unpacks the application; dragging it to Applications is the whole installation. No step runs code before the application itself opens, so there is nothing to click through.
The same page also publishes a checksum file for the release, FileZilla_3.71.1.sha512. That turns the safety question from a matter of trust into something measurable. The check takes four steps.
- Download the Mac archive and the
.sha512file from the same page. - Open Terminal and run
shasum -a 512followed by the path to the archive. - Open the checksum file in a text editor and find the line naming the same archive.
- Compare the two long strings. If they match, the file is byte for byte what the project published.
A mismatch means the download came from somewhere else or was damaged on the way, and the archive should be deleted rather than opened. Very few reviews mention this file, which is odd, because it settles the question more firmly than any reputation score.
The practical rule is simple: download only from filezilla-project.org, and verify the checksum once. After that, the remaining security question is about the protocol, not the program. Plain FTP sends the password unencrypted. FTPS and SFTP do not. If a hosting provider offers SFTP, use it, and the client's own security record becomes a much smaller part of the risk.
Is it still maintained? The release record says yes
Several of the pages ranking for this search describe FileZilla as old, and some imply it is drifting. The version history answers that directly. Checked on 9 October 2026, it lists eight releases between 13 April and 26 August 2026, from 3.70.1 through the current 3.71.1.
The content of those releases matters more than the count.
| Release | Date | What changed |
|---|---|---|
| 3.70.0 | 9 April 2026 | Licence moved to GPL version 3 or later |
| 3.70.5 | 7 May 2026 | Linked against GnuTLS 3.8.13, listed under fixed vulnerabilities |
| 3.70.6 | 4 June 2026 | Site Manager flag for servers that send invalid attribute bits |
| 3.71.0 | 19 August 2026 | Empty remote path returns to the home folder; SSH library update |
| 3.71.1 | 26 August 2026 | Workaround for a macOS 27 crash with non-English system language |
Two patterns stand out. First, security fixes arrive as relinks against newer versions of GnuTLS, the library that handles FTPS encryption and certificate checks. That is how a maintained project behaves. Second, the 3.70 series replaced the SFTP layer with a new library, and almost every release since then has added compatibility work for servers that break the SSH specification. One of those changes became a whole compatibility page inside the Site Manager, so an awkward host can be handled per site instead of globally.
The macOS 27 entry is the clearest signal for Mac users. A crash inside Apple's own AppKit framework, triggered when the system language is not English, was worked around in the client within weeks. Whatever one thinks of the interface, an abandoned application does not ship fixes like that.
Theme two: the interface people forgive
The vendor's FileZilla Pro page quotes App Store reviews and states an average rating of 4.5 out of 5. The quotes are a curated selection, so they say little about the average experience. What they do show is which praise the vendor chose to repeat. One calls it "the only FTP client that works out of the box". Another says plainly that the interface is not as pretty as Cyberduck or Transmit, and recommends it anyway.
That pairing matches what independent reviews say. The window is dense: a message log across the top, local and remote trees side by side, file lists under them, a transfer queue along the bottom. Everything is visible at once. New users find it busy. People who connect to servers several times a week tend to like it for the same reason, because nothing needed for a transfer is hidden behind a menu.
The features that earn that loyalty are on the official feature list, and two of them do most of the work.
- Synchronized directory browsing keeps both sides walking the same folder tree. Open a folder on the local side and the matching folder opens on the remote side.
- Directory comparison highlights files that differ between the two sides before anything moves.
Together they make the routine job of pushing changed files to a web host fast and hard to get wrong. The list also includes a Site Manager with bookmarks, a transfer queue that survives restarts, filename filters, remote file search, remote file editing through an external editor, resume for files over 4 GB, configurable speed limits, and proxy support.
Reviews that call the client slow usually trace back to one of two causes. A speed limit was switched on once and forgotten, since limits persist across sessions. Or an older Intel build is still running on an Apple silicon Mac, which the next section covers.
Theme three: free or Pro?
This is the decision most readers are actually making, and the vendor's own pages draw the line clearly. The free client speaks FTP, FTPS and SFTP. That is the full list. Anything else needs FileZilla Pro.
Prices on the macOS tab of the Pro page, checked on 9 October 2026:
| Option | Price shown | What it covers |
|---|---|---|
| FileZilla (free) | Free | FTP, FTPS, SFTP on macOS, Windows, Linux |
| FileZilla Pro, single device | From 12,99 € | Adds major cloud storage, macOS only, one device |
| FileZilla Pro, multiple devices | From 29,99 € | Up to 3 devices across macOS, Windows, Linux |
| FileZilla Pro RemoteDrive | 12,99 € per year | Mounts remote storage in the Finder, macOS only |
The cloud services listed for Pro are Amazon S3, Backblaze B2, Box, Dropbox, Google Cloud, Google Drive, Microsoft Azure, OneDrive, OneDrive for Business, SharePoint, OpenStack Swift and WebDAV. Pro also lists Site Manager synchronisation between machines and a master password that stores saved passwords encrypted.
So the decision rule is short. If every server in the Site Manager is FTP, FTPS or SFTP, the free client covers the job, and paying buys convenience rather than capability. If even one destination is a bucket or a cloud drive, the free client cannot reach it, and Pro or a different tool is required. The Pro page's FAQ also covers what happens when a subscription is not renewed. Read that answer before buying if cloud access is the reason, because cloud APIs change and older builds can stop connecting.
Mac details that most reviews skip
Three practical points apply only to Macs, and each one explains a common complaint.
The default download is the Intel build. Visiting the download page from a Mac shows a heading for macOS (Intel), and the button offers the x86 archive. The native Apple silicon archive, FileZilla_3.71.1_macos-arm64.app.tar.bz2, sits on the same release but only appears after following "Show additional download options". Both require macOS 10.13.2 or newer. An Intel build runs through Rosetta translation and works, but it is the wrong default for any M series Mac. To check which one is installed, open Activity Monitor while FileZilla is running and look at the Kind column: Apple means native, Intel means translated.
Updates do not replace the old copy. Because the Mac version is an archive rather than an installer, each new download unpacks a fresh application next to the old one unless it is dragged over it. Two copies in Applications, or one in Downloads, lead to the familiar loop where the client asks to update immediately after updating. Delete the older copy and keep one.
An old tuning tip no longer applies. For years, forum answers to slow Mac uploads recommended changing a custom send buffer setting. The version history shows that option was removed in 3.70.0-rc1 for macOS and Unix systems, which now rely on the operating system's own tuning. Advice pointing at that setting predates current builds.
What FileZilla does not try to do
A transfer client has edges, and FileZilla is honest about where its edges are. The local pane exists to give transfers a source. It is not a full file manager. There is no batch rename, no tagging, no rendered preview of Markdown or images, and no terminal. Remote editing works by handing a file to an external editor and uploading it again, which covers small fixes but not commands such as unpacking an archive on the server or changing permissions across a folder tree.
None of this is a defect. It is the scope of the product. The cost shows up in how the working day is arranged. A typical Mac setup ends up with the Finder for local browsing and renaming, FileZilla for the remote side, and a separate Terminal window for anything requiring a command. If transfers are occasional, that is fine. If most of the day is local work on project folders with a shell open beside them, a better transfer client does not reduce the window juggling, because the friction is on the local side. That is a different category of tool, and the comparison page sets those tools side by side.
Who should install it today
FileZilla fits anyone whose remote work is FTP, FTPS or SFTP: pushing a site to shared hosting, pulling logs or database dumps from a server, maintaining a list of client sites in one Site Manager. The free version includes the features that save the most time, the project ships fixes every few weeks, and the licence is GPL.
It fits less well in two cases. If the work involves S3 buckets, Google Drive or another cloud destination, the free client cannot connect, and the decision becomes FileZilla Pro against other paid clients. And if the real annoyance is switching between a file browser, a transfer client and a terminal all day, the answer lies in how local files and the shell are organised, not in the transfer client.
What to change first
Download the Apple silicon archive from the official list, verify it against the published .sha512 file, and delete any older copy before judging speed. Then switch on synchronized browsing and directory comparison on day one. If the friction that remains is local folder work with a terminal beside it, Atriens keeps folders and a terminal in one Mac window, free on the Mac, as outlined on the pricing page.
Frequently asked questions
Is FileZilla safe to download on a Mac?
Yes, when it comes from filezilla-project.org. The Mac version is a compressed application archive with no setup program, so there is no offer screen to click through. The download page also publishes a SHA-512 checksum file for each release, which can be compared against the archive with the shasum -a 512 command in Terminal.
What is the latest version of FileZilla for Mac?
As of 9 October 2026, the latest stable release is 3.71.1, dated 26 August 2026. Separate archives exist for Intel and Apple silicon Macs, and both require macOS 10.13.2 or newer. The version history page lists every release with its changes.
Is the free FileZilla enough, or is FileZilla Pro needed?
If every server uses FTP, FTPS or SFTP, the free client covers it. FileZilla Pro adds cloud destinations such as Amazon S3, Google Drive, Dropbox, OneDrive and WebDAV. On macOS, Pro starts at 12,99 € for one device and 29,99 € for up to three devices, according to the vendor's page.
Why is FileZilla slow on an M1 or M2 Mac?
Two common causes. The download page offers the Intel build by default, which runs through Rosetta translation; the Kind column in Activity Monitor shows Intel or Apple. The other is a transfer speed limit left switched on, since limits persist between sessions until turned off in the settings.
Does FileZilla store my passwords securely?
The free client can save site passwords, and the FileZilla Pro page lists a master password that stores saved passwords encrypted. Whichever version is used, choosing SFTP or FTPS rather than plain FTP matters more, because plain FTP sends the password across the network without encryption.