# UniClipboard: Sync Your Clipboard Across Devices Privately This repository profile is provided by osrepos.com, an open source repository discovery platform. Source: osrepos.com Repository profile: https://osrepos.com/repo/uniclipboard-uniclipboard Generated for open source discovery and AI-assisted research. UniClipboard syncs clipboard text, images, and files across Windows, macOS, and Linux, with iOS and Android companion apps. Its Go/Wails desktop app uses the UniClipboard Engine for encrypted, peer-to-peer sync without an account or cloud dependency. GitHub: https://github.com/UniClipboard/UniClipboard OSRepos URL: https://osrepos.com/repo/uniclipboard-uniclipboard ## Summary UniClipboard syncs clipboard text, images, and files across Windows, macOS, and Linux, with iOS and Android companion apps. Its Go/Wails desktop app uses the UniClipboard Engine for encrypted, peer-to-peer sync without an account or cloud dependency. ## Topics - typescript - desktop-app - cross-platform - privacy - clipboard-sync - clipboard-manager - peer-to-peer ## Repository Information Last analyzed by OSRepos: Tue Nov 03 2026 22:58:29 GMT+0000 (Western European Standard Time) Detail views: 6 GitHub clicks: 2 ## Safety Notice OSRepos shares public repositories for knowledge and discovery only. Review source code, dependencies, licenses, and security implications before running or installing anything. ## Content ## Overview UniClipboard is a local-first clipboard manager for Windows, macOS, and Linux, with iOS and Android companion apps. It keeps searchable clipboard history on your devices and syncs text, images, and files between them, including across networks, without an account or cloud dependency. Its desktop interface is built with Go/Wails and React, while the separate Rust-based UniClipboard Engine handles sync, encryption, and storage; iroh powers peer-to-peer networking. The project is aimed at people who move between devices and want clipboard history without sending readable content to a cloud service. Devices connect directly where possible, with an encrypted relay as a fallback. The phone app's regular sync mode is different: it uses an HTTP service on the desktop and is intended for local networks or a VPN. ## Key Features - Syncs clipboard text, images, and files across paired devices, including over the internet. - Stores clipboard history, previews, and the full-text search index encrypted on disk. - Provides a keyboard-driven Quick Panel for finding and pasting previous items. - Uses short-lived invitations and a shared space passphrase to pair devices without accounts. - Offers a headless `uniclip` CLI for sending, receiving, searching, and managing devices. - Supports per-device content controls, sync pausing, and lost-device removal. - Includes iOS and Android companion apps, with experimental phone pairing as a space member. ## Use Cases - A person working across a Windows desktop and a macOS laptop can keep copied snippets and files available on both. - A developer can search past commands or code snippets locally and retrieve them through the Quick Panel or CLI. - A privacy-conscious household or small team can share a paired-device space without storing clipboard contents on a central cloud service. - Someone can send a screenshot from a phone to a desktop using the mobile companion, while accounting for the regular mode's local-network or VPN constraints. ## Our Take UniClipboard is an actively maintained, feature-rich option for private cross-device clipboard workflows, but adoption means trusting a project whose code contributions are highly concentrated in one person. **Good fit if:** - You need clipboard sync and searchable history across Windows, macOS, or Linux, and value local encrypted storage. - You want direct peer-to-peer connections with an encrypted relay fallback instead of a cloud account. - Your team can meet the AGPL-3.0 obligations and is comfortable with Node.js and Rust in the development toolchain. **Look elsewhere if:** - You need silent background clipboard sync on iOS, or phone sync that works across networks without a VPN or server setup. - Your adoption policy requires broadly distributed project maintenance, since most code contributions come from one person. - You need a permissively licensed component rather than an AGPL-3.0 project. ## Project Health | Signal | Value | |---|---| | Status | **Active**: regular commits and releases | | Last commit | 2026-11-03 (today) | | Commits, last 90 days | 100+ | | Releases, last 12 months | 100+ (latest v1.6.1, 2026-11-03) | | Contributors | 12 (top contributor: 99% of commits) | | Issues closed, last 90 days | 5+ (typically closed in 4 days) | | Pull requests merged, last 90 days | 75 (typically merged in 0 days) | | Project age | 20 months | Checked on 2026-11-03 with the GitHub API. ## Project Facts - Language: TypeScript - License: AGPL-3.0 - Stars: 2k - Forks: 97 - Topics: clipboard-manager, clipboard-sync, clipboardsync, cross-platform, e2ee, efficientnet, linux, local-first - Website: https://uniclipboard.app - Archived: no ## What You Need Detected in the repository: - Node.js (from package.json) - Rust (from Cargo.toml) - A test suite and automated checks on GitHub Actions ## Getting Started On macOS, install the desktop app with Homebrew: ```bash brew install --cask uniclipboard ``` For other platforms and setup instructions, see the [README](https://github.com/UniClipboard/UniClipboard#readme). ## License in Plain Words **AGPL-3.0** (network copyleft). - Commercial use: yes - Modify and redistribute: yes - You must keep: the license notice - Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service) - Includes an explicit patent grant from the contributors A summary, not legal advice: the LICENSE file is what applies. ## Considerations The project is active, with regular commits and releases, and recent pull requests are merged quickly. However, contribution is highly concentrated in one person, and measured issue closures are modest relative to the reported open issue backlog, so teams should assess their support and maintenance needs. Building from source requires Node.js and Rust, along with platform-specific Wails prerequisites and other tools documented by the project. The mobile app's regular sync mode uses plain HTTP with Basic Auth at the listener, is not peer-to-peer, and should be limited to trusted networks or protected by a TLS reverse proxy. iOS cannot silently monitor the clipboard in the background, and the experimental phone device-connection mode has different behavior from regular sync. Upgrading from version 0.19 to 1.0 changes local data and pairing formats, prevents downgrade, and requires devices to be paired again.