Cyberduck feels sluggish: what to measure first

When Cyberduck is slow, the cause is almost always one of five settings, and the symptom tells which one. Thousands of small files crawling usually means per file commands for permissions and timestamps. A rate stuck at the same number points to a bandwidth limit. A download that reaches the end and then sits still is segment merging. Low throughput on big files is the connection mode. Folders that take ages to open are a listing problem, which transfer settings never touch. Every setting named below comes from the official Cyberduck documentation and changelog as read on 9 October 2026, when the current release was 9.5.4 from 25 August 2026.

Name the symptom before touching anything

The GitHub issues, forum threads and Reddit posts that rank for this search share a pattern. Someone reports that the app is slow, several people suggest unrelated fixes, and the thread ends without a clear answer. The reason is that "slow" covers several separate problems. Start by matching what is on screen to one row.

What happens What is actually slow Setting to look at
Many small files crawl, one big file is fine Per file commands Transfers, Permissions and Timestamps
Rate stays at exactly the same number A bandwidth cap Bandwidth control in the transfer window
Download hits the end, then waits Joining downloaded segments Segmented downloads
Big files move well below line speed Too few connections Transfer Files connection mode
Folders take seconds to open Listing round trips Browser settings, server side
Repeated upload resends unchanged files Existing file action Downloads and Uploads, Existing Files

One check comes before any of these. Move the same large file to the same server with another tool, for example scp or sftp in Terminal. If both tools are equally slow, the client is not the variable, and the useful conversation is with the hosting provider. That comparison takes two minutes and ends a surprising number of investigations.

Measure with the transcript and the log

The Cyberduck support page describes two tools that turn an impression into evidence.

The first is the protocol transcript, which prints each request and response as it happens. Open Terminal and run:

log stream --predicate '(process == "Cyberduck") && (category == "transcript")' --level info

Keep that window open, then repeat the slow action in Cyberduck. Read the timing between lines rather than the content.

  • A long wait before each response means latency or a busy server.
  • A burst of short commands with a pause after each file means per file overhead.
  • A steady stream with no gaps means data is moving as fast as the link allows.

The second tool is the debug log. Turn on Enable debug log under Cyberduck, then Preferences, then Connection, repeat the action once, and open cyberduck.log in ~/Library/Logs/Cyberduck. The same Connection pane has a button that reveals the file. According to the support page, the five previous log files are kept as compressed archives next to it, which helps when the slow run happened yesterday.

Measure first because several of the fixes below trade one kind of speed for another. Without a before and after number, there is no way to tell whether a change helped or just moved the delay somewhere less visible.

Small files: two settings that send an extra command per file

This is the most common complaint, the subject of a long GitHub issue near the top of the results, and the one with the clearest official answer. The File Transfers documentation carries two notes in plain words. Enabling change of permissions slows down the transfer rate when uploading many files with FTP. Enabling change of modification date does the same.

Both settings live under Preferences, then Transfers, in the Permissions and Timestamps sections. Each one adds a command after every file. On ten files nobody notices. On ten thousand files those commands can take longer than the data itself.

There is a trade-off that many forum answers miss. The same page states that the timestamp options must be enabled for synchronization to work. Sync decides what changed by comparing modification dates, so switching timestamps off to speed up an upload quietly breaks the next sync.

The practical split is by job:

  1. One way bulk upload: turn off permission changes and timestamp preservation, run the upload, then restore the settings.
  2. A folder kept in sync: leave timestamps on and accept the cost, because correctness depends on it.
  3. Either job: trim the file list before it is queued.

The third point uses the transfer filter, a regular expression under Preferences, then Advanced. The default pattern is .*~\..*|\.DS_Store|\.svn|CVS, which skips backup files and some version control metadata. Adding |\.git|node_modules to that pattern for a web project can remove tens of thousands of files from the queue, and no connection setting will ever beat not sending a file at all.

Connection mode and the parallel limit

For large files moving well below line speed, the connection mode is the main lever. It is set under Preferences, then Transfers, then Transfer Files, or per bookmark under Bookmark, Edit Bookmark, Transfer Files. The documentation lists three options:

  • Use browser connection: reuses the browser window's connection. Browsing stops while the transfer runs, and progress shows only at the bottom of the browser window. Needed only when a server allows one connection per user.
  • Open single connection: one extra connection, files sent one after another. Predictable and gentle on shared hosting.
  • Open multiple connections: files sent concurrently. Usually the biggest gain on large batches.

Above the mode sits a limit on parallel connections, set from the toolbar dropdown in the transfer window on macOS. That one number controls three things at once: how many transfers run in parallel in the Transfers window, how many connections a segmented download uses, and how many connections a multiple file transfer opens. A transfer showing "Maximum allowed connections exceeded. Waiting" is queued behind that limit.

Higher is not always better. Many hosts refuse or throttle beyond a few connections per user, and refused connections are retried, which is slower than a smaller number that works cleanly. Try a modest increase, watch the transcript for refusals, and stop at the point where they appear.

A bandwidth cap that persists

A transfer that sits at exactly the same rate, whatever the file or time of day, is almost always capped by Cyberduck itself. The documentation describes the feature: limit the maximum bandwidth for transfers so they do not take the whole connection. It is set from Bandwidth in the transfer window's toolbar, and the default is configurable in Preferences.

The trouble is that the cap stays. A limit chosen during a video call months ago still applies today. Real network speed fluctuates; a throttle does not. If the rate looks suspiciously steady, check the Bandwidth control before anything else.

The values offered in that menu come from a hidden option, queue.bandwidth.options, listed on the same page. The page also documents queue.upload.priority.regex and queue.download.priority.regex, which choose which files go first inside a folder. Setting the upload rule to .*\.html sends HTML files before images, for example. Neither makes the whole job faster, but sending the files that matter first can make a long upload feel much shorter. Cyberduck's guide to hidden configuration options explains how to add them: save a plain text file named default.properties in the application support folder, with one option per line, then restart the app.

The wait at the end is the merge

A download that reaches its full size and then appears frozen is usually segmented downloading doing its last step. The setting is under Preferences, Transfers, General, Downloads. With it on, a file is fetched in parts over several connections, and the documentation says the parts are merged into the actual file once all segments arrive, with only that final file being usable.

On very large files, the merge takes noticeable time, and the disk is busy while the network is idle. The changelog shows the project has worked on this repeatedly. One past fix addressed composing segments very slowly, and another added an indeterminate progress indicator while segments are joined after a download, so the wait is at least visible in current versions.

Two limits apply. Segmented downloads need the server to accept concurrent connections, so on a host that allows one connection per user they add nothing. And on unreliable links a failed segment leaves parts behind that must be resumed. Some people turn the feature off for that reason, choosing a slower download that never needs repeating.

Repeat transfers: choose the existing file action

When a folder is uploaded again with only a few changes, the setting that matters is what happens to files that already exist. It lives under Transfers, General, Downloads and Uploads, as Existing Files. The documentation defines each choice:

Action What it does Cost on a mostly unchanged folder
Overwrite Restarts every file from scratch; existing files go to the Trash Highest
Compare Skips files with a matching checksum, or compares dates when no checksum exists Low
Resume Appends to partial files, skips those matching in size and checksum Low
Skip Sends nothing that already exists Lowest, but misses changes
Prompt Asks every time Waits for a person

Moving from Overwrite to Compare is often the single largest improvement available on repeated uploads, and it costs nothing. Prompt is not slow in a technical sense, but the transfer finishes only when someone returns to answer it.

Slow folder listings belong to the server

Opening a folder is a different problem from moving files, and none of the transfer settings touch it. Each listing costs a round trip plus whatever time the server needs to enumerate the directory. On a folder with tens of thousands of entries, the server is usually the constraint.

Two things on the client side still help. Showing hidden files makes every listing larger, so leave it off unless needed. On Amazon S3, previous versions of objects used to appear in listings by default. Version 9.5.0, released on 18 June 2026, disabled versioned listing by default and moved it to an option in Preferences. Anyone on an older version, or anyone who switched that option on, is listing more than necessary on versioned buckets. Updating to the current release is a cheap first step.

Beyond that, compare the same listing in another client. If both are slow, the tuning belongs on the server.

A last observation from the threads that rank for this search: sometimes the measurement shows Cyberduck is fine, and the real drag is the constant switching between a transfer window, a Finder window and a terminal. That is a workflow problem, not a protocol one. The comparison page sets the main Mac file managers side by side for that question.

What to change first

Run the transcript command, repeat the slow action once, and match the gaps to a row in the first table. Change one setting only, measure again, and keep it only if the number improved. If the transfer turns out fine and the time goes into moving between windows, Atriens keeps folders and a terminal in one Mac window.

Frequently asked questions

Why is Cyberduck so slow uploading many small files?

The time goes into per file commands, not bandwidth. The documentation notes that changing permissions and changing modification dates each slow the rate when uploading many files over FTP. Turn both off for a one way bulk upload, but keep timestamps on for any folder that is synchronized, because sync depends on them.

A Cyberduck download reaches 100 percent and then stops moving. Is it stuck?

Usually not. With segmented downloads enabled, the parts are merged into the final file after they all arrive, and on a large file that takes a while with the disk busy and the network idle. Current versions show a progress indicator during this step.

Why does a Cyberduck transfer stay at the same speed every time?

A constant rate points to a bandwidth limit set in Cyberduck rather than the network. Check the Bandwidth control in the transfer window toolbar and the default in Preferences. The setting persists until it is changed.

Does increasing the number of connections always speed up Cyberduck?

No. The parallel limit controls concurrent transfers, segmented download connections and multiple file transfers together. Many servers refuse or throttle beyond a few connections per user, and the retries make things slower. Raise it gradually and watch the transcript for refused connections.

What is the latest version of Cyberduck for Mac?

On 9 October 2026, the changelog listed 9.5.4, released on 25 August 2026. Version 9.5.0 from June 2026 turned off versioned listing on S3 by default, which reduces listing work on versioned buckets, so updating is worth doing before deeper tuning.

Back to all posts