Why Some Clipboard Apps Will Never Sync

"Sync" is one of the most-requested features for any clipboard app. Users want the URL they copied on their laptop to be available on their desktop, the screenshot from their tablet to land on their work machine, the snippet from their phone to appear in their editor. It is a reasonable request, and many clipboard apps ship sync to satisfy it. Some, however, deliberately do not. Edge-Drop is one of them. This guide covers why sync is a different product with a different threat model, what the threats are, what users gain from a no-sync stance, and how to get cross-device clipboard when you need it. For the broader local-first context see what local-first software means for clipboard apps and Apache-2.0 clipboard tools you can actually audit.

Sync is a different product

A local clipboard app and a synced clipboard app are different products, even if they share a UI. The differences are in the data path, the threat model, the infrastructure, and the legal exposure.

A vendor that ships sync is signing up for a different business. They need to operate cloud infrastructure, manage user accounts, handle encryption key custody (or outsource it to a third party), and accept the legal exposure of storing user data. The cost is real; the subscription revenue is what funds it.

A vendor that does not ship sync is making a deliberate scope choice. The local product is complete on its own; sync is a separate product that someone else can build.

The threats sync introduces

Syncing clipboard content introduces threats that do not exist in a local-only product:

• Cloud breach — the vendor's cloud is a high-value target. A breach exposes every user's clipboard history, including passwords, 2FA codes, and private messages. Even with encryption-at-rest, if the vendor holds the keys (which most do, for cross-device sync to work), the breach exposes the keys too.
• Vendor insider — vendor employees with database access can read user data. Background checks and access controls reduce but do not eliminate this risk.
• Legal subpoena — a government can subpoena the vendor for a user's clipboard history. The vendor may or may not be able to disclose the subpoena; the user may or may not have recourse.
• Account lockout — if the vendor's account system is the gate to the user's clipboard history, an account lockout (billing failure, TOS violation, vendor error) cuts off access to the user's own data.
• Sync lag — copies appear on other devices with a delay. The user may believe a copy has synced when it has not, leading to incomplete paste on the other device.
• Sync conflicts — copies made on two devices at the same time may conflict; the resolution rules are vendor-defined and may surprise the user.
• Cloud retention — the vendor's data-retention policy applies. Deleted items may persist in cloud backups for weeks or months.

These threats are not hypothetical. Cloud clipboard services have been breached; account systems have been abused; legal processes have been served. The local-first movement exists in part because of these incidents.

Why "ship it badly" is not the answer

A common vendor response is to ship sync with weak encryption — encrypt in transit (TLS) but not at rest, or encrypt at rest with vendor-held keys. This satisfies the marketing claim of "encryption" without providing the privacy guarantee the user expects. It is worse than not shipping sync at all, because it gives users a false sense of security.

The honest alternatives are:

• End-to-end encryption (E2EE) — the user's device encrypts with a key the vendor cannot see. The vendor stores ciphertext only. This is the gold standard; it is also complex to implement, especially key management across devices. See cloud sync roadmaps: what E2E would have to mean.
• No sync — the local product is complete; cross-device workflows use a different tool. This is Edge-Drop's stance.
• User-managed sync — the user sets up their own sync (Syncthing, Resilio, etc.) over the local store. The vendor does not operate cloud infrastructure. This is rare but exists in some open-source tools.

A vendor that cannot ship E2EE should not ship sync at all. Sync with vendor-held keys is the worst of both worlds: it adds the threats of cloud storage without the privacy guarantee of local-first.

What users gain from no sync

The no-sync stance is not a deficit; it is a benefit. Users gain:

• No account — no login, no password, no account-recovery flow, no account-lockout risk.
• No cloud bill — the vendor's cost model is one-time (or donation-funded); there is no recurring subscription to maintain access.
• No jurisdictional exposure — the user's data never leaves their device, so the user's local jurisdiction is the only one that applies.
• No breach surface — there is no cloud to breach.
• No retention policy — the user controls retention via local settings (auto-delete, clear-on-restart). See how to set auto-delete timers in Edge-Drop.
• No sync lag — local operations are instant.
• No sync conflicts — there is only one copy of the data.
• Offline operation — the app works with no network connection.

For users whose clipboard content is genuinely sensitive — developers handling production credentials, support agents handling customer data, lawyers handling privileged material, journalists handling sources — these gains outweigh the loss of cross-device sync.

How to get cross-device clipboard when you need it

For users who do need cross-device clipboard, the options are:

• Windows clipboard sync (Win+V sync) — Microsoft's built-in sync across Windows devices signed into the same Microsoft account. Text only, opt-in. See does Windows clipboard sync upload what you copy.
• Phone Link — Microsoft's Phone Link app syncs clipboard between Android phones and Windows PCs. See phone link clipboard access: privacy checklist.
• Cloud clipboard apps — third-party apps like Pushbullet, Join, or similar. These ship their own sync infrastructure and accept the threat model above.
• User-managed file sync — for power users, sync the %APPDATA%\Edge-Drop folder across machines with Syncthing or Resilio. This gives local-first behaviour with cross-device availability. The encryption is user-controlled.
• Manual copy — re-copy the item on the other device. Often the simplest answer.

For most users, the right combination is: a local-first clipboard app (Edge-Drop, Ditto, Win+V) for day-to-day, plus Win+V sync or Phone Link for the occasional cross-device need. The local-first app handles 95% of the workflow; the sync feature handles the 5% where it is genuinely useful.

For the broader landscape, see cloud clipboard apps worth using in 2026 and 1clipboard and cloud clip apps vs local managers.

Why Edge-Drop does not ship sync

Edge-Drop does not ship sync for the reasons above:

• The threat model of sync is different from the threat model of a local clipboard.
• Shipping sync with vendor-held keys would be dishonest.
• Shipping E2EE sync is a substantial engineering project that is out of scope for a single-maintainer project.
• The existing alternatives (Win+V sync, Phone Link, user-managed file sync) cover the cross-device use case for users who need it.
• The local-first stance is a feature, not a missing feature. See what Edge-Drop is not trying to become.

This is a deliberate product decision, not a "we'll add it later" deferral. The maintainer has been clear in the project's communication that sync is not on the roadmap. For users who need sync, the recommendation is to pair Edge-Drop with a sync tool rather than wait for Edge-Drop to ship sync.

How to evaluate a synced clipboard app

For users evaluating a synced clipboard app, the questions to ask:

• Is sync end-to-end encrypted? If not, the vendor can read your clipboard. Treat the product as cloud storage, not as a private clipboard.
• Who holds the encryption keys? If the vendor holds them, the vendor can read your data. If the user holds them, the user is responsible for key management (and for losing access if they lose the key).
• What is the data-retention policy? How long does deleted data persist in cloud backups?
• What is the jurisdiction? Where are the servers? Which legal regimes apply?
• What is the account-recovery model? If you lose access to your account, can the vendor reset your encryption key? (If yes, the vendor can read your data.)
• What is the breach-notification policy? How will you be informed if the vendor is breached?

A synced clipboard app that cannot answer these questions clearly is not a product to trust with sensitive data. See privacy settings checklist for any clipboard manager for the broader framework.

What Edge-Drop does not claim

• The no-sync stance is not a permanent commitment to never ship sync. The maintainer could in theory change course. The Apache-2.0 license ensures the existing source remains free; a future version could theoretically add sync. There is no current plan to do so.
• The no-sync stance does not mean Edge-Drop is "more secure" than a synced app. A synced app with strong E2EE can be as secure as a local app for the local data; the difference is the cloud copy.
• The no-sync stance does not mean Edge-Drop is "better" than synced alternatives. It is a different product for users with different priorities. See edge-drop vs Maccy: Windows users cannot copy minimalism blindly and other comparisons.
• The no-sync stance does not preclude the user from setting up their own sync. The user-managed file-sync approach is a legitimate workflow.

Summary

Sync is a different product with a different threat model. A synced clipboard app introduces cloud breach, vendor insider, legal subpoena, account lockout, sync lag, sync conflicts, and cloud retention as threats that do not exist in a local-only app. The honest alternatives are end-to-end encryption (hard, but the gold standard) or no sync (simple, and a feature in its own right). Edge-Drop does not ship sync because the threat model is different, E2EE is out of scope, and the alternatives cover the cross-device use case. Users who need cross-device clipboard should pair Edge-Drop with Win+V sync, Phone Link, or a user-managed file-sync tool. The no-sync stance is a deliberate product decision, not a missing feature.

Related reading

• Apache-2.0 Clipboard Tools You Can Actually Audit
• Reading an Electron App's IPC Surface as a User
• What Local-First Software Means for Clipboard Apps
• How to Enable Clipboard History in Windows 11

Sources

• Ink & Switch — Local-first software — the essay that articulated the local-first principles underlying the no-sync stance
• Microsoft Learn — Windows clipboard sync — official documentation for the OS-level sync that is the alternative to vendor sync
• Electronic Frontier Foundation — Encryption primer — reference for the difference between transit encryption and end-to-end encryption
• OWASP — Cryptographic storage cheat sheet — reference for what "end-to-end encryption" must mean to be meaningful
• National Institute of Standards and Technology — Cryptographic standards — reference for the cryptographic primitives underlying E2EE sync design

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support