I’m about to start a project that involves working with several different servers at the same time. FileZilla is what I know, but I’m open to hearing what others use in that kind of setup. Do you find it handles that kind of work well, or do you prefer something else for more involved workflows?
I’ve been using FileZilla for years to move files between my laptop and various web servers. It’s one of those programs that feels like it’s been around forever, and for most people, it’s the first name that comes up when you need an FTP client.
FileZilla: My Honest Take
FileZilla is a free, long-established FTP client that most people who work with servers have come across at some point. It supports FTP, SFTP, and FTPS and has been around long enough to become the default recommendation for anyone getting started with remote file transfers. It works on Windows, Mac, and Linux, which makes it a common starting point for beginners and pros alike.
Interface and Everyday Use
The way FileZilla works is pretty standard. You have a dual-pane layout with your local files on one side and the remote server on the other. You just drag and drop files between the panes to start a transfer. There is a transfer queue at the bottom that tracks what is in progress, and a Site Manager where you can save your connection details so you don’t have to type them in every time. It covers the basics well enough, but the whole thing feels dated compared to more modern tools.
Pros
- Free to use: There is no subscription required, which is the main reason I stuck with it so long.
- Huge community: Since so many people use it, it’s easy to find a tutorial or a forum post if you get stuck.
- Cross-platform: It works the same way whether you are on a Mac or a PC.
- Simple tasks: For moving a single small file once in a while, it’s fine.
- Queue system: It can handle multiple transfers at once without much setup.
The Main Problem: Slow Transfers and Hanging
The biggest issue I’ve run into – and the reason I started looking elsewhere – is how often it slows down or just hangs mid-transfer. You’ll start a routine upload, everything looks normal for a minute, and then the progress bar just stops moving. The interface stays open, but nothing is happening. Sometimes you wait and it recovers, but other times it just sits there until the connection times out entirely.
It’s a frustrating experience, especially with larger files or if your internet connection isn’t perfect. FileZilla’s error messages during these hangs aren’t helpful at all. It usually just says “Connection timed out” or “Disconnected from server,” so you never really know if the problem is your network, the server, or the software itself.
Over the years, I’ve tried everything to fix this. I’ve lowered the number of simultaneous connections in the settings, messed with the server timeout values, and switched between passive and active modes. Sometimes these tweaks help for a day or two, but the hanging always seems to come back eventually.
There are a few other things that have worn me down over time:
- The interface gives almost no feedback when a problem starts.
- Plain FTP is the default, which sends your passwords unencrypted, and the app doesn’t really warn you about it.
- Some versions of the installer have included bundled “offers” for other software, which really damaged my trust in the project.
Tips for Getting the Most Out of It
If you’re going to use it, here are a few things that might make it a bit smoother:
- Always use SFTP or FTPS instead of plain FTP to keep your data secure.
- If your transfers keep stalling, try lowering the “Maximum simultaneous transfers” in the settings to 1 or 2.
- Only download it from the official FileZilla site to avoid the junk that comes with third-party installers.
- Keep it updated, as they do put out patches fairly often.
- If you did download it from a random site, run a malware scan just to be safe.
An Alternative Worth Trying
For Mac users who are tired of the hanging issues, I’ve found Commander One to be a much better experience. It supports FTP, SFTP, and FTPS just like FileZilla does, so you aren’t losing any functionality there. The main difference I noticed immediately was the reliability – transfers feel more consistent, and I don’t get that “silent stall” where you aren’t sure if the app is actually doing anything.
It works as a full file manager for the Mac, not just an FTP tool. This is great because you can handle your local file organization and your remote transfers in the same window. It has a built-in Terminal emulator, a process viewer, and lets you see hidden files easily. It also supports MTP, so you can move files to an Android or iOS device without opening another app.
The trade-off is that Commander One is a paid app, whereas FileZilla is free. If you only move a file once a month, FileZilla is probably fine. But if you’re transferring files every day, paying for the extra reliability and features makes a lot of sense.
Final Thoughts
FileZilla is still a working free option if you just need to do basic transfers every now and then. But for regular use, the constant hanging and slowdowns make it hard to stick with. Moving to Commander One has been a more reliable experience for my daily workflow, even though it costs a bit more.
2 Likes
Short answer for daily multi‑server work: FileZilla is “ok, but you will hit its limits fast”.
Where I agree with @mikeappsreviewer:
FileZilla is fine for:
- Occasional small edits.
- One or two simple sites.
- When you are on someone else’s machine and need a free client fast.
Where I disagree a bit:
I do think you can keep using FileZilla for many servers, but only if:
- You accept it as a barebones tool.
- You offload any “organization” to your own system.
Some practical points from managing 30+ client servers daily:
- Site organization at scale
FileZilla’s Site Manager does not scale well.
- No tags.
- No search by note or label.
- Folder grouping is limited.
For more than ~10 clients, it turns into:
- “Which of these 40 entries is the staging box?”
- “Which of these is old and unused?”
Workarounds:
- Prefix names consistently: CLIENT1‑prod, CLIENT1‑stage, CLIENT1‑db, CLIENT2‑prod.
- Use a shared password manager (Bitwarden, 1Password, KeePass) as the actual “source of truth” for hosts and notes.
- Treat FileZilla as a dumb connection list, not your main inventory.
- Daily reliability
What @mikeappsreviewer said about hangs and stalls matches what I saw, but for me it was worst with:
- Many small files over SFTP.
- Long uploads on congested networks.
For daily work this hurts because:
- You start a 2 GB upload, context switch, then comeback to a half‑finished queue.
- Logs do not help you decide if you should retry or debug the server.
If you do:
- Frequent deployments with thousands of files.
- Large backup pulls or pushes.
Then you want:
- Robust resume.
- Clear per‑file errors.
- Better throttling and queue control.
- Security posture
One thing I am harsher on than @mikeappsreviewer:
FileZilla’s default “FTP is fine” feel is a problem if you manage client systems.
You want:
- SFTP only, whenever the server supports SSH.
- FTPS only where legacy vendors force you.
- Plain FTP only on disposable, non‑sensitive stuff and only if you must.
For multi‑client work, I treat plaintext FTP as a last resort, never a default.
- Workflow issues for “many servers”
Things that slow you down over time:
- No quick global search across stored sites.
- No environment‑level grouping like “All production servers” vs “All staging”.
- No real integration with your editor or terminals beyond “open with”.
So you end up juggling:
- FileZilla.
- One or more terminals.
- Your editor.
- A password manager.
- A doc with notes on which box is which.
It works, but it wastes time.
What I recommend instead for your use case
Mac:
- Commander One is a strong option if you live on macOS.
- Dual‑pane file manager plus SFTP/FTP/FTPS.
- Lets you treat remote servers like another pane, next to your local filesystem.
- Better process visibility, better for large transfers.
- You can also use it as a general file manager and for Android/iOS connections.
You pay for it, but if you are on many servers daily, you save hours and frustration over months. That tradeoff makes sense once this is “your job” and not “a hobby”.
Cross‑platform alternatives to consider if you want more structure:
- A client with:
- Tagging of connections.
- Grouping by environment.
- Better logging.
- Good SFTP focus.
I will not list every tool here, but I would look for:
- Native SFTP first, not bolted on.
- Obvious warnings when you try plain FTP.
- Fast search over stored connections.
When to keep FileZilla in your stack
- As a backup client on random machines.
- When a client already uses it and you are doing a 5‑minute fix.
- When you work on a tiny side project and do not want another app.
When to move on
- You touch more than 5–10 servers daily.
- You transfer large archives or tons of small files.
- You need clearer logging and better organization.
So if you are “starting to manage several remote servers for different clients” and expect that number to grow, I would:
- Standardize on SFTP.
- Use a password manager for all connection data.
- Use FileZilla only as a fallback.
- Move your main daily work to something like Commander One on mac or another more modern SFTP client with better organization features.
Short version: FileZilla “works,” but for daily multi‑server work it’s like trying to run a delivery company on a bicycle. You can, but why.
Where I’m in the same camp as @mikeappsreviewer and @yozora:
- It’s fine as a fallback client or for quick one‑off uploads.
- Site Manager is primitive once you have more than a handful of servers.
- The UI gives weak feedback when transfers hang or error.
- It subtly normalizes plain FTP, which is not great for client work.
Where I’ll push back a bit:
- Scaling to lots of servers
You can scale FileZilla to 30+ servers if:
- You keep the “source of truth” in a password manager or config repo.
- You use strict naming like
CLIENT‑prod‑web,CLIENT‑stage‑db. - You accept that finding stuff is slower and there is no tagging, search, or env grouping.
But “can” ≠ “pleasant.” The time cost adds up once you are hopping between clients all day.
- Reliability vs. workflow
The stalling and vague errors are only half the problem. The bigger hidden cost is workflow friction:
- No quick global search across connections.
- No good way to group by environment (prod/stage/dev).
- No tight integration with terminals or editors.
So you end up doing:
- FileZilla for files
- SSH client or terminal for commands
- Password manager for creds
- External notes / docs to track which box is which
It works, but if this is your day job, that context switching is brutal over time.
-
Security posture
I’m even stricter than both of them here: if you’re managing multiple client servers, I would treat plain FTP as basically “only for throwaway legacy junk.” FileZilla lets you pick SFTP/FTPS, but it doesn’t guide you hard enough in that direction. For a tool that a lot of juniors copy by default, that’s a problem. -
What I’d actually do in your situation
Since you’re “starting to manage several remote servers,” I’d set yourself up like this:
-
Standardize on SFTP
One protocol for 95% of servers simplifies everything. FTPS only when a vendor forces it. -
Centralize server info outside the FTP client
Use a password manager or a small internal doc as your master list:- Client name
- Host, port
- Role (prod / stage / dev / backup)
- Notes (weird firewalls, ports, special deploy rules)
Then let your client (whichever you pick) be a dumb connection launcher, not your inventory.
-
Pick a “primary tool,” keep FileZilla as backup
I would flip the relationship:- FileZilla as “emergency tool on random machines.”
- Something better as “daily driver.”
On macOS, I think @mikeappsreviewer undersold how much nicer life gets with a dual‑pane manager.
Commander One is very relevant for what you described:
- Remote SFTP/FTP/FTPS looks like just another pane next to your local files.
- You can jump between:
- Local folder
- Client A prod server
- Client B staging server
using the same UI and shortcuts.
- Built‑in terminal in context of the current folder is huge for real‑world workflows.
- Handling big uploads and lots of small files tends to be more predictable than in FileZilla, especially once you’re constantly moving backups, assets, etc.
Is it paid? Yep. But if you’re literally in and out of servers all day, the “time saved + stress avoided” argument is very real. Free but flaky is actually expensive once you factor in lost time, half‑finished queues and “did that file actually upload or not?” moments.
- When FileZilla is “good enough”
I would still keep it around and not uninstall it in rage:
- Few servers, low traffic.
- Mostly tiny edits, not multi‑GB archives.
- You already have a separate, clean way to track which server is which.
- You’re okay babysitting long uploads sometimes.
- When to move on
Given your description, I’d switch as soon as:
- You’re touching >5–10 servers regularly.
- You’re doing deployments or moving big backups.
- You start losing time trying to remember which entry in Site Manager is the right one.
At that point, a more organized SFTP client or a dual‑pane file manager like Commander One on macOS is just a better fit. Keep FileZilla as the “if all else fails” tool, not the main one.