Mountain Duck 5.3.2 Mac

Anyone who has used Cyberduck to transfer files will find a familiar logic in Mountain Duck. Where Cyberduck opens a connection for manual uploads and downloads, Mountain Duck takes the next step: it mounts that same remote storage directly as a disk in Finder, so every Mac app can open, edit, and save files without a separate transfer step.

How it works with your existing toolkit

After connecting a service — the current version supports FTP, SFTP, WebDAV, SMB, Amazon S3, Google Drive, Dropbox, Backblaze B2, and several others — the volume appears in Finder and in any Open or Save dialog. Because bookmarks are shared with Cyberduck when both apps are installed, a server profile you set up in one tool is immediately available in the other. Files are downloaded only when opened, a behavior the developer calls Smart Synchronization, and the local cache is trimmed on demand.

Offline work and version safety

Files stored on the local disk remain available without a connection. As of version 5, Mountain Duck adds storage-independent file versioning, so you can retrieve earlier drafts of a document regardless of which backend holds the data. For sensitive material, encryption at rest is supported through compatible Cryptomator storage, keeping the plaintext off the remote server.

How Mountain Duck stacks up against similar tools

Three Mac apps tend to surface in the same conversation: ExpanDrive, CloudMounter, and Mountain Duck itself. ExpanDrive covers many of the same protocols and also mounts cloud storage as a Finder volume. The difference is in the caching engine — ExpanDrive streams files on demand, while Mountain Duck downloads them in full when opened, which makes repeated access noticeably faster on slow connections. CloudMounter takes a different approach by routing everything through a single helper app and encrypting on the fly, but it does not offer the same breadth of protocols as Mountain Duck; SMB and Backblaze B2 are absent from its lineup. Where Mountain Duck pulls ahead is in its quiet integration with Cyberduck bookmarks and the Cryptomator-compatible encryption layer, both of which feel like they belong to the same workflow rather than being bolted on.

Switching to SMB without leaving Finder

Version 5 brought SMB support, and that changed the equation for people who maintain Windows file servers alongside cloud buckets. A network admin who once kept two separate tools — one for the office NAS over SMB and another for the team’s S3 backups — can now manage both from the same Mountain Duck menu bar icon. The volume label shows up in Finder with the server’s name, permissions behave as expected, and a file dragged from an SMB share to a Backblaze B2 folder copies across without opening a second interface.

A typical working session, step by step

Imagine a photographer who stores client proofs on an SFTP server and final JPEGs in an Amazon S3 bucket. Monday morning begins with a coffee and a Wi‑Fi check. The Mountain Duck icon sits in the menu bar, and a click reveals two saved bookmarks: “Client Proofs” and “Delivery Archive.”

She selects the SFTP bookmark. Within a second, a new volume appears on the desktop — no password prompt, because the keychain stored the credentials last week. The volume opens in Finder, showing a list of project folders. She navigates to “Wedding / May 2025 / proofs,” double‑clicks a RAW file, and Lightroom launches. The file downloads in the background; a small progress indicator in the Finder sidebar shows the transfer. She makes a crop, hits Save, and the updated file uploads automatically when the connection is available. There is no “upload” button, no transfer queue to monitor.

Next, she right‑clicks the “Delivery Archive” S3 bookmark and chooses “Mount.” A second volume stacks below the first. She drags the finished JPEG folder from the SFTP volume to the S3 volume. Finder copies the files as if both locations were local disks. Mountain Duck handles the SFTP‑to‑S3 hop in the background. By the time she pours a second coffee, the copy is complete and both volumes sit idle, waiting for the next file that needs attention.

Common snags and how to sort them out

No tool that juggles a dozen protocols avoids occasional friction, and Mountain Duck users report a handful of repeat issues.

Volume fails to mount after a macOS update. The system sometimes revokes the kernel extension approval. Open System Settings, navigate to Privacy & Security, and look for a prompt about “David Kocher” software near the bottom of the window. Allow it, then try the bookmark again. A restart is rarely needed, but dismounting all volumes before the update avoids the problem entirely.

Files appear with zero‑byte size in Finder. This almost always traces back to Smart Synchronization. A file that has not been opened yet shows a placeholder; the content is fetched only on first access. Double‑clicking the file triggers the download. If it still shows zero bytes, the connection may have dropped mid‑fetch — unmount the volume, verify the network, and mount again.

Cryptomator vaults report decryption errors. Mountain Duck relies on a compatible Cryptomator implementation, and the most common cause is a vault created with a newer Cryptomator version that uses settings the app does not yet parse. Creating the vault directly through Mountain Duck’s bookmark editor avoids this mismatch. When migrating an existing vault, check that it uses AES‑256 and not a newer cipher before connecting.

Mountain Duck and Cyberduck bookmarks drift apart. The shared bookmark library works only when both apps run the same major version and the preference “Save bookmarks to Keychain” is enabled in Cyberduck. Toggling that setting and restarting both apps usually re‑syncs the list within a minute.

Users who hit an unfamiliar snag often find that the menu bar icon’s “Show Log” option surfaces a clear error line — a time‑out, an authentication rejection, or a protocol mismatch — that narrows the troubleshooting to a single setting on the server side.

• macOS 13 or later
• Apple Silicon or Intel Mac