Loading...
The Mac app captures your clipboard and syncs it. The iPhone and iPad app receives that history and adds a full keyboard.
Free — there is no paid tier and no billing.
A signed, notarised disk image, downloaded straight from us. Requires macOS 14 or later.
Distributed through the App Store as UniClip - Clipboard Sync. Requires iOS 17 or later.
Both editions are available now, at the same version. They are the same app built two ways, and what separates them is sandboxing and how they update, not what is in them: the disk image updates itself through Sparkle, and the App Store edition updates through the store and runs in Apple’s sandbox.
Everything you would use it for works the same in both. Capture, search, pinning, the ⌘⇧V shortcut and sync need no special permission either way.
Your history does not move between them
A sandboxed app reads a different location on disk, so installing the store edition over the downloaded one starts you with an empty history. We cannot migrate it for you — the sandbox is what stops the new copy reading the old copy’s files, and that is the point of it. Items already synced come back when you sign in; anything that never left the Mac does not. Pick an edition and stay on it.
On the name. The App Store listing reads “UniClip - Clipboard Sync” because another developer holds the bare name in the US store. The app itself, its home-screen name and this site are all just UniClip.
The Mac build is signed with a Developer ID issued to UniAuth Inc. (team A5FW5P2536) and notarised by Apple. You do not have to take our word for it — check the copy you downloaded:
codesign --verify --strict \
--verbose=2 /Applications/UniClip.app
codesign -dv --verbose=4 /Applications/UniClip.app 2>&1 \
| grep -E '^(Identifier|TeamIdentifier)='
spctl --assess --type execute \
-vv /Applications/UniClip.appThe first says the copy is intact. The second is the one that matters: it must print Identifier=id.uniauth.clip.mac and TeamIdentifier=A5FW5P2536. The third should report accepted.
Check the team, not just the checkmark — a validly signed, notarised build from someone else passes the other two as well. The identity is what ties this copy to us.
The Mac app reads a release feed at a fixed address over HTTPS, and installs what it finds only if that download is signed by the same Apple Developer ID as the copy already on your Mac. A web server handing out a tampered build cannot produce that signature.
Release feed
https://clip.uniauth.id/dl/appcast.xmlRunning the 1.0 disk image? It will not update itself
The 1.0 disk image shipped with automatic update checks switched off. It never looks for a new version and never asks, so it cannot reach 1.4 on its own. This does not affect the App Store edition, which updates through the store. Either download above, or use Check for Updates in the menu bar — both work, and every build since 1.1 asks you once whether it may check on its own from then on. Nothing is wrong with 1.0 otherwise: it captures, syncs and encrypts exactly as it should. It simply cannot hear about its own successor. What changed since 1.0.
The App Store handles updates on iPhone and iPad.