How to Install FileZilla on macOS

FileZilla Client is a free, open source file transfer program that speaks FTP, FTPS (FTP over TLS) and SFTP (SSH file transfer). It is the tool most Noiz customers reach for when they need to upload a site, pull a backup down, or fix one file without going through a control panel file manager.

Installing it on a Mac is not the same job as installing it on Windows, and the differences are where people get stuck. There is no setup wizard on macOS. What you download is an application archive, not an installer, so the steps that matter are moving the app to the right place and getting past the Gatekeeper warning on first launch without doing something reckless to your Mac's security settings. This guide covers those macOS specifics and the decisions you have to make along the way.

Last reviewed: 27 July 2026, against the current FileZilla release. This guide is written for Noiz hosting and is kept current against FileZilla. It complements, and does not replace, the official FileZilla documentation linked below.

Official Documentation Reference

• FileZilla Client download page (the only download source you should use)
• FileZilla wiki: Client Installation
• FileZilla wiki: Documentation index
• FileZilla changelog (check what changed before upgrading)
• Apple: Safely open apps on your Mac (what Gatekeeper is doing and why)
• Apple: Open a Mac app from an unknown developer (the current click path for the override)
• Apple: Using Intel-based apps on a Mac with Apple silicon (Rosetta 2)

Prerequisites

• A Mac running a currently supported version of macOS.
• Your macOS account password. You need it to move an app into the system Applications folder and to approve the first launch.
• Administrator rights on the Mac. Without them you can still install FileZilla, into your own home folder instead, as described below.
• Your Noiz FTP details (host, username, password, port), which are in your welcome email and in the Noiz client area. You do not need them to install FileZilla, only to connect afterwards.

Step 1: Download From the Project Site, Not From a Search Result

Go to the official FileZilla Client download page and take the button labelled Download FileZilla Client.

Four things on this page trip Mac users up:

• The sponsored adverts look like download buttons. The page carries large advert blocks styled to resemble the real thing. The genuine button names FileZilla. If a button says Download Now, Start Download or similar without naming FileZilla, it is an advert.
• FileZilla Pro is a different, paid product. It adds cloud storage protocols such as S3 and Google Drive. Nothing on a Noiz hosting account needs it. Take the plain FileZilla download.
• The Mac App Store is not a shortcut. Searching the Mac App Store for FileZilla returns FileZilla Pro and a related Pro utility, not the free client. The free FileZilla Client is not distributed through the App Store.
• Homebrew does not carry it either. There is no FileZilla cask in Homebrew's cask index, so brew install --cask filezilla will not find anything. Use the project download page.

Never download FileZilla for Mac from a third-party download portal. FileZilla is one of the most heavily repackaged applications on the internet. Portal sites wrap it in their own .dmg installer that carries adware, browser hijackers or worse, and they buy search advertising so they outrank the real project. If the address bar does not say filezilla-project.org, close the tab. Nothing about the file being "the same FileZilla" is true once someone else has rebuilt the package.

Intel Build and Apple Silicon

At the time of review the project publishes the macOS client as an Intel build, labelled macOS (Intel) on the download page. On an Apple silicon Mac (M-series) it runs through Rosetta 2, Apple's translation layer. If Rosetta 2 is not already installed, macOS offers to install it the first time you open an Intel application; accept the prompt and let it finish. There is nothing to configure afterwards, and FileZilla's performance under Rosetta is irrelevant for file transfer work, which is bound by your line speed rather than the CPU.

Step 2: Understand What You Actually Downloaded

This is the biggest difference from Windows. The macOS download is a compressed archive containing the finished application, named along the lines of FileZilla_3.x.x_macos-x86.app.tar.bz2. It is not a .dmg disc image and not a .pkg installer.

• In Safari, with the default Open "safe" files after downloading setting on, the archive is expanded automatically. You may never see the .tar.bz2 file at all, only FileZilla.app sitting in your Downloads folder.
• In Chrome, Firefox or Edge, the archive stays as it is. Double-click it and macOS Archive Utility expands it into FileZilla.app beside it.

There is no setup wizard, so there are no bundled offer screens. The sponsored offers that the Windows installer presents are a function of that installer, and macOS has no equivalent step here. Use that as a test: if something claiming to be a FileZilla installer for Mac opens a wizard with licence screens and third-party offers, it did not come from the project. Quit it, delete it, and download again from the project site.

Step 3: Move It Into Applications Before You Open It

Drag FileZilla.app out of Downloads and into your Applications folder. macOS may ask for your password to authorise the move.

Do this before the first launch rather than after. Because the download is an archive rather than a disc image, there is no drag-to-Applications window nudging you to do it, so it is easy to leave the app in Downloads and forget. That causes two real problems:

• App translocation. When you run a quarantined app straight from Downloads, macOS may execute it from a randomised, read-only location instead of where you think it is. The symptom is an app that behaves oddly, most often settings or saved sites that do not persist between launches. Moving the app to Applications and launching it from there stops it happening.
• Accidental deletion. Downloads is the folder people clear out. An application living there gets thrown away by a tidy-up months later, taking nothing with it but leaving you wondering where FileZilla went.

If you do not have administrator rights on the Mac, create a folder named Applications inside your home folder and put FileZilla there instead. It works exactly the same way and needs no password.

Step 4: Get Past the Gatekeeper Warning Safely

The first time you open FileZilla, macOS will very likely block it and show a warning that it cannot verify the developer, or that the app was downloaded from the internet and Apple cannot check it for malicious software.

This is Gatekeeper reacting to the quarantine flag that macOS attaches to anything downloaded by a browser. It is a statement about where the file came from, not a verdict on FileZilla. Handle it like this:

What Not to Do

• Do not run sudo spctl --master-disable or any similar command from a forum post. That switches Gatekeeper off for every application you download from now on, not just this one, and people forget they did it.
• Do not strip the quarantine flag with xattr as a reflex. It skips the check you actually want the next time you download something less trustworthy.
• Do not click through the warning on an app you did not download yourself, from a source you did not choose.

What to Do

1. Dismiss the warning dialogue.
2. Open System Settings and go to Privacy & Security. On older macOS releases this is System Preferences then Security & Privacy.
3. Scroll to the security section. A message names the app that was just blocked, with a button to open it anyway.
4. Confirm with Touch ID or your account password. The app opens, and macOS remembers the decision, so this is a one-off.

Apple moves the exact wording and placement of this control between macOS releases, so if what you see does not match, follow Apple's own Open a Mac app from an unknown developer page for the current path.

The rule that matters: only ever approve an app you downloaded yourself, from a source you chose deliberately. This same dialogue, and this same override, is exactly how a repackaged copy of FileZilla from a download portal gets waved onto a Mac. The click is safe here because you know the file came from filezilla-project.org. That is the only reason it is safe.

Step 5: Confirm the Install Worked

FileZilla opens with a welcome dialogue listing links to the project forums and documentation. Close it. The main window is split into a local file pane on the left, a remote file pane on the right, a message log across the top and a transfer queue along the bottom.

To check which version you installed, open the FileZilla menu in the menu bar and choose About FileZilla. On macOS this sits under the application menu, not under a Help menu as it does on Windows.

If the window opens and About shows a version number, the installation is finished. Everything after this point is configuration, not installation.

Where FileZilla Lives on Your Mac

Worth knowing before you need it:

• The application is /Applications/FileZilla.app, a self-contained bundle. There is no installer receipt, no background helper, no login item and nothing added to your system folders. Uninstalling is dragging that one item to the Bin.
• Your settings and saved sites are not inside the app. They live in a hidden folder in your home directory. In Finder choose Go then Go to Folder and enter ~/.config/filezilla. If that is not there, try ~/.filezilla, which older builds used. Pressing Shift + Command + . in any Finder window toggles hidden items on and off.

Two consequences follow from that split. First, dragging the app to the Bin does not remove your saved connections or stored passwords; delete the settings folder as well if you want a genuinely clean removal. Second, that folder is what you copy across when you move to a new Mac, which saves you rebuilding every site entry by hand.

Two Settings Worth Handling Before You Connect

• Password storage. FileZilla keeps its own credential store rather than using the macOS Keychain, so anything you save sits in that settings folder. The first time you save a connection, FileZilla asks how to handle passwords. Choose the option to protect saved passwords with a master password, which encrypts them at rest. There is no recovery if you forget that master password, so record it in your password manager at the same time you set it.
• Updates. FileZilla checks for new releases itself and prompts you. Leave that on. An FTP client handles credentials and opens network connections, so running an old build is a real exposure rather than a cosmetic one.

When you do connect, prefer an encrypted method. Plain FTP sends your username and password across the network in the clear. Use FTPS (explicit FTP over TLS) or SFTP on your Noiz hosting account.

Next Steps

With FileZilla installed, the next job is adding your Noiz account to the Site Manager:

• How to Connect to Your FTP Account Using FileZilla
• How to Upload the Index File to Your Website via FileZilla
• How to Create or Delete a Directory Using FileZilla
• How to Download Files and Directories to Your Computer via FileZilla

Setting the same thing up on a PC as well? See How to Install FileZilla on Windows, where the installer does present bundled offer screens you need to refuse.

Troubleshooting

Symptom: "FileZilla is damaged and can't be opened. You should move it to the Bin." Despite the wording, this is almost never a corrupted app. It usually means the download was truncated, or the archive came from somewhere that altered it. Delete the app and the archive, empty the Bin, and download again from the project site over a stable connection. Do not disable Gatekeeper to work around this message; a genuinely incomplete download will misbehave later anyway.

Symptom: macOS says the application is not supported on this type of Mac, or asks to install Rosetta. You are on an Apple silicon Mac and the Intel translation layer is not installed yet. Accept the prompt to install Rosetta 2 and let it complete, then open FileZilla again. Apple's Using Intel-based apps on a Mac with Apple silicon page covers it.

Symptom: the download finishes but the archive will not expand. Check the file size against the project page. A file noticeably smaller than expected is a partial download. Some corporate networks and endpoint security tools interfere with compressed archives in transit, so try a different browser or a different network before assuming the file is at fault.

Symptom: brew install --cask filezilla reports no such cask. That is correct behaviour, not a broken Homebrew. FileZilla is not published as a Homebrew cask. Download it from the project page instead.

Symptom: the Mac App Store only offers FileZilla Pro. Different product. Pro is the paid edition and the free client is not distributed through the App Store, so the download page is the route.

Symptom: macOS refuses to let you move the app into Applications. Your account does not have administrator rights on that Mac. Create an Applications folder inside your home folder and put FileZilla there. It runs identically.

Symptom: settings or saved sites do not survive a restart of the app. Check whether you are launching FileZilla from Downloads rather than Applications. Move the app properly, then launch it from its new location, and the problem goes away.

Symptom: FileZilla opens but nothing connects. That is a connection problem, not an installation problem. Check your host, username, port and encryption setting against the details in your welcome email or the Noiz client area, and work through the connection guide linked above.

Symptom: the current release will not run on an older Mac. Recent FileZilla builds require a supported macOS version. Older FileZilla builds exist, but an unsupported macOS is the bigger problem, since it stops receiving security updates. Where you can, move the transfer work onto a Mac that is still supported.

Getting Help

If FileZilla installs cleanly but will not reach your hosting account, open a ticket from the Noiz client area and paste in the exact text from the FileZilla message log. Those log lines tell Noiz support immediately whether the issue is credentials, an encryption mismatch, something filtering the connection on your side, or something on the server, which normally removes a full round of back and forth.