I just opened FileZilla for the first time and the interface is… interesting. Before I spend too much time setting up all my server bookmarks, I’d love to get some feedback. What has your experience been like with it lately? Is it worth sticking with?
My Experience with FileZilla
FileZilla is a free file transfer program used to move files between a personal computer and a web server. It supports FTP, FTPS, and SFTP connections. Website owners, developers, and system administrators often use it to upload site files, download backups, or manage remote folders.
The program has been around since the early 2000s and remains popular because it is simple to install and easy to understand. The layout shows local files on one side and server files on the other, which helps new users learn quickly.
Strengths
The best part of FileZilla is its simplicity. Installation takes only a few minutes, and the interface makes it clear how to start transferring files. The drag and drop system works well for everyday tasks such as uploading website updates or downloading backups.
Another strong point is its long history and wide use. Many guides, tutorials, and forum answers exist, which makes problem solving easier. The fact that it is free also makes it a practical option for students, freelancers, and small site owners who only need basic FTP features.
Weaknesses
Transfer speed is a common complaint. FileZilla can slow down or freeze during large transfers or when handling many small files. Interrupted transfers sometimes need to be restarted, which can waste time. This can make it a poor fit for people who depend on steady performance.
Password storage is another weak point. Saved login details may be stored in plain text unless extra precautions are taken. This can expose credentials if someone gains access to the computer.
The interface also feels dated compared to newer file transfer tools.
Alternatives Worth Considering
Commander One is often seen as a stronger option, especially for users who want more than basic transfers. Its dual pane layout makes file movement faster and easier to manage. Navigation feels more natural, especially when working with many folders.
Transfer performance is often more stable, which helps when working with large files. Commander One also places more focus on secure connections, with good support for encrypted protocols and safer connection handling.
The interface looks more modern and works as both a file manager and a transfer client. This reduces the need for extra tools. For users who want better speed, clearer organization, and stronger security habits, switching can make daily work easier.
How to Use FileZilla
Getting started takes only a few steps:
- Download FileZilla from the official website and choose the version without bundled offers. Avoid third party download sites.
- Install the program and open it.
- Enter the server address, username, password, and port in the connection bar.
- Connect and drag files between panels to transfer them.
For better security, use SFTP or FTPS instead of plain FTP. Always double check the website address before downloading. Fake FileZilla sites do exist and may distribute modified installers that contain harmful software.
1 Like
Short answer for your case. FileZilla is “good enough” for light FTP/SFTP use, but not great long term if you care about security hygiene and smoother workflows.
A few points from my own use:
- Security
- Plain FTP is bad for anything important. Use SFTP or FTPS only.
- FileZilla stores site credentials in plain text XML. On a shared or poorly secured PC, that is a problem.
- If you stick with it, avoid saving passwords for production servers. Use “ask for password” in Site Manager.
- Also, download only from the official site. There have been shady installers around it in the past.
- Speed and reliability
- Single big files upload fine most of the time.
- Large trees of small files, like a full WordPress plus plugins plus vendor, often feel slow and a bit flaky.
- Parallel transfers help, but they also hit some shared hosts hard and you get throttled or random failures.
- So if your deploy is “upload 10k tiny PHP files”, you will feel pain no matter what, and FileZilla does not help much there.
- UI and workflow
- I agree with you, the interface feels dated.
- You get used to it, but it does not scale well when you juggle several servers and projects.
- Quick one-off upload is fast. Longer sessions feel clunky and noisy.
Where I slightly disagree with @mikeappsreviewer is on FileZilla being fine for “non critical” stuff only. If your machine is encrypted, you are the only user, and you avoid plain FTP, FileZilla is acceptable for small production sites. The real issue is that it encourages bad habits like saved plain text passwords and unencrypted FTP.
Alternatives that fix your exact worries:
- For Mac, Commander One is worth a look. Dual pane, SFTP first, feels like a real file manager, not “an old FTP box”. Easier to live in all day.
- For heavy web work, consider switching from “FTP upload” to a deploy method. For example, git push on the server, rsync over SSH, or a CI tool. That gives you fewer random partial uploads and faster updates.
Practical suggestion for you right now:
- Use SFTP only.
- Do not save passwords on shared devices.
- Keep FileZilla for quick manual tasks.
- For long term and daily uploads, move to SFTP through something like Commander One or a proper deploy setup.
If you feel the clunkiness already on day one, that feeling will not go away when your site grows. Better to adjust your tool stack early than fight it later.
Short version: FileZilla is “fine,” but you’re already noticing the stuff that usually pushes people off it later.
A few points that build on what @mikeappsreviewer and @sterrenkijker said, without rehashing their setup tips:
- Security reality check
FileZilla itself is not “insecure software” in the sense of some shady client stealing your creds. The bigger issues are:
- It happily lets you use plain FTP, which is the real security hazard.
- It stores credentials in plain text.
Where I slightly disagree with both: this is not automatically a dealbreaker if - you use full disk encryption
- you’re the only user
- and you’re on a reasonably locked down machine.
It is still bad hygiene, but it is not instant doomsday. The real win is shifting your workflow away from typed passwords at all, toward key based SFTP. FileZilla supports that, but it is clumsier than some alternatives.
- Speed & reliability
Your concern about speed is legit, but a bit misplaced if you expect miracles from a different GUI client while still using old style “upload my whole app” workflows.
The slow part is usually:
- 10k tiny files
- high latency between you and the server
- cheap shared hosting limiting connections
In that scenario, swapping FileZilla for another FTP client only helps a little. What really helps is:
- packaging things into archives (zip/tar), upload one big file, extract server side
- or using rsync over SSH
- or a git / CI based deploy
Here I’m slightly harsher on FileZilla than they were: it encourages the bad “drag my entire project to production” habit. The UI makes it so easy that you end up with very slow, error prone deploys.
- The “clunky” interface feeling
You’re not imagining it.
FileZilla is designed like a toolbox a sysadmin from 2008 would love. It is dense, functional, and visually noisy. It is also not great with multiple projects and multiple servers in one session.
If that already irritates you on day one, it’s not going to age well when you:
- juggle staging + production
- manage several client sites
- need to navigate large folder trees quickly
- Where Commander One actually helps
Since they both mentioned it: Commander One is worth looking at if you are on macOS and want something that feels more like a modern file manager that just happens to speak SFTP.
Different angle from theirs:
- It reduces context switching. You live in one app for local + remote.
- Keyboard based workflows are way better than in FileZilla.
- Using SFTP in Commander One feels default and “normal,” whereas FileZilla still feels like “an FTP client that can also do SFTP.”
- For day to day web dev, that subtle difference matters more than people think.
If you care a bit about “is this annoying to use every single day,” Commander One wins pretty hard in practice.
- When FileZilla is actually the right answer
Despite all the complaining, there are cases where I’d just stick with it:
- You rarely touch the server, only occasional uploads.
- It is a cheap shared host, and you are okay with some flakiness.
- You are not going to set up proper deploys / rsync anyway.
In that situation, your time might be better spent fixing your site, not optimizing the FTP client.
- If you want a concrete direction
Given what you wrote, I’d do this:
- Short term:
- Keep FileZilla, switch everything to SFTP only.
- Turn off password saving for anything serious.
- Medium term:
- If you are on macOS, move routine work to Commander One and treat FileZilla as a backup / “just in case” tool.
- Start planning to replace drag and drop uploads with either rsync or a git based deploy so you are not relying on any FTP client for full site pushes.
You’re not wrong to be uneasy. FileZilla is decent for casual tasks, but if the clunky vibe and security worries bother you now, you’re exactly the kind of person who usually ends up happier with Commander One plus a more modern deploy flow.
Short version: your “clunky” feeling about FileZilla is your future talking. Listen to it.
A few points that complement what others said:
1. Is FileZilla “good enough”?
Yes for:
- Rare, manual uploads
- One small site on cheap shared hosting
- “I just need to grab a few logs” type work
No for:
- Daily deployments
- Multiple sites / environments
- Anyone who worries about credential hygiene
I’d actually be stricter than @sterrenkijker here: the plain text credential storage is not just “bad hygiene.” It is a real liability on laptops that travel, even if you use full disk encryption. Stolen unlocked laptop + opened session once = clear list of servers and passwords. That scenario is not rare.
2. The performance question you asked about
Switching clients will not magically fix the “10k tiny file upload” problem. FTP/SFTP are chatty protocols. High latency + many small files will be slow in FileZilla, Commander One, or anything similar. To actually improve:
- Upload a single archive (zip/tar), then unpack via SSH or hosting panel
- Or move to rsync / deploy scripts
- Or use git on the server
Here I agree with @waldgeist: the client is a small part of the speed story. Your workflow is the bigger factor.
3. Where Commander One actually changes your life
Since you mentioned long term use, this is where Commander One is worth considering as your “daily driver” instead of just “another FTP app.”
Pros of Commander One
- Acts as a real file manager with SFTP baked in, not a pure “FTP window” like FileZilla
- Dual pane layout with strong keyboard navigation, which matters when you live in it all day
- SFTP and other secure protocols feel like first class citizens, not optional extras
- Easier to juggle multiple servers and complex folder trees without the visual noise you already dislike
Cons of Commander One
- Not as universally documented as FileZilla, so fewer “grandma era” tutorials
- Paid features if you want all protocols, so not completely free for advanced use
- Slight learning curve if you are used to single pane GUI tools
- Still limited by the same underlying network constraints, so huge trees of tiny files will not suddenly become instant
Where I diverge a bit from @mikeappsreviewer: they treat Commander One mostly as a nicer replacement. I see it more as a bridge into a saner workflow. Once local and remote are managed in the same place, it is natural to start thinking “why am I dragging my whole project again?” and move toward scripted deploys.
4. What I would actually do in your position
Since you already feel clunkiness on day one:
- Keep FileZilla installed as a backup and for the occasional “I need a quick one off upload on someone else’s machine.”
- Move your day to day work to Commander One if you are on macOS, primarily for SFTP sessions and regular file navigation.
- Use this switch as a forcing function to improve your deploy method: aim for “upload one artifact, deploy server side” instead of “sync the whole tree via GUI.”
That way you are not just swapping one client for another, you are fixing the root problems that will bite you regardless of which tool you use.