Get Support

Feature Requests

If you have a feature request please make sure to include a detailed and comprehensible description of the requested feature in the ticket. Make sure to check if someone already requested a similar feature.


For issues with your remote storage user account credentials, please instead write to your hosting service provider.

Bug Reports

Open a new ticket with a description of what you have done and what went wrong. Make sure to look or search for existing issues first.


Discuss features and issues you are having in the Cyberduck Google Group. For licensing issues and other support questions, please send an mail to


Please be aware that you are possibly using our software at no charge if you have not purchased a registration key. Thus the support provided here is best effort only.

Logging Output

Reveal the log output named cyberduck.log by choosing Preferences → Connection → Log → Show.

Alternatively, the cyberduck.log file can be found in ~/Library/Logs/Cyberduck.


You can only access the transcript which will log protocol request and responses. It’s particular useful for protocols using HTTP. Open a window and enter

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


The transcript will be written in the window. Make sure to keep the window open after executing the command.

Heap Dump

To create a heap dump of the Cyberduck process on macOS (in case of excessive memory usage for example) you can use jmap from the OpenJDK 13.

jmap -dump:file=cyberduck-dump.hprof [PID of Cyberduck process]

Debug Logging Level

Enable debug logging by choosing Preferences → Connection → Log → Enable debug log. Alternatively this can be configured using the following command line options.

To enable debug logging open a window and enter

defaults write ~/Library/Preferences/ch.sudo.cyberduck.plist logging debug

Reset the logging configuration with

defaults delete ~/Library/Preferences/ch.sudo.cyberduck.plist logging

Restart Cyberduck for any logging configuration change to take effect.

Application Support Folder

Inside the application support folder, the application saves files needed for their operations e.g. settings, log data, history files, etc.

You can reach the application support folder by choosing Go Go to folder within the Finder menu and paste the path ~/Library/Group Containers/ Support/duck/ into the window.

Crash Reports

Crash reports are saved to ~/Library/Logs/DiagnosticReports/Cyberduck_*.crash. On macOS 12 or later crash reports are saved to ~/Library/Logs/DiagnosticReports/Cyberduck_*.ips.