Self-hosted service
UniClipboard/UniClipboard avatar
UniClipboard/UniClipboard

UniClipboard: Peer-to-Peer Clipboard Sync Without a Cloud Account

Real-time clipboard sync across all your devices, local-first, peer-to-peer, and end-to-end encrypted. No account. No cloud dependency. No central server.

1,716 stars78 forksRustAGPL-3.0

At a glance

What is it?
UniClipboard is a local-first, end-to-end encrypted clipboard synchronizer for desktop and mobile, built in Rust under AGPL-3.0. This review covers its P2P architecture, installation paths, encryption model, and current alpha-stage limitations.
Who is it for?
Adopt UniClipboard if you need cross-network clipboard sync without a cloud account and are comfortable with alpha-stage software: expect missing features and potential instability. Do not use it for critical workflows yet, especially on mobile where the current LAN compatibility mode is a separate channel.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

The Problem: Clipboard Sync Without a Middleman

The problem is not just about encryption. It is also about network topology. Many tools only work on the same LAN or require a paid relay. UniClipboard claims automatic NAT traversal and encrypted relay fallback for cross-network sync. That means a desktop on your office network can reach a desktop at home without manual port forwarding. The README emphasizes that the relay only sees ciphertext, so even when the P2P path fails, the fallback does not compromise confidentiality. For a user who regularly moves between networks, this is a meaningful advantage over LAN-only tools.

How UniClipboard Works: Spaces, Invitations, and P2P

Large files use streaming transfer, which means they do not have to fit in memory. That is a practical design choice for clipboard items that can be gigabytes, such as video files. The local full-text search index is encrypted on disk, so searching your history does not expose plaintext to other processes. The Quick Panel is a keyboard-shortcut overlay that shows inline previews for text, links, images, code, and files. The README says it is designed to feel like part of the OS clipboard, not a separate app. That is an ambitious UX goal, and the demo videos suggest it works, but I cannot verify that from the material alone.

Getting It Running: Install Scripts and Build Options

The project also provides a command-line tool called `uniclip`. It mirrors the GUI flow and works headlessly, which is useful for SSH sessions, scripts, and tmux workflows. The CLI is a separate binary, but the README does not detail its exact commands. This is a gap in the documentation, but the existence of a CLI is a strong feature for power users who want to automate clipboard sync from a terminal.

Encryption and Privacy: What the Docs Claim

The local full-text search index is encrypted on disk. That is a good practice, but it also means that search performance depends on the encryption overhead. The README claims search works "in milliseconds, even with tens of thousands of entries," but I cannot verify that benchmark. The claim is plausible given Rust's performance, but it is not a measured result in the material. The passphrase is central to the security model. If you forget it, you likely lose access to your clipboard history. The README does not describe a recovery mechanism, which is a potential failure mode. Users must manage the passphrase carefully.

Mobile Compatibility: The Current LAN-Only Limitation

This is a significant limitation for a tool that promises "across the internet." The desktop-to-desktop sync works cross-network, but mobile is stuck on LAN for now. The README also mentions a bundled iOS Shortcut as part of the LAN compatibility channel. That suggests the mobile experience is a workaround, not a first-class citizen. If your primary use case is sharing clipboard items between your phone and desktop while you are away from home, UniClipboard will not work for you yet. The target architecture aims to make mobile a full P2P peer, but that is future work. For now, treat mobile sync as a local-network convenience.

Alpha-Stage Risks and Wrong-Tool Scenarios

The AGPL-3.0 license is another consideration. If you plan to use UniClipboard as a library or modify it, AGPL-3.0 imposes copyleft obligations. For an end-user tool, that is not a problem, but for a company embedding it in a proprietary product, it could be a barrier. The README does not discuss this, but the license is clear from the repository.

Alternatives: KDE Connect and Syncthing

The key difference in approach is that KDE Connect and Syncthing are typically LAN-oriented or require manual relay configuration, while UniClipboard aims for automatic NAT traversal and encrypted relay fallback. That is a meaningful feature if you regularly work across networks. However, the alpha status of UniClipboard means you are trading maturity for that convenience. If you need reliability today, choose a mature tool; if you value the no-account, encrypted cross-network model and can tolerate instability, UniClipboard is worth trying.

Maintenance and Upgrade Costs

The command-line tool is a plus for automation, but it adds another surface for bugs. The README does not document the CLI's full command set, so you may need to read the source code to understand its options. This is a documentation gap that increases the learning curve. Overall, the maintenance cost is moderate for an alpha project, but the update mechanism's inconsistency is a specific pain point.

Editorial conclusion

Adopt UniClipboard if you need cross-network clipboard sync without a cloud account and are comfortable with alpha-stage software: expect missing features and potential instability. Do not use it for critical workflows yet, especially on mobile where the current LAN compatibility mode is a separate channel. Before relying on it, verify that the invitation code and passphrase flow works across your specific OS versions, test large file transfers for memory usage, and confirm the relay fallback is acceptable for your privacy needs. The project is AGPL-3.0, so review the license implications if you plan to modify or embed it. The concrete next step is to run the one-line installer on a test device and check the Quick Panel behavior, since that is the core experience.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Community notes

Community notes