ClipCascade
ClipCascade 3.2.0 is an open-source clipboard synchronization tool for Windows, macOS, Linux and Android, with server or P2P modes, end-to-end encryption, file sync and self-hosting.
What ClipCascade provides
ClipCascade synchronizes text, images and files between trusted Windows, macOS, Linux and Android devices. A central server can relay messages and authenticate clients, while P2P mode establishes a more direct data path after signaling. It is useful for a personal device set, but every connected client becomes part of the clipboard trust boundary.
Encryption and endpoint boundaries
End-to-end encryption reduces the server's ability to read clipboard contents, but it does not protect an unlocked or compromised client. Clipboards commonly contain passwords, recovery codes and private images; pause synchronization before copying sensitive values and clear local history afterward. P2P is not anonymous and can expose network metadata to peers or signaling services.
Self-hosting and release notes
Version 3.2.0 improves P2P recovery, WebSocket heartbeats, Wayland monitoring and multi-platform packaging. Self-hosted deployments should replace published default credentials, use HTTPS/WSS, restrict registration and CORS, set message limits and maintain backups. Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave ClipCascade to this cloud drive
Baidu Netdisk
Save ClipCascade to this cloud drive
ClipCascade 3.2.0 client setup and secure self-hosting guide
Test two trusted devices with non-sensitive text, compare server and P2P paths, then harden a self-hosted service before enabling file or image synchronization.
Before you start
- Prepare at least two trusted devices and avoid production accounts, passwords or private documents during the first test.
- For self-hosting, prepare Java 21 or a container runtime, an HTTPS domain, a persistent database path, backups and a strong administrator password.
- Decide between a central server and P2P, including the signaling, STUN, firewall and peer-address implications of an internet connection.
Installation steps
- 01
Choose the matching client
Select the Windows MSI or portable EXE, the correct macOS architecture, Linux ZIP or TAR.XZ, or Android APK, and verify the package name and version.
- 02
Harden the server before pairing
Change the initial administrator credentials, disable unused self-registration, restrict allowed origins and put the service behind HTTPS/WSS rather than exposing a plain port.
- 03
Configure encryption and limits
Use the same strong end-to-end encryption settings on trusted devices, set sensible clipboard and message-size limits and keep keys separate from server credentials.
Quick start
- 01
Sync a harmless test phrase
Copy a non-sensitive phrase, confirm that only paired devices receive it and clear both clipboard histories after the test.
- 02
Limit content types and devices
Enable only the text, image or file types needed, pair one device at a time and remove a device from the account when it is no longer trusted.
- 03
Test reconnect and revocation
Stop and restart the client, inspect WebSocket or P2P reconnect behavior and verify that a logged-out or revoked device no longer receives updates.
Usage tips
- Automatic clipboard monitoring can capture passwords, tokens, screenshots and file paths; pause synchronization for sensitive copy operations.
- Android monitoring may request additional permissions, and desktop P2P may request network access; grant only the scopes required.
- Self-hosted logs, database backups and signaling metadata require the same privacy review as clipboard contents.
Troubleshooting and uninstall
Why does one device receive no updates?
Check the service address, account, client version, encryption key, WebSocket proxy timeout and clipboard permission. Keep TLS enabled while troubleshooting.
Why do large images or files make a client stall?
Lower the local clipboard and message limits, disable unused image or file sync and retry with a small file. Apply limits on every client because P2P may bypass server-side limits.
- Revoke devices and rotate secretsRemove unused devices, rotate encryption material and administrator credentials and confirm that the old client cannot reconnect.
- Clear local and server dataClear clipboard history, caches and logs before uninstalling. For self-hosting, back up required account data, stop the service and process database and proxy logs according to retention rules.
Frequently asked questions
Does end-to-end encryption make the server fully trusted?
It reduces the server's ability to read message content, but it does not protect unlocked clients, account metadata, configuration mistakes or weak keys.
Is P2P mode more private than server mode?
The data path can be more direct, but signaling and STUN may expose connection metadata and peers still need to trust their own endpoints. P2P is not anonymous.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.