Download

Install it wherever it belongs

The same core, installed two ways: as the app on a phone, tablet, TV or headset, or as a background service on a computer, NAS or Docker host. Sign in with the same CloudDrive account.

App stores

Phones, tablets, TVs and headsets

Install from the store and sign in with the same CloudDrive account. Core membership and App Pro both live on the account, so they follow you across devices and platforms.

The iPhone and iPad build is in App Store review and installs as soon as it clears. Android is in closed testing and not open to everyone yet — but the universal APK below installs at any time, whatever the store is doing.

What each platform can do, what it requires and what it looks like is on the apps pages.

The app

Direct app downloads

The app and the core service are separate packages, released separately and versioned separately. These are the app builds that do not go through a store: a notarised dmg for macOS, signed installers for Windows and a universal APK for Android. They all check for their own updates in-app.

Current release 1.0.14 · GitHub release

What they need

macOS 12 or later, universal for Apple silicon and Intel. This build is notarised by Apple, so it opens without a security warning, and it runs outside the sandbox — local mounting (which needs macFUSE), Blu-ray BD-J disc menus and USB Native DSD exist only here. The full comparison is on the macOS page.

Windows 10 version 1809 (build 17763) or later, with separate x64 and Arm64 installers — pick the wrong one and the installer says so. Both are code-signed and timestamped. Installing needs administrator rights: it writes to Program Files and sets up the WinFSP driver that mounting uses.

Android 7.0 or later, one package for phones, tablets and Android TV. The universal APK covers arm64-v8a and armeabi-v7a (32-bit ARM); there is no x86_64 build.

iPhone, iPad, Apple TV, Vision Pro and Meta Quest install from their own stores — see above. If you only want mounting and browser management and no player, the core service is enough on its own.

The core service

Core service packages

The core service runs in the background on a computer, NAS or Android device, and does the actual work: connecting clouds, mounting, cross-cloud copying, backup and WebDAV. Once it is installed, open http://<host-ip>:19798 in a browser to reach the management interface. Step-by-step instructions are on the help page.

Current release 1.0.14 · GitHub releases

Windows

Linux

macOS

Mounting clouds as local disks needs macFUSE installed first, and its kernel extension approved afterwards — see letting macFUSE through. You can also install through Homebrew — see the help page.

Android

The APK here wraps the core service as an Android app, with its own web management interface; the tgz archives run the core service inside an existing Android environment. The CloudDrive2 app with the player is a different package, in the section above. Local mounting on a phone requires root; browsing, playback, backup and WebDAV do not.

fnOS

The listing in the official fnOS app centre is still under review. For now, download the fpk package for your architecture and install it manually.

Mirrors

Download from a cloud drive

The same packages as above. Use these when GitHub is slow.

NAS and containers

Running it on a NAS

A NAS runs the same core service, by either of two routes: pull the Docker image, or install the package for its architecture from the list above.

Third-party NAS packages

Please note

These NAS packages come from third parties. Judge them for yourself before downloading — we cannot vouch for their security or stability.

Plugin

The Emby and Jellyfin companion plugin

This one installs on the media server, and makes Emby or Jellyfin work with the CloudDrive2 on the same host. One source tree, two builds.

  • Live library updates, with monitoring off

    The plugin subscribes to CloudDrive2's file-change notifications and hands each one to the server's targeted-refresh entry point. A scraper — tinyMediaManager, MoviePilot, MDCx — finishes in the mounted folder and the film turns up in the library on its own, with real-time monitoring switched off. No recursive walk at startup, no burst of cloud listings, and no reliance on full scans, which are the single biggest cause of cloud-provider rate limiting.

  • Playback-aware prefetch

    At playback start it warms the head and tail of the file — the moov atom or EBML header a player needs for the first frame, and the MKV cues a seek reaches for. Near the end it warms the next file in the same folder, and on stop it closes the reader straight away. Every client benefits, not just the CloudDrive2 App.

  • Zero-config path mapping

    Direct play needs to know which local cloud folder a server's media path corresponds to, and that used to be a hand-written rule. The plugin exposes the mounts and cloud-account identities, and the App works the mapping out itself — matching on account identity rather than folder name, because the same 115 account is rarely named the same on both machines.

Download

Jellyfin takes the DLL, meta.json and thumb.png together in a CloudDrive subfolder of its plugin directory; Emby takes the DLL on its own, no subfolder. Replacing the DLL inside a container needs the container restarted — the server's own restart button is not enough. Full install and configuration notes are in the plugin repository.

What it needs

Server minimum: Emby 4.8.0.80 or Jellyfin 10.11. Verified on Emby 4.9.5 and Jellyfin 10.11.11.

The first two features are server-side only — install the plugin, point it at CloudDrive2, done, with no CloudDrive2 App involved. Live library updates rely on file-change notification, which is a membership (Pro) feature. Zero-config path mapping needs CloudDrive2 App 1.0.14 or later.

The plugin connects to CloudDrive2 with an API token. When you create one, Push Messages and Get Mounts are off by default and have to be ticked by hand — without them the plugin connects, reports healthy, and never updates the library. It never writes, deletes or modifies a file.

Changelog

What changed in each release

Release notes for the core service and the web interface, newest first. The last 10 releases are listed here; everything before them is on the GitHub releases page.

1.0.14(Web3.0.14)
  1. Added account deletion. You can delete your account from the profile page: a confirmation code is emailed to your registered address, and the deletion only goes through once you enter that code. Accounts that were registered automatically by a partner device, and accounts signed in through Xunlei, must first set an email address and password on the profile page before they can be deleted. Deleting an account cancels its remaining balance and all membership entitlements; refunds are not available
  2. Fixed mounted drives hanging under heavy load — when transfers were busy and many requests arrived at once, a mounted cloud drive could stop responding for a long time (hours in extreme cases). This is now properly fixed: requests queue smoothly instead of hanging when the system is busy, and a single failing request returns an error promptly and the system recovers on its own
  3. Smoother rate limiting, less likely to trip the risk controls of 115 and other clouds; raising the rate limit now takes effect immediately
  4. Fixed intermittent "file does not exist" / duplicate-name errors after creating a folder on 115 — a freshly created folder could be misjudged because the cloud's index takes a few seconds to catch up. CloudDrive now detects that delay and retries briefly, so the operation completes normally
  5. More reliable backups — temporary problems such as network hiccups are now retried automatically instead of being skipped, so fewer files are missed
  6. Fixed backups treating a folder as a file, and added automatic cleanup of the invalid tasks left behind by that bug
  7. The membership page now explains what CloudDrive2 App Pro unlocks, and links to it
  8. Other bug fixes and performance improvements

View this release on GitHub

1.0.13(Web3.0.13)
  1. Added resource-usage controls for full scans in multi-cloud backup:
    1. The default number of concurrent backup scans is 1. You can change the maximum concurrency on the backup page; full scans beyond that limit are queued and wait their turn
    2. You can set upper and lower thresholds for the upload task queue. When the number of upload tasks exceeds the upper threshold, scan tasks pause and wait; when it falls back to the lower threshold, scan tasks resume automatically. This prevents too many upload tasks from piling up when scanning large files. Unlimited by default; configurable on the backup page
  2. For cross-cloud copies, you can choose on the Download/Upload page in system settings whether to save the downloaded data to a temporary file during the hash-computation stage, so the source file does not need to be downloaded again for the upload. The temporary file is deleted automatically once the copy completes. This option is off by default
  3. Windows: fixed errors that could occur when editing images on a mounted drive in the system file manager, and fixed thumbnails not refreshing automatically after rotating an image
  4. Fixed the task count shown in real time in the web UI possibly being inaccurate
  5. Web UI: fixed dragging a local file to the root directory creating an upload task that could never complete, along with a file that could not be deleted

View this release on GitHub

1.0.12(Web3.0.12)
  1. Fixed memory growth after a fuse mount: memory no longer grows without bound when media servers such as Emby scan millions of files
  2. Fixed multiple S3 accounts on the same endpoint overwriting each other
  3. Improved performance when accessing files over http, lowering CPU and memory usage
  4. Web UI: added Select All and Deselect All options after entering multi-select mode on mobile
  5. Fixed read-only folders (Guangya Cloud) not being usable as the source directory for a mounted drive or a backup
  6. Other performance improvements and bug fixes

View this release on GitHub

1.0.11(Web3.0.11)
  1. Added support for adding Guangya Cloud. Currently read-only: you can browse directories and read files, but cannot create folders, delete files, rename, move or upload. Login by scanning a QR code with the Guangya Cloud app is supported. A fully functional Guangya Cloud integration will come in a later release
  2. For S3, when no bucket name is specified, all buckets in the account are browsable: ListBuckets (GET /) is used automatically and each bucket is shown as a top-level folder. Both path-style and virtual-hosted-style addressing, and V2/V4 signatures, are supported. The bucket-list root directory is read-only (creating/deleting buckets is not supported)
  3. Fixed file reads possibly failing when connecting to some WebDAV servers that do not support http range requests
  4. Web: added multi-server support. You can connect to the grpc service of another CloudDrive2, which makes it convenient to manage a mobile device's CloudDrive remotely from a desktop browser
  5. Other bug fixes and UI improvements

View this release on GitHub

1.0.10(Web3.0.10)
  1. When purchasing a lifetime membership, if the account still has an unexpired annual or monthly membership, the remaining unexpired portion is automatically credited at the annual rate against part of the lifetime membership price
  2. Fixed authorization failing in 1.0.9 when adding Xunlei and when signing in with a Xunlei account

View this release on GitHub

1.0.9(Web3.0.9)
  1. Added fnOS installation package downloads. The listing in the official fnOS app center is under review; for now you can download the fpk package for your architecture and install it manually
  2. The web file browser now supports media scraper files (.nfo): it recognizes NFO files and posters inside a folder (Kodi/Emby/Jellyfin/Plex compatible) and shows movie information in the file properties panel. This feature only displays already-scraped directories; it does not scrape anything from the internet on its own
  3. With 2FA enabled, if you lose both your recovery codes and your phone app and cannot sign in, you can have a reset code sent to the account email to disable two-factor authentication and sign in with just the account password
  4. Accounts registered automatically by a partner device can be unbound from the original device after changing the email and password, so that a lost or sold bound device does not lead to account exposure
  5. Added a "use multi-threaded download when copying" option in the cloud storage account configuration. When enabled, cross-cloud transfers and backups use the old multi-threaded download behavior
  6. Added a confirmation dialog when locking an already-decrypted folder, to avoid making files unusable by mistake
  7. Fixed directory listing failing in edge cases on macOS when there are multiple mount points, which required remounting
  8. Fixed slow copying of files into encrypted directories
  9. Fixed uploads possibly failing on Windows when editing files directly inside an encrypted folder with editors such as Visual Studio Code
  10. Fixed temporary files being left behind when editing a docx file directly with Word in an encrypted directory on 115
  11. Fixed downloads possibly failing on 32-bit armv7 when accessing large files directly over http
  12. Other performance improvements and bug fixes

View this release on GitHub

1.0.8(Web3.0.8)
  1. Cross-cloud copy performance improvements:
    • Memory usage during the preprocessing and upload stages of cross-cloud copies is greatly reduced
    • Cross-cloud copies to a local folder now use multi-threaded download for higher download speed
  2. Fixed editing files directly inside an encrypted folder through a mounted drive possibly failing
  3. Fixed the Update button being unclickable in some cases when editing a mount point on Windows
  4. Fixed CPU spikes and memory blowup in isolated cases after the service had been running for a long time
  5. Other performance improvements, bug fixes and UI improvements

View this release on GitHub

1.0.7(Web3.0.7)

⚠️ Important security notice (required reading for Windows users)

This release upgrades WinFSP to 2026 beta1 in order to fix the security vulnerability CVE-2026-3006 found in older versions of WinFSP.

  • You must download the full installation package and run the installer again, and restart your system when the installation wizard prompts you to.
  • Do not use the in-app OTA update: OTA only replaces the CloudDrive2 program files and will not reinstall the WinFSP driver, so you will not receive this security fix.
  1. In the 115 configuration screen, the maximum number of download threads is limited to 2; the value set cannot exceed 2
  2. Added a maximum requests-per-second limit in the 115 configuration screen, which cannot exceed 5.0
  3. SMB/SFTP/FTP now support reporting disk space (only on some FTP servers; Pure-FTPd and ProFTPD with mod_facts enabled are currently known to return it correctly, other servers fall back to placeholder values. Due to protocol limitations, AVBL only returns the number of available bytes, so total capacity equals available and used is shown as 0)
  4. Improved the SMB server and share discovery algorithm to work in more scenarios
  5. Improved handling of file rename conflicts:
    • At the core layer (webdav/http/CloudDrive sharing, etc.), a rename conflict now returns a rename failure instead of directly overwriting the old file (which followed POSIX rename behavior)
    • Linux and macOS keep the original Unix rename-overwrite semantics: the old file is deleted first and then the rename is performed; if the old file is a non-empty directory, the error ENOTEMPTY is returned, matching POSIX rename(2) behavior
    • Windows switches from the previous POSIX behavior to the default Win32 MoveFile behavior, i.e. a rename conflict returns the ERROR_ALREADY_EXISTS error and Explorer shows a "destination already exists" prompt
  6. For accounts signed in directly through Xunlei and accounts signed in directly through a partner device, the change-password option is hidden on the profile page, leaving only the change email and password options
  7. Fixed the "copy to clipboard" button in the web UI not working correctly in a non-secure context (when the cd2 URL is http:// and not localhost)
  8. Other performance improvements and bug fixes

View this release on GitHub

1.0.6(Web3.0.6)
  1. Added support for adding three network file system types: SFTP/FTP (FTPS)/SMB, with automatic discovery of SMB servers and automatic discovery of SMB shared directories
  2. When adding a backup, you can now choose not to run a full scan immediately; the default is to run a full scan right after the backup is added
  3. Fixed 1.0.5 possibly hanging while running on some systems
  4. When removing a cloud storage from the root directory of the file browser, you can choose whether to remove it permanently. If not removed permanently, the cloud storage is only removed for the current run and is restored after a restart
  5. Other performance optimizations and bug fixes

View this release on GitHub

1.0.5(Web3.0.5)
  1. Brand-new asynchronous mount engine for macOS: it communicates directly with the macfuse kernel extension and supports fully asynchronous concurrency, so file reads no longer block directory browsing and multiple files can be read and written at the same time. Multiple threads receive kernel requests from the FUSE device simultaneously, avoiding the request backlog caused by a single-threaded bottleneck, which greatly improves how smoothly Finder handles large numbers of file operations. macfuse is detected dynamically at runtime, and when it is not installed an error message is shown instead of the program failing to start
  2. Migrated the upload task database from PickleDB to SQLite, so upload task ordering is preserved after a restart
  3. Fixed an issue where, in some cases, multiple backup tasks were disabled after restarting the machine and could only be re-enabled by restarting the service
  4. Offline download now supports .torrent files: you can drag in or upload a .torrent file directly, and it will be parsed into a magnet link before being added
  5. Added shortcuts for cloud drive configuration and folder disk cache to the context menu, so you no longer have to open the properties panel first to configure them
  6. Local folders no longer show cloud drive configuration or disk cache configuration
  7. Other performance improvements, bug fixes and UI improvements

View this release on GitHub

See every past release on GitHub