Mountain Duck Mounts Cloud Storage as Local Disks
Mountain Duck is a desktop utility that presents remote servers and cloud storage as a drive in the file manager, so you can work with distant files using the tools you already have. Connect an account, choose the bookmark, and a volume appears; double-clicking a spreadsheet opens it in the spreadsheet application, and saving writes back to the server. Files that are not needed locally stay in the cloud and are fetched on first access, while anything you mark for offline use is kept on disk. Version information, sync status, and transfer history sit in the menu bar. It removes the separate upload step from everyday work.
Mountain Duck inherits its engine from Cyberduck, an open-source transfer client, which is why the protocol list is unusually broad: FTP, SFTP, WebDAV, S3, Azure, Backblaze B2, Google Drive, Dropbox, OneDrive, OpenStack Swift, and WebDAV-based services such as Nextcloud. Bookmarks are shareable between the two applications, and connection profiles define custom endpoints. Cryptomator-compatible vaults add client-side encryption, so files are encrypted before they leave the machine and stay unreadable on the provider's infrastructure. Recent versions integrate with the operating system's own cloud file APIs, which means no driver installation and a familiar status-column experience. Where a browser-mounted volume is the wrong model, a conventional transfer client such as SmartFTP Client still handles one-off publishing jobs cleanly.
Benefits of Using Mountain Duck
What makes Mountain Duck worth its disk-space-free promise is that it removes the decision between local and remote. There is no staging folder to manage and no manual upload after editing, because saving to the mounted volume is the upload. Files you use regularly are cached, so they open instantly even on a slow link, and files you never touch cost nothing in local storage. Background transfers mean a large commit does not block the application you are working in, and status icons make it obvious when something is still in flight. For teams on object storage, that behaviour turns an S3 bucket into something a designer can use without learning a command-line tool. Client-side encryption covers the last objection, since the provider sees only encrypted blobs.
Comments