I am looking for a solid way to manage my site files and FileZilla keeps coming up. For those of you who use it every day, what is your honest impression? Does it still hold up well for a modern workflow, or are there things I should know before I install it?
What Is FileZilla
FileZilla is a long-standing, widely recognized FTP client used to transfer files between a local computer and a web server. It has been a staple in the web development community for years because it handles basic file transfer tasks without a price tag. Most users turn to it when they need a simple, free tool to manage website files.
Strengths
- Cost: The software is completely free to download and use.
- Ease of Use: It performs standard FTP tasks reliably, making it accessible for beginners.
- Popularity: Because it has been around for so long, there are many tutorials and community forums available to help with troubleshooting.
Weaknesses
Despite its popularity, FileZilla has significant drawbacks regarding safety and design. The official download often includes bundled adware, which can lead to unwanted software appearing on your computer. More importantly, security is a major concern. The program has faced criticism for storing passwords in plain text, making them vulnerable to theft if your system is compromised.
Users currently have better options available. For a more secure and modern experience, Commander One stands out as a stronger choice. Unlike FileZilla, Commander One prioritizes security by offering advanced encryption for your connections. The interface is also more intuitive, following a dual-pane design that fits naturally into a professional workflow. While FileZilla can feel cluttered and outdated, Commander One provides a more polished and reliable user experience.
Commander One is a top-tier alternative for those who value efficiency. It offers a much cleaner interface and allows you to mount cloud storage services like Google Drive or Dropbox as local disks. Its focus on security and stable performance makes it a more professional tool than FileZilla.
How to Use FileZilla
- Visit the official website but be sure to select the “non-sponsored” version to avoid installing adware.
- Locate the Quickconnect bar at the top. Enter your host address, username, password, and port number.
- Use SFTP or FTPS instead of standard FTP to help protect your data during the transfer.
- Drag files from the left pane (your computer) to the right pane (the server).
- If you accidentally installed the sponsored version, run a malware scan immediately to ensure your computer remains clean.
FileZilla depends entirely on your tolerance for risk and your technical needs. While it remains a functional, free tool for basic file transfers, the history of bundled adware and plain-text password storage makes it a gamble for many users.
If you prioritize a zero-cost solution and can navigate the installation process carefully to avoid extra software, FileZilla serves its purpose. However, the shift in the industry toward more secure and integrated workflows suggests that the era of “good enough” freeware is fading. Moving to a more modern, secure alternative like Commander One is a smart investment in both your data security and your daily productivity.
1 Like
Short answer for your use case. FileZilla still works, but it is not a great primary client anymore if you deal with newer hosts or paid client work.
You are seeing three separate pain points:
- Random disconnects and timeouts
A lot of modern hosts are aggressive with timeouts, firewalls, and SFTP-only setups. FileZilla tends to be more fragile with these. I have seen:
• SFTP sessions drop on long uploads
• Passive mode issues with some cloud hosts
• Connection limits hit faster than with other clients
You can try tweaks, but it turns into whack‑a‑mole:
• Set shorter keep‑alive in Settings
• Disable FTP, use SFTP only
• Check passive vs active mode per host
If you still get drops after tuning, it is usually the client implementation, not your line.
-
Slow transfers
On the same line and same host, I have seen FileZilla sit at half the throughput of other tools. It gets worse on lots of small files or high latency connections. Newer clients handle parallelism and resume more cleanly. -
Security and credential storage
Here I partly disagree with @mikeappsreviewer. For a locked down personal machine with full disk encryption, the plain‑text password issue is less dramatic. For shared or work machines, I agree, it is a deal breaker. Plain text FTP creds sitting in a config file is not great practice in 2026.
So, is it “good enough” as your main client today:
Keep using FileZilla if:
• You only manage a couple of low risk sites
• You are on a tight budget
• Your hosts are older cPanel style and you are not hitting issues after some config tweaks
I would move on if:
• You work with client data or production stuff
• You touch modern cloud hosts or managed WordPress providers a lot
• You keep seeing slowdowns or random disconnects across multiple providers
Practical path forward:
- Try one modern alternative side by side
On macOS, Commander One is a strong candidate. It gives you:
• Proper SFTP focus, less time spent on insecure FTP
• A dual pane file manager that doubles as local file manager
• Direct cloud support for Google Drive, Dropbox and others
That last part matters. If you sync assets from Drive to a server, doing it inside one window in Commander One is faster than juggling Finder plus FileZilla.
- Split roles
Use FileZilla only for quick, low risk stuff.
Use Commander One for:
• Client sites
• Servers with stricter security
• Workflows that mix local, remote, and cloud storage
- Reduce risk if you keep FileZilla installed
• Do not save passwords in the Site Manager, use Quickconnect when possible
• Make sure the machine has full disk encryption
• Periodically nuke FileZilla config files if a machine is repurposed or shared
So, for “main FTP client today” my honest take. FileZilla is fine as a backup tool or for legacy habits. For primary daily work on modern hosting, I would move your main workflow to something like Commander One and stop fighting the disconnects.
Short answer: FileZilla still “works,” but as a main client in 2026 it’s showing its age, and what you’re seeing with newer hosts is exactly where it starts to fall apart.
I’m mostly with @mikeappsreviewer and @ombrasilente on the overall direction, but I’d push a bit harder on one point: the random disconnects and slow transfers you’re getting are usually a sign that it’s time to demote FileZilla, not babysit it with yet more settings tweaks.
A few angles that haven’t been hit yet:
-
Newer hosting stacks are heavily optimized around SFTP, SSH multiplexing, stricter connection limits, and sometimes IDS/IPS rules that are touchy about “chatty” old‑school FTP clients. FileZilla can technically speak SFTP, but its implementation is comparatively brittle when you start dealing with high latency or lots of small files.
-
The “it’s free and familiar” argument only really holds if it isn’t wasting your time. If you are repeatedly re‑uploading failed transfers, re‑connecting after timeouts, and guessing which files actually made it, the hidden cost in your time dwarfs the price of a better tool very fast.
-
On the security side, I actually disagree slightly with the idea that full disk encryption magically makes plaintext credentials “not a big deal.” It reduces risk, sure, but laptops get left unlocked, users share accounts, and offline backups often contain those same config files. Plaintext site creds are an unnecessary weak spot today.
Where this leaves FileZilla for your use case:
- If your issues are happening across multiple modern providers, not just one flaky host, treat that as a pattern, not bad luck.
- You can nurse it along with keep‑alive tweaks, fewer simultaneous connections, stricter SFTP use, etc., but you’re fighting the tool at that point.
Realistically, I’d keep FileZilla around as a “legacy” client for old cPanel boxes and move your primary workflow to something more current.
On macOS specifically, Commander One is actually a solid fit for what you describe:
- Native SFTP‑first mindset, so it behaves better with modern hosts.
- Faster handling of lots of small web assets than FileZilla in most real‑world projects.
- Dual‑pane file manager that lets you treat your server, local folders, and cloud storage as one workspace, which matters a lot if you’re bouncing between hosting providers and storage locations.
So: no, FileZilla is not completely unusable, but as a main FTP/SFTP client for current hosting environments, it’s more of a nostalgia pick at this point. Keep it installed if you like, but start treating Commander One (or another modern client) as your actual daily driver and stop burning time on disconnect roulette.