Cyberduck on a budget: the free path and where it stops

Searching for a cyberduck free download usually means one of two things. Either the download has already happened and a prompt keeps appearing, or the Mac App Store listing showed a price and the free claim now looks suspect. Both reactions are reasonable, because Cyberduck is distributed three ways at once and the three do not cost the same thing.

The short version is that the application is free software in the legal sense, not free in the freemium sense. Nothing is feature gated. Nothing expires. What changes between the paths is a prompt, a receipt, and the level of support you are entitled to ask for. Knowing which of those you actually care about settles the question in about two minutes.

What free means in this particular case

Cyberduck is licensed under the GPL and the source is on GitHub. The project page states the position plainly:

Free software is a matter of the users freedom to run, copy, distribute, study, change and improve the software. The continued donations of users is what allows Cyberduck to be available for free today.

That is a different promise from a trial. There is no thirty day clock, no file size ceiling, no protocol held back for paying users. The build downloaded from the project site and the build sold in the Mac App Store are the same application at the same version number. As of this writing both sit at 9.5.4, released on 25 August 2026.

The system requirement attached to that build is macOS 10.13 or later, on either 64 bit Intel or Apple silicon. That is unusually generous for 2026 and it is one of the genuine reasons people stay on Cyberduck. A Mac that no longer receives security updates from Apple can still run a current version of this client, which is not true of most commercial transfer tools.

The trade the project makes in exchange is visibility. Because nothing is withheld, the only lever available to fund the work is asking. That ask is the prompt, and the prompt is what most people are searching about when they type the word free.

The donation prompt and what the key removes

Contributing gets you a registration key. The project describes the minimum and the effect in one sentence on its donation page: a contributor giving at least 10 USD receives a key that registers the installed application to a name and disables the donation prompt that is otherwise displayed.

Two details matter and are easy to miss. The key is tied to a person, not a machine. The project states it can be used on multiple computers but is personal and is not to be shared. If you run a laptop and a desktop, one contribution covers both. If you are buying for a team, the donation form has an installations field that recalculates the amount, so the correct route for an office is that field rather than several separate 10 USD payments.

The second detail is the file itself. The key arrives by email as an attachment ending in .cyberducklicense. The project's own help notes that some email applications rewrite the extension to .xml when saving the attachment, and that a key modified in that way will not register. If a key appears to be rejected, checking the extension before contacting anyone saves a round trip. Keys can also be recovered later using the email address used at the time of the donation, so losing the attachment is not fatal.

The prompt itself is not a nag screen in the aggressive sense. The project describes it as appearing after installing or updating, and its help pages describe it as appearing when quitting. Either way it is a dialog that a key removes, not a restriction on what the application will do.

The three routes compared

Route	What it costs	Donation prompt	Notes
Download from the project site	Nothing	Shown	Same build and version as the paid one
Site download plus registration key	10 USD minimum, one time	Removed	Key is personal, usable on several machines
Mac App Store	23.99 USD on the US storefront	Never shown	Delivered and updated through the App Store

The App Store price surprises people who have just read that the software is free, and the project explains why it exists. The donation key model is not permitted under Apple's developer agreement, because software asking for voluntary contributions does not get approved. Rather than skip the store entirely, the project ships a fixed price build there with no prompt at all. It is the same code under a different distribution rule.

Which route is cheaper depends on something other than the numbers. A single person who wants the prompt gone pays roughly a third as much through the donation page. An organisation that can only expense software through a managed App Store, or that needs the update to arrive through the same channel as everything else, is often better served by the store build even at the higher figure. Neither choice changes what the application can do.

One practical difference does follow from the channel, and it is about updates rather than money. The site build checks for new versions itself, with the feed selectable in the preferences so that snapshot or beta builds can be followed instead of stable releases. The store build updates when the App Store updates it, which is steadier but slower. Anyone who has ever needed a fix that landed in a snapshot build before it reached a release will recognise which side of that trade they belong on. Anyone managing a fleet will recognise the other.

The store price also varies by storefront, since Apple sets local tiers rather than converting a single figure. The 23.99 USD above is the United States listing. Checking the price in the local store before assuming a conversion is the safer habit, and in several storefronts the gap against a 10 USD contribution is wider than the raw exchange rate suggests.

What a free download does not include

The most common misreading is treating Cyberduck as the whole product line. It is not. The same developer publishes Mountain Duck, which mounts remote server and cloud storage as a local disk in the Finder so that ordinary applications can open files directly from it. That is a separate product with its own pricing at mountainduck.io, and no amount of contributing to Cyberduck unlocks it.

This distinction decides more workflows than the price does. Cyberduck presents a remote server in its own browser window. Files move when you tell them to move, into a download folder, and back up when you are done. If the goal is to open a file on a server from a text editor and hit save, that is Mountain Duck's job, not Cyberduck's.

There is also a command line tool, published as Cyberduck CLI, that speaks the same protocols and shares the same bookmarks and connection profiles through a common application support folder. It is a separate download from the same project.

What the free download does include is genuinely broad. FTP and FTP over TLS, SFTP, WebDAV, SMB, Amazon S3, Google Cloud Storage, OpenStack Swift, Azure, Backblaze B2, Box, Dropbox, Google Drive, OneDrive, SharePoint, Nextcloud, ownCloud, Files.com, DRACOON and more, plus client side encryption through Cryptomator vaults. Passwords go into the system Keychain as internet passwords, which means other applications on the same Mac can use them and that removing the app later does not remove them. Thirty localizations ship in the box, Japanese among them. Amazon CloudFront and Akamai distributions can be configured from inside the application, and files can be opened for editing in an external editor without a manual download and re-upload.

For a client at zero cost that range remains hard to beat, and it is worth saying plainly that no paid tier exists which extends it. Whatever the protocol list does not cover, contributing will not add.

The support policy is the real difference

Buried in the support documentation is a warning that deserves more attention than the price does. The project states that anyone who has not purchased a registration key is possibly using the software at no charge, and that the support provided is therefore best effort only.

That is honest and it is also a planning constraint. Bug reports go to a public tracker and discussion happens in GitHub Discussions. There is no response time commitment for anyone, and explicitly less of one for people who have not contributed. Registration key problems have a dedicated support address, which tells you where the paid obligation actually sits.

The same page adds a second piece of triage advice that is easy to resent and usually correct. If a connection fails or credentials are rejected, the project asks that you take it up with the hosting provider first. A large share of what gets filed as a Cyberduck bug turns out to be a server that has disabled a cipher, changed a port, or started requiring a second factor. The client is reporting the refusal accurately.

For a personal machine none of this bites. For a team that depends on a nightly upload to a client's server, it is worth being clear eyed. The mitigation is not to pay more, because the store build buys the same best effort. It is to keep the protocol transcript and the debug log available so that a failure can be diagnosed without anyone else, and to know that previous installers stay published in the project changelog, so a release that breaks a workflow can be rolled back the same afternoon rather than waited out.

Where the free path stops for daily work

Cost stops being the deciding factor once the tool is in daily use, and the honest limit of Cyberduck has nothing to do with money. It is a server browser. It is very good at that. It is not a place to live.

Concretely, a working session tends to look like this. A folder is inspected in the Finder, a terminal is opened somewhere else to check a checksum or run a build, and Cyberduck is opened as a third window to move the result to a server. Three windows, three navigation states, and the mental overhead of keeping them pointed at the same place. Nothing in the free download addresses that, because addressing it was never the project's goal.

People reaching the end of the free path usually want one of two different things. Some want the remote storage to behave like a disk, which is the Mountain Duck answer. Others want the local side consolidated, so that browsing, a shell, and the file operations sit in one window instead of three. That second group is looking at file managers built around that idea rather than at another transfer client, and the comparison is worth making before paying for anything, including a registration key.

If the machine also holds files that arrive from an iPhone or iPad, that transfer path is a separate question again, and one worth settling before committing to a workflow built entirely around a server browser.

What to change first

Download from the project site and use it as it is for a week. If the prompt is the only complaint, the 10 USD key ends the matter and costs less than the store build. If after that week the complaint is that three windows are open to do one job, the problem was never the price, and a file manager with a built-in terminal is what to evaluate next, with Atriens as one of the options to weigh.