The 6 Best Free FTP Clients for Windows, Mac, and Linux in 2026

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Short answer: FileZilla Client is the best free FTP client for most people because it provides an approachable interface on Windows, macOS, and Linux. Choose WinSCP for Windows administration and scripting, Cyberduck for a polished Mac and cloud-storage workflow, CrossFTP for a broad cross-platform alternative, gFTP for a lightweight Linux GUI, or lftp for command-line automation and mirroring.

Before choosing an application, identify the server protocol. Use SFTP when available, FTPS with explicit TLS when the server requires FTP compatibility, and plain FTP only when a legacy system requires it and the network is appropriately trusted. SFTP and FTPS are not the same protocol.

Quick comparison

Client	Best for	Native GUI platforms	Protocols and automation	Free-edition reality
FileZilla Client	Most users and website owners	Windows, macOS, Linux	FTP, FTPS, SFTP; queues, resume, bookmarks, directory comparison	Core client is free. Additional cloud integrations are part of the separate FileZilla Pro product.
WinSCP	Windows power users and administrators	Windows	SFTP, SCP, FTP/FTPS, WebDAV, S3; scripting, synchronization, .NET/COM automation	Free and open source, including its core advanced features.
Cyberduck	Mac users and cloud-oriented transfers	Windows, macOS	FTP, FTP over TLS, SFTP, WebDAV, S3, Google Drive, Dropbox, OneDrive and more	Free software with a donation prompt. Contributor registration or store versions remove the prompt.
CrossFTP	Cross-platform users wanting a FileZilla alternative	Windows, macOS, Linux	FTP, FTPS, SFTP, WebDAV, S3 and other cloud protocols	Free tier supports basic transfers; synchronization, scheduling, remote search, speed limits and other advanced features require Pro.
gFTP	Linux users wanting a small GTK application	Linux and Unix desktops	Primarily FTP-oriented, with support varying by build; queues and resumable transfers	Free and GPL-licensed, but dated and distributed in a beta-era package line.
lftp	Scripts, cron jobs, backups and mirroring	No GUI; Linux/Unix command line, Windows through MSYS2	FTP, FTPS, HTTP/HTTPS, SFTP and more; recursive mirror, queues, retries and parallel jobs	Free and GPL-licensed. Powerful, but not beginner-friendly.

This is a use-case ranking, not a speed benchmark. There is no controlled, current test comparing all six clients under identical server, network and file conditions, so claims that one is universally fastest would be misleading.

Version and availability notes in this guide were checked against the linked project pages on August 9, 2026. Software versions and installer options can change.

What an FTP client actually does

An FTP client is a desktop or command-line program that connects to a remote file server. A graphical client normally shows local files on one side and remote files on the other, allowing you to upload, download, rename, move and delete files. Most also provide transfer queues, bookmarks, resume support and connection logs.

Common uses include:

• Uploading a WordPress theme, plugin, image or other website file.
• Downloading logs, backups or media from a hosting account.
• Moving a compiled application or deployment package to a VPS.
• Editing a remote configuration file through an external editor.
• Comparing local and remote directories before a deployment.
• Synchronizing a website or backup directory.
• Automating recurring transfers from a server without opening a desktop application.

Despite the name, an FTP client may support protocols that are not FTP at all, including SFTP, WebDAV, SMB and S3-compatible object storage. Your client can offer a protocol only; the remote server must support that protocol too. A website’s public HTTPS address is also not necessarily its FTP or SFTP hostname.

FTP vs. FTPS vs. SFTP: choose the protocol first

Protocol	What it is	Encryption	Common port	Typical use
FTP	The original File Transfer Protocol	None by default	21	Legacy systems or controlled internal networks
FTPS	FTP protected with TLS	TLS encryption	21 for explicit TLS; 990 often for implicit TLS	Hosting and enterprise systems that require FTP compatibility
SFTP	SSH File Transfer Protocol	SSH encryption, authentication and integrity protection	22 commonly	Linux servers, VPSs, secure hosting and administration

Port numbers are conventions, not proof of a protocol. An administrator can configure SFTP on a port other than 22, or FTPS on a nonstandard port. Always use the hostname, protocol and port supplied by the hosting provider or server administrator.

Plain FTP sends login credentials without built-in encryption. Microsoft documents this risk for ordinary FTP authentication in its FTP authentication guidance, while the relevant protocol standards define FTP, FTP over TLS and SSH separately. Do not select plain FTP simply because a hosting control panel lists it first.

1. FileZilla Client: best free FTP client for most people

FileZilla Client is the easiest general recommendation for readers who want a familiar two-pane graphical interface across Windows, macOS and Linux. It supports FTP, FTPS and SFTP, and includes transfer queues, resumable transfers, drag-and-drop, bookmarks, a Site Manager, directory comparison, filters and remote-editing workflows. The official feature list and WordPress connection guide document the core capabilities.

Best for

• Beginners connecting to shared hosting.
• WordPress owners maintaining server files.
• People who move between Windows, macOS and Linux.
• Routine uploads, downloads and remote file management.

What is free?

The core FileZilla Client is free and supports the principal FTP, FTPS and SFTP workflows. FileZilla Pro is a separate paid product for additional cloud-storage protocols and should not be treated as part of the free client. The official FileZilla site and FileZilla Pro site distinguish the products.

When downloading for Windows, use the official download page and read every installer screen. The project has used sponsored or bundled-offer installer choices in the past, and the exact labeling can change. If the page distinguishes sponsored, non-sponsored, portable or package options, select the option appropriate for you rather than clicking through automatically. The official download page is the right place to check the current choices.

How to connect

1. Open File → Site Manager.
2. Click New Site.
3. Enter the exact server hostname supplied by your host.
4. Choose SFTP – SSH File Transfer Protocol if the server supports it.
5. Enter the username and password, or configure the supplied SSH key.
6. Enter the administrator’s port. Use 22 only if that is the configured SFTP port.
7. Verify the SSH host-key prompt before accepting it.
8. Use the advanced settings to set local and remote default directories if you will reuse the connection.

For a temporary test, FileZilla’s Quick Connect bar can accept a host, username, password and port. An SFTP connection can be identified with an sftp:// prefix. Use Site Manager for saved profiles and repeat connections; the FileZilla usage documentation explains both approaches.

Limitations

FileZilla is not the strongest choice for unattended deployment or complex scheduled jobs. WinSCP has deeper Windows scripting and synchronization tools, while lftp is more capable for shell-based mirroring. FileZilla’s directory comparison helps you inspect differences, but do not assume it includes every advanced synchronization feature found in paid products.

Verdict: Choose FileZilla when you want the simplest secure GUI that works on all three major desktop operating systems.

2. WinSCP: best free FTP client for Windows power users

WinSCP is a free, open-source Windows file manager and transfer client built particularly well for SFTP administration. It also supports SCP, FTP/FTPS, WebDAV and S3, and adds scripting, synchronization, queues, portable operation, Windows integration and a .NET/COM automation interface. Its official overview lists the major capabilities.

As of the date checked, the official download page lists WinSCP 6.5.6 as the current stable release. It also lists 6.6.2 RC, a release candidate. Ordinary users should normally choose the stable release rather than a release candidate unless they specifically need to test it. See the current downloads page before installing.

Best for

• Windows administrators managing Linux servers.
• PowerShell, batch and scheduled transfer jobs.
• Directory synchronization and deployment workflows.
• SSH-key authentication.
• Users who prefer an Explorer-like or Commander-style interface.
• People who need a portable Windows copy.

How to connect

1. Open WinSCP; the Login dialog appears.
2. Select the correct File protocol.
3. For SFTP, choose SFTP. For FTP over TLS, choose FTP and then select the appropriate FTPS invocation method.
4. Enter the hostname, username, password or key, and port.
5. Click Save to create a reusable site.
6. Click Login.
7. Verify the SSH host key or TLS certificate when prompted.

Do not select SFTP merely because both SFTP and FTPS contain the letters FTP. WinSCP’s connection guide explains the distinction and the correct FTP-over-TLS setup.

Automation example

open sftp://user@example.com/ -hostkey="ssh-ed25519 255 <verified-fingerprint>"
put C:/path/file.txt /home/user/
exit

Replace the placeholder fingerprint only with a value obtained and verified from the server administrator or another trusted existing connection. Never copy a host key blindly from an unrelated example. WinSCP documents open, put, get and synchronize in its automation guide.

Trade-offs

WinSCP’s main disadvantage is platform coverage: its native GUI is for Windows. Its extensive settings can also overwhelm a first-time user. SCP remains available for compatibility, but SFTP is usually the better default when both are offered. Finally, synchronization can overwrite or delete files if its direction and deletion settings are misunderstood, so preview changes and keep a backup.

Verdict: Choose WinSCP if you use Windows and need more than occasional drag-and-drop transfers.

3. Cyberduck: best free FTP client for macOS

Cyberduck provides a polished graphical workflow on macOS and Windows and is especially useful when file transfers involve both a traditional server and cloud storage. It supports FTP, FTP over TLS, SFTP, WebDAV, SMB, S3, Google Drive, Dropbox, OneDrive, Azure, Backblaze B2, OpenStack Swift and other services. Its official product page lists the supported services.

The download page checked for this guide reports Cyberduck 9.5.2, dated July 2, 2026. It lists macOS 10.13 or later for Intel and Apple Silicon systems and Windows 10 64-bit or later. The page displays a macOS archive filename that does not exactly match the displayed version number, so use the displayed release information and official download page rather than inferring a version from the filename. See Cyberduck’s current requirements.

Best for

• Mac users who want native-looking system integration.
• Users combining SFTP or FTP with cloud storage.
• External-editor workflows.
• Credential storage through macOS Keychain or Windows Credential Manager.
• Users who need client-side encryption through supported Cryptomator vaults.

Free-edition reality

Cyberduck is free software, but a donation prompt appears after installation or updates. A contributor registration key or store purchase removes that prompt. This is not the same as a time-limited trial or an upload quota; the application remains usable without paying. The official download information explains the arrangement.

How to connect

1. Choose File → Open Connection.
2. Select FTP, FTP-SSL or SFTP.
3. Enter the server, username, password or key, and port.
4. Verify the SSH host key or TLS certificate when prompted.
5. Drag files into or out of the browser window.
6. Create a bookmark when the connection will be reused.

Cyberduck documents Quick Connect, bookmarks and the Open Connection workflow. For SFTP, it can use public-key authentication and relevant OpenSSH configuration. Accepted public-key fingerprints are stored in the user’s known_hosts file in ordinary desktop installations; a changed fingerprint still requires independent verification. See the SFTP documentation.

Cyberduck can also open Cryptomator-compatible vaults, which encrypt filenames, directory structure and file contents through the vault format. That protects data stored in the vault, but it does not turn an ordinary FTP connection into an encrypted one. Details are in the Cryptomator integration guide.

Linux qualification

Cyberduck’s desktop GUI is officially for macOS and Windows. Linux users can use the duck command-line interface, available for macOS, Windows and Linux, but that is not the same as a native Linux Cyberduck desktop application. The CLI documentation covers that option.

Verdict: Choose Cyberduck for a Mac-first workflow or when FTP/SFTP and cloud storage need to live in the same application.

4. CrossFTP: best broad cross-platform alternative

CrossFTP is a Java-based client for Windows, macOS and Linux. Its free edition supports FTP, FTPS, SFTP, FXP, WebDAV, Amazon S3, Glacier, Azure, Google Cloud Storage and OpenStack Swift. It uses a traditional two-pane, tabbed interface and is a practical alternative when you want the same application on all three desktop platforms. The feature comparison lists the protocol support and edition differences.

The official download page checked for this guide lists CrossFTP 2.01.2, with Windows, macOS, Debian/Ubuntu and portable packages. The portable package requires JDK 17 or later; the Windows installer includes its runtime, and the macOS package is listed for OS X 10.11 or later. Check the current download page because runtime and operating-system requirements can change.

Best for

• Users who need one GUI across Windows, macOS and Linux.
• People transferring between FTP servers and cloud services.
• Users who like a tabbed, two-pane file manager.
• Readers seeking a free alternative to FileZilla.

Free-tier limitations

The free edition includes basic connections, tabs, encrypted password storage, archives, local search, batch transfer, previews and favorites. Synchronization, scheduling, remote search, speed limits, proxy support, client-side encryption, multipart upload and other features are identified as Pro features in the vendor’s comparison table.

CrossFTP’s performance language should not be treated as an independent benchmark. There is no controlled test here establishing that it is a particular number of times faster than another client. Also distinguish the free client from the 30-day Pro or Enterprise evaluation, which returns to the free edition after the evaluation period. Review the purchase and evaluation terms and the exact license before using it commercially.

How to connect

1. Choose Sites → Site Manager → New Site, or use File → New Connection To….
2. Select FTP, FTPS/TLS or SFTP.
3. Enter the host, port, username and password or private key.
4. Click Connect.
5. Verify the certificate or host key where prompted.

On Linux, use the portable package if your distribution does not provide a suitable build. Confirm that the required Java runtime is available and that you are running a graphical desktop session. The CrossFTP manual documents the connection paths, protocol choices and Linux startup instructions.

Trade-offs

Java and runtime requirements can make installation less seamless than FileZilla. The interface and documentation are also less polished than those of the leading choices, and advanced synchronization and scheduling features are paid-only.

Verdict: Choose CrossFTP when broad protocol support and one GUI across Windows, macOS and Linux matter more than a completely free advanced feature set.

5. gFTP: best lightweight Linux-native GUI, with caveats

gFTP is a small, GTK-based client for Linux and Unix desktops. It offers simultaneous transfers, resumable transfers, queues, recursive directory transfers, bookmarks, remote-directory caching, drag-and-drop and permission operations. Its project and package information are available through the GNU directory listing and Fedora package page.

Best for

• Linux users who want a lightweight, traditional GTK application.
• Basic FTP transfers on a desktop.
• Users who value queues and resume support without cloud integrations.

Why it is not the default recommendation

gFTP’s interface and project history are much older than those of FileZilla, WinSCP and Cyberduck. Fedora’s package information lists the 2.9.1 beta line, and protocol support can depend on the build and distribution packaging. Older documentation describes FTP, FTPS control-connection support, HTTP, HTTPS, SSH and FSP, but that should not be read as a guarantee that every current build provides every modern SFTP feature.

Use gFTP when you specifically want a small Linux-native GUI and can confirm that your distribution’s build supports the protocol your server requires. Do not present it as the most modern SFTP client, a cross-platform program or a replacement for lftp in unattended jobs. The gFTP manual page provides additional feature and protocol detail.

Verdict: gFTP remains a reasonable lightweight Linux option, but FileZilla or lftp is usually a safer default for a new secure or automated workflow.

6. lftp: best for command-line automation and mirroring

lftp is a free, GPL-licensed command-line transfer program for Linux and Unix-like systems. It supports FTP, FTPS, HTTP/HTTPS, SFTP and other operations, with background jobs, parallel transfers, bookmarks, retries, resumable operations, queues and recursive mirroring in both directions. The upstream project page and official manual document its capabilities.

The upstream site lists lftp 4.9.3, released November 8, 2024, and notes that the maintainer has limited time to support the project. Windows users can obtain an MSYS2 package; the MSYS2 package page lists the 4.9.3-1 package and a July 2026 update.

Best for

• Cron jobs and continuous-integration pipelines.
• Nightly backups and repeatable deployments.
• Large directory trees.
• Mirroring a local directory to a server or downloading a remote tree.
• Linux servers without a graphical desktop.
• Users who want shell-composable commands and detailed logs.

Basic interactive workflow

lftp

open sftp://example.com
user username
pwd
ls
put local-file.txt
get remote-file.zip
exit

Use an interactive prompt, protected configuration, an SSH agent or a secret-management system for credentials. Avoid putting passwords directly in shell commands, URLs or scripts because they can appear in shell history, process listings, logs or CI output.

Mirroring examples

# Download the remote directory into a local directory
mirror /remote/site /local/site

# Upload a local directory to the remote server
mirror -R /local/site /remote/site

The mirror command supports continuing jobs, selecting newer files, excluding patterns, limiting recursion, parallel transfers, retries and dry runs. Options such as --delete can remove files from the destination, so test with a dry run and verify the direction before enabling deletion.

Verdict: Choose lftp when repeatability, mirroring and unattended operation matter more than a graphical interface.

Which client should you choose?

Your situation	Recommended client	Reason
I am a beginner uploading website files.	FileZilla	Simple two-pane interface, broad desktop support and straightforward Site Manager profiles.
I manage Windows systems or need PowerShell automation.	WinSCP	Strong SFTP support, synchronization, scripting, portable mode and .NET/COM integration.
I use a Mac and also manage cloud storage.	Cyberduck	Mac integration, Keychain support, external editors and a broad cloud-service list.
I need the same GUI on Windows, macOS and Linux but want an alternative to FileZilla.	CrossFTP	Broad platform and protocol coverage, with a familiar tabbed interface.
I use Linux and want a small native desktop application.	gFTP	GTK-based and lightweight, provided your distribution build supports the required protocol.
I need a nightly backup, deployment or mirror.	lftp or WinSCP	lftp is excellent for shell automation; WinSCP is better when the job runs on Windows.

Feature and licensing questions answered

Which clients support SFTP?

FileZilla, WinSCP, Cyberduck, CrossFTP and lftp support SFTP. gFTP’s available support depends on the distribution build and should be verified before relying on it. Remember that SFTP requires an SSH-enabled server or SFTP service; an FTP account does not automatically grant SFTP access.

Which support FTPS?

FileZilla, WinSCP, Cyberduck, CrossFTP and lftp support FTP secured with TLS. gFTP documentation describes FTPS control-connection support, but the exact behavior depends on the packaged build. In WinSCP, choose FTP and then the appropriate FTP-over-TLS mode rather than choosing SFTP.

Which support SSH keys?

WinSCP, Cyberduck and FileZilla support SSH-key authentication for SFTP. lftp can use SSH’s authentication mechanisms through the command line and the local SSH configuration. CrossFTP and individual gFTP builds may differ in key formats and setup, so check their current documentation and test with a noncritical account. A private key is not a password: select the client’s key-file or SSH-agent option.

Which support scripting or unattended jobs?

lftp is the strongest command-line choice for Unix-like systems. WinSCP provides scripts, synchronization and .NET/COM automation on Windows. Cyberduck provides the duck CLI, including Linux support. FileZilla and CrossFTP are primarily interactive GUI tools for this comparison, while gFTP is not a sensible choice for unattended jobs.

Which support synchronization?

WinSCP has mature synchronization features. lftp provides two-way-style mirroring commands with extensive controls. CrossFTP includes synchronization in Pro rather than its free tier. FileZilla provides directory comparison and manual transfer controls, but it should not be treated as a full replacement for a dedicated synchronization workflow. Cyberduck’s desktop app and gFTP are not the primary recommendations for complex synchronization.

Which support remote editing?

FileZilla, WinSCP and Cyberduck can open remote files through an external editor workflow. This usually downloads a temporary copy, watches for changes and uploads the edited file; it is not the same as editing directly on the server. For configuration files, make a backup and confirm the correct remote path before saving.

Which support cloud storage?

Cyberduck has the broadest cloud-oriented GUI coverage in this list. CrossFTP’s free edition supports several cloud protocols, including S3, Azure, Google Cloud Storage and OpenStack Swift. WinSCP supports S3 and WebDAV. FileZilla’s additional cloud protocols belong to FileZilla Pro, not the core free client. gFTP is primarily a traditional file-transfer client, while lftp is not a general cloud-storage browser.

Which are open source?

WinSCP, FileZilla Client, Cyberduck, gFTP and lftp are free or open-source projects, subject to their respective license terms. CrossFTP is a separate commercial product with a free edition and paid feature tiers. Open source does not mean that you can ignore license obligations, and a free edition does not automatically mean free commercial use. For work, confirm the license for the exact version and edition, especially for CrossFTP and any bundled installer.

Are these clients free for commercial use?

Do not use the word free as though it had one legal meaning. It can mean open source, freeware, free for personal use, a donation-supported application, a free core with paid upgrades or a time-limited trial. WinSCP, FileZilla Client, gFTP and lftp are open-source projects whose licenses should be followed. Cyberduck is free software with a donation prompt. CrossFTP’s free-versus-Pro terms should be checked on its feature page and purchase page before business use.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What you need before connecting

Obtain these details from your hosting provider, system administrator or cloud-service documentation:

• Hostname or IP address: this may differ from the website’s public domain.
• Protocol: SFTP, explicit FTPS, implicit FTPS, FTP, WebDAV, S3 or another service.
• Port: use the supplied value rather than assuming a default.
• Username: some hosts require a full email address or account prefix.
• Password or SSH private key: and the key passphrase if applicable.
• Remote directory: such as a provider-specific web-root directory.
• FTP mode: passive FTP is usually preferable behind home routers and firewalls.
• Proxy or bastion details: required on some corporate or private networks.
• Expected SSH fingerprint or TLS certificate information: needed for meaningful verification.
• Connection limits: some providers restrict simultaneous sessions.

Connect safely: a verified workflow

1. Identify the protocol before entering credentials. Do not use FTP as a generic label for SFTP or FTPS.
2. Prefer SFTP. If the server does not provide it, use explicit FTPS when the server supports FTP over TLS.
3. Enter the exact hostname and port supplied by the administrator.
4. Verify the host key or certificate. A first-connection warning is expected, but a changed SSH fingerprint is not something to accept automatically. Verify it through a separate trusted channel.
5. Start with one connection and one small transfer. Some shared hosts reject clients that open too many sessions.
6. Upload a harmless test file, download it again and inspect the contents. Check filename encoding, permissions and the resulting file size.
7. Set the local and remote default directories. This reduces the chance of uploading to the wrong server path.
8. Use binary transfer mode for non-text files. Images, archives, videos, executables and database dumps should not be altered by text conversion. Automatic mode is generally suitable unless the server or workflow requires a specific setting.
9. Preview synchronization changes. Confirm the direction, disable deletion until you understand the workflow and keep a backup.

FTP-specific passive mode and connection limits

FTP and FTPS use a control connection plus separate data connections for directory listings and file transfers. Those extra connections are why FTP can fail after apparently authenticating successfully. Passive mode usually works better for clients behind a home router, NAT or firewall, but the server must expose an appropriate passive port range.

If a directory listing hangs or you see a data-connection error:

1. Enable passive mode in the client.
2. Ask the administrator whether the server’s passive port range is open.
3. Check local firewall and endpoint-security rules.
4. Reduce simultaneous transfers.
5. Confirm that the FTPS mode matches the server’s instructions.

Do not solve a data-connection problem by silently downgrading to unencrypted FTP. Cyberduck’s FTP documentation explains passive and active modes and the separate data connection in more detail.

Troubleshooting common connection and transfer failures

Connection refused

Usually the hostname, protocol or port is wrong, the service is down, a firewall blocks the port or the SFTP subsystem is disabled. Confirm the exact protocol and port with the administrator. Do not try random ports or switch from SFTP to FTP simply because the first attempt failed.

Authentication failed

Check the username format, password, SSH key, key passphrase and key permissions. Confirm whether the account is an FTP account, an SSH account or both. Some accounts are restricted to a source IP, require keyboard-interactive authentication or have access to FTP but not SFTP. Never paste a private key into a password field.

Directory listing hangs or the data connection cannot open

This is commonly an FTP/FTPS passive-mode, firewall, NAT or passive-port-range problem. Enable passive mode, reduce simultaneous transfers and confirm the server’s passive ports. If the host supports SFTP, switching to SFTP avoids FTP’s separate data-channel design, but only do so after confirming that SFTP is enabled for the account.

Too many connections

Hosting providers often impose per-account or per-IP limits. Set simultaneous transfers to one through three, disconnect stale sessions and avoid opening multiple clients with the same account. Some servers count directory-listing sessions separately from transfers.

Permission denied

The account may be read-only, the directory may belong to another user, the account may be jailed to a different root or the server may prohibit permission changes. Confirm the remote path and ask the administrator to correct ownership or permissions. A client cannot grant privileges that the server account does not have.

Files appear to be missing

Refresh the listing, enable hidden-file display and check the remote path. The account may be chrooted, the web root may be named public_html, www or htdocs, or the server may use case-sensitive filenames. A cached directory listing can also be stale.

A transferred file is corrupted

Retry in binary mode, compare file sizes and use cryptographic hashes when available. Disk-space exhaustion, an interrupted resume, a proxy, the wrong transfer mode or an overwritten destination can all produce an apparently successful but unusable file. Reduce parallelism and try SFTP if the server supports it.

Filenames contain strange characters

Older FTP servers may advertise or assume a legacy character set. Try UTF-8 first, then the encoding documented by the server. Avoid mass-renaming files until you understand whether the issue is display-only or has changed the actual names. Cyberduck documents per-connection encoding options in its FTP guide.

The SSH host key changed

Stop and verify the new fingerprint with the administrator or a previously trusted management channel. A legitimate server migration can change a key, but interception is another possibility. Remove or replace the stored key only after independent verification.

Clients not included in the six

FireFTP is obsolete for mainstream Firefox use. Its own site says that Firefox removed the relevant support and that development ended; Mozilla removed Firefox’s built-in FTP implementation beginning with Firefox 90. See the FireFTP notice and Mozilla announcement.

Transmit, Fetch, ForkLift and CuteFTP may be excellent paid applications, but they should not be described as fully free clients unless the article specifically means a trial. A recent comparison that mixes free and freemium products illustrates why the label needs qualification; see Hostinger’s comparison.

Core FTP LE is a potentially useful Windows alternative, but it is redundant in this six-client selection because WinSCP provides a broader power-user feature set. If you consider it for commercial work, verify the current free-use terms for the exact edition before deployment.

Bottom-line decision tree

• Need one easy GUI on Windows, Mac and Linux? Start with FileZilla.
• Use Windows and need scripting, synchronization or SSH administration? Choose WinSCP.
• Use macOS and combine server transfers with cloud storage? Choose Cyberduck.
• Need a cross-platform alternative and accept paid advanced features? Try CrossFTP.
• Use Linux and want a small GTK desktop application? Consider gFTP, after confirming protocol support and accepting its dated maintenance profile.
• Need cron jobs, CI transfers, backups or directory mirroring? Use lftp on Unix-like systems or WinSCP on Windows.

Whatever client you select, the protocol decision matters more than the brand: use SFTP when available, explicit FTPS when FTP compatibility is required, and plain FTP only for a deliberate legacy or controlled-network exception.

Frequently Asked Questions

Is SFTP safer than ordinary FTP?

Yes, for normal internet use. SFTP uses SSH encryption and authentication, while ordinary FTP does not encrypt credentials by default. FTPS is also encrypted, but it is a different protocol that uses TLS around FTP.

Does SFTP always use port 22?

No. Port 22 is the common default, but administrators can configure SFTP on another port. Use the port supplied by the server administrator rather than assuming one.

Can I use an FTP client to manage a WordPress site?

Yes. A client such as FileZilla can upload themes, plugins, media and configuration files when your host provides FTP, FTPS or SFTP credentials. SFTP is preferable when the host offers it. The correct remote web-root directory and account permissions come from the hosting provider.

Why can I log in through SSH but not through SFTP?

The account may not have an SFTP subsystem enabled, the client may be using the wrong protocol or port, the account may be restricted to a different path, or the server may require a particular SSH key or authentication method. Ask the administrator whether SFTP is enabled for that account.

Should I enable synchronization immediately?

No. First test with a small directory, preview the changes, confirm the synchronization direction and disable deletion. Synchronization tools can overwrite or delete files when their rules are misunderstood.

The Bottom Line

For most readers, install FileZilla Client and connect with SFTP. Windows administrators who need scripting or synchronization should use WinSCP; Mac users who also manage cloud storage should use Cyberduck; lftp is the strongest choice for unattended command-line work. Verify the protocol, hostname, port and host key before transferring anything, and treat plain FTP as a legacy exception rather than the default.