Copy on your Mac, paste on your Windows PC. Text, images, and files move directly between your trusted devices on the same local network. If you need devices to catch up while apart, use your own shared cloud folder or WebDAV server. Everything is encrypted on your device first.
A clipboard manager that syncs everywhere without handing your data to anyone.
AES-256-GCM with a key created on your first device and kept in the operating system's secure storage. Encryption happens before anything leaves your device.
For most people, ClipNSync works directly across the same Wi-Fi or wired network with no cloud account. Shared cloud folders and WebDAV remain available when devices need to catch up while apart.
Clips your password manager marks concealed or transient are never captured or synced. Your passwords stay put.
Add a nearby device with a short one-time code. The encryption key moves through an authenticated encrypted pairing session, never in plaintext.
On the same network, trusted devices discover each other and push the same encrypted clip directly over the wire - near-instant.
Link an optional account and send files straight to someone by email. Incoming files from people you have not accepted always ask first, accepted contacts can be trusted to skip the prompt, and you can block anyone or turn off being discoverable entirely - every transfer is end-to-end encrypted. Adding someone who is not on ClipNSync yet opens your own mail app with a ready-to-send invite.
A built-in Usage view shows your relay quota for the day and your last 30 days of transfers: how much you sent and received, and how many went through.
Exclude anything you do not want synced with a regular expression: card numbers, key material, whatever you choose.
Installs and runs as a regular user on macOS, Windows, and Linux. No UAC prompt, no privileged helper, no kernel extensions.
One Rust core behind a menu-bar/tray app on desktop, with iOS and Android companions. Crypto is never reimplemented per platform.
The server only ever sees ciphertext. Encryption keys are created and protected on your devices, not uploaded to ClipNSync.
Everything the app does today, in one list.
Local network by default, with shared storage when you need it.
Device A copies text -> encrypted locally (AES-256-GCM, your key) -> sent directly to a trusted device on your LAN -> or stored as ciphertext in your chosen shared folder -> Device B receives it and decrypts locally -> clipboard updated
LAN delivery is normally near-instant. Shared-folder speed depends on your cloud or NAS provider.
ClipNSync never stores your clips on clipnsync.com or any ClipNSync server - we run no storage of your clipboard data. Clips move one of two ways, and both are end-to-end encrypted on your device first: directly device-to-device over your local network (LAN), or through a cloud folder you already use (iCloud Drive, Google Drive, Dropbox, OneDrive, or Nextcloud), where only encrypted ciphertext is ever stored.
The interface has changed substantially since the early screenshots. The current guide follows the latest desktop design and identifies the published version for each platform.
Start the first device, choose LAN or shared storage, then connect every other device with a short code. Read setup instructions.
Clipboard, Send files, Folder sync, and Usage solve different jobs. See what every tab does.
Run the built-in private health check and follow the highlighted next step. Open troubleshooting.
The security model, in plain terms.
Your first device creates the vault key. Pairing transfers it through an authenticated encrypted session, and each device protects it in operating-system secure storage - never in a config file.
Every clip is AES-256-GCM encrypted before it touches the sync folder or the network. The cloud only holds ciphertext.
Clipboard and folder sync need no account - you own the transport: your cloud folder or your own WebDAV. Add an optional account and you can send files end-to-end encrypted to people by email: direct on your LAN or across the internet when possible, or through an encrypted relay as a fallback. The server only ever sees ciphertext and routing metadata - never file contents, names, or keys.
Crypto lives in one shared Rust core with cross-implementation test vectors as the compatibility contract.
Alpha. Current builds: macOS v0.21.27, Windows v0.21.23, Linux v0.21.23. macOS releases are signed and notarized; Windows SmartScreen may still warn while the app establishes publisher reputation.
| Platform | Build | Notes |
|---|---|---|
| macOS | Universal .dmg | Menu-bar app; Intel + Apple Silicon |
| Windows | Per-user .exe (NSIS) | Installs to %LOCALAPPDATA%, no admin |
| Linux | .deb / .rpm / AppImage | x64 and ARM64 / Raspberry Pi |
| iPhone + iPad | TestFlight build 17 | Join the iOS beta (needs the TestFlight app) |
| Apple Vision Pro | TestFlight build 12 | Join the visionOS beta |
Latest in the Apple betas: files you receive save to Photos (media) or the Files app (everything else), you can share a received file again from File History, and sending from a Mac or Windows PC to your iPhone or Vision Pro works over the internet. Background clipboard capture is impossible on iOS and is not faked.
Download for your computer All builds What's new Platform support Documentation
Quick answers. The complete help guide is in Documentation.
Current macOS releases are signed with a Developer ID certificate and notarized by Apple. Download the current DMG from this site. If macOS still blocks it, do not bypass the warning: verify the file is the current official download and contact support.
SmartScreen warns on any app it has not yet seen widely signed.
Click More info, then Run anyway.
The installer is per-user: it installs to %LOCALAPPDATA%
and never asks for admin or shows a UAC prompt. Signing will remove
the warning later.
Two ways, both end-to-end encrypted - your Nextcloud server only ever stores ciphertext:
~/Nextcloud).
ClipNSync writes encrypted .cns files into it;
Nextcloud carries them to your other devices, where ClipNSync
reads them. Works on macOS, Windows, and Linux.https://your-server/remote.php/dav/files/USERNAME/)
and an app password (Nextcloud: Settings -> Security ->
Devices & sessions -> Create new app password). Choose this
during Cloud storage setup, or later under Settings -> Sync and
storage -> Change sync method.Use the same dedicated ClipNSync folder on every device. If Nextcloud's "Virtual files" feature keeps files online-only, make that folder available offline before using it.
ClipNSync watches a folder your cloud app syncs. Nextcloud, OneDrive, and iCloud can keep files "online-only" as placeholders that download only when opened. If the desktop client is offline or restarting, reading a placeholder fails with messages like "the cloud file provider exited unexpectedly" (Windows os error 404). Two things fix it:
ClipNSync retries temporary cloud-provider failures, but the cloud app still controls whether a placeholder is downloaded. Keeping the dedicated ClipNSync folder offline-available is the reliable setup.
You need stable Rust and your platform's Tauri prerequisites. Then, from the repo root:
cargo test --workspace cargo run -p clipnsync-desktop
Common gotchas:
webkit2gtk and
libappindicator development packages first.xcode-select --install.CLIPNSYNC_PASSPHRASE=<pass> to skip
the keychain while testing.Yes. Everything is encrypted on your device with AES-256-GCM before it touches the folder or the network. The vault key is created on your first device, transferred only through authenticated encrypted pairing, and kept in operating-system secure storage. The storage layer only ever sees ciphertext.
Through a cloud folder, sync is as fast as your provider - usually a few seconds, not instant. On the same network, trusted devices normally exchange clips near-instantly over the LAN.
No. Clipboard, image, and folder sync work entirely through your own cloud folder or WebDAV server, with no ClipNSync account. An account is optional and only unlocks one thing: sending files to other people by email. If you never send files to someone else, you never need one.
Link a free account, then type the person's email. People are findable by their exact address unless they opt out (Profile, "Discoverable by email"), and anything from someone you have not accepted always asks before a single byte is saved. Add them as a contact and they can accept you for a smoother, trusted flow. Either way they get a prompt to accept or decline, and you can block anyone permanently. Every transfer is end-to-end encrypted, and you can mark a contact as trusted to skip the prompt next time. If the person is not on ClipNSync yet, the app opens your own mail app with a ready-to-send invite - the message goes out from your mail account, never from our servers.
ClipNSync picks the fastest path that will reach the other person: a direct connection on your local network, a direct connection across the internet when your networks allow it, or an encrypted relay as a fallback when they do not. In every case the file is encrypted on your device first. The server only ever sees ciphertext and the routing metadata needed to hand the transfer off - never the file contents, file names, or your keys.
Once a day, the desktop app sends us a small ping: a random id generated for this install, the app version, your OS, and your CPU type. That id is not your sync identity - it is separate from the device id ClipNSync uses to sync your clipboard, and it is never sent alongside any account or sync request. This tells us what platforms and versions to keep supporting. On Windows and Linux, fully removing the app sends one final ping with the same fields marked as an uninstall (skipped if you opted out), so our install counts stay honest.
It never includes clipboard content, file names, your email, or anything about your account, and we do not keep IP addresses from these pings. It is on by default; turn it off any time in Settings -> History and privacy -> Share anonymous install statistics.
Questions, bugs, ideas - all welcome.
General questions and private support: support@clipnsync.com. We read every message.
Let us know what is broken or what you would like to see: contact support.