What Local-First Software Means for Clipboard Apps

"Local-first" is a software philosophy that puts the user's machine — not a vendor's cloud — at the centre of the data model. The user's data lives on the user's device by default; any cloud synchronisation is opt-in, explicit, and visible. For a clipboard app, where the data includes passwords, customer details, code snippets, and trade secrets, the local-first default is not a stylistic preference. It is the only safe default. This guide covers what local-first means in practice for a clipboard app, how it differs from cloud-first, why a clipboard should default to local, and what Edge-Drop does and does not ship. For neighbouring topics see managers that stay local on purpose and Apache-2.0 clipboard tools you can actually audit.

What local-first means

The local-first movement, articulated clearly by Ink & Switch in 2019, proposes seven principles for software that respects user ownership of data. The relevant ones for a clipboard app:

• Data is on the user's device by default. The user's machine is the source of truth; the cloud, if any, is a replica.
• The app works offline. No network connection is required for the core functionality.
• The user owns the data. The data is in a format the user can read, back up, or export; it is not locked in a proprietary cloud.
• Network use is explicit and visible. When the app sends data to the cloud, the user knows — it is not silent, not "telemetry," not "improving the product."

For a clipboard app, this translates to:

• History is stored on the local disk, encrypted with keys that do not leave the device.
• The shelf works with no internet connection.
• The user can back up, inspect, or delete the history without involving a vendor.
• The app does not send clipboard content to any server unless the user explicitly turns on a sync feature.

Microsoft's Win+V is local-first by default: history is on the device, sync is opt-in. Edge-Drop is local-first by design: there is no sync feature to opt into at all.

How local-first differs from cloud-first

A cloud-first clipboard app sends every copy to the vendor's cloud, processes it there, and replicates it to the user's other devices. The user's clipboard content lives on the vendor's servers, subject to the vendor's data-retention policy, breach risk, and legal-jurisdiction rules. The user pays for the convenience of cross-device sync with the privacy cost of cloud storage.

A local-first clipboard app keeps every copy on the device. Cross-device sync, if available, is a separate product or feature; the local history is complete and usable without it.

Why a clipboard should default to local

The clipboard is a particularly sensitive data surface:

• Passwords and 2FA codes — copied by password managers and 2FA apps. Even when marked as concealed (see what Edge-Drop does with password manager copies), mistakes happen.
• Customer data — support agents copy customer details, account numbers, and case notes into chat and tickets.
• Code and configuration — developers copy code snippets, configuration files, environment variables, and (accidentally) secrets.
• Trade secrets and internal URLs — employees copy internal wiki links, internal API endpoints, and proprietary documentation.
• Personal data — banking details, account numbers, government IDs, private messages.

For all of these, the default should be: do not send to the cloud. If the user wants cross-device sync, they should turn it on deliberately, with full knowledge of what is being sent where. Silent cloud sync of the clipboard is a security incident waiting to happen.

This is why Windows clipboard history (Win+V) ships with sync off by default and limits sync to text only. See does Windows clipboard sync upload what you copy and how to disable Windows clipboard cloud sync for the OS-side controls.

What local-first looks like in practice

A local-first clipboard app:

• Stores history on the local disk, encrypted with keys derived from the user's OS credentials (DPAPI on Windows). See where Edge-Drop stores data on disk.
• Works offline. Capturing, replaying, searching, filtering, pinning — all work with no network connection.
• Does not phone home with clipboard content. Telemetry, if any, is about app health (crashes, version), not about what was copied. See how to audit whether a clipboard app talks to the network.
• Makes network use visible. If the app fetches a URL preview (see how to open links from Edge-Drop in your browser), the user can see the request happen and disable it if desired.
• Lets the user export and delete. History can be cleared, items can be deleted, the entire store can be wiped. There is no vendor lock-in.
• Does not require an account. The app launches and works without login. There is no "Edge-Drop account" because there is no Edge-Drop cloud.

What local-first does not mean

Local-first does not mean:

• No network at all. A local-first app can use the network for non-data purposes: checking for updates, fetching UI assets, displaying a changelog. The key is that the user's data does not leave the device without explicit consent.
• No cloud features ever. A local-first app can offer cloud sync as an opt-in feature; it just cannot make sync the default or the only path. Edge-Drop does not offer sync at all, which is a stronger stance.
• No telemetry. A local-first app can collect telemetry about app health (crashes, errors) as long as the telemetry does not include user data and the user can opt out. Edge-Drop currently collects no telemetry.
• Open source. Local-first and open source are separate properties. A local-first app can be closed source; an open-source app can be cloud-first. They are correlated in practice but not the same. See open source vs closed clipboard apps.
• Slow or limited. A local-first app can be fast and feature-rich; the local-first constraint is about data location, not capability.

How local-first interacts with cross-device workflows

The main objection to local-first is the cross-device workflow: a user copies a URL on their laptop and wants it on their desktop. With cloud sync, this is automatic. With local-first, it requires either:

• Manual copy — re-copy the URL on the desktop (most common, mildly inconvenient).
• A separate sync tool — the user sets up Syncthing, Resilio Sync, or a similar file-sync tool to mirror the clipboard store between devices. This is opt-in, visible, and the user controls the encryption.
• A different product — a cloud-sync clipboard like Windows Win+V sync, Pushbullet, or similar. The user uses the local-first app for day-to-day and the cloud-sync app for cross-device.

None of these is as seamless as silent cloud sync, but all of them are more private. The local-first philosophy is willing to accept the friction in exchange for the privacy.

For the broader topic, see remote work: clipboard across home and office PCs and cloud clipboard apps worth using in 2026.

What Edge-Drop does and does not ship

Edge-Drop is local-first by design. Specifically:

• History is stored locally, encrypted with DPAPI. See where Edge-Drop stores data on disk.
• The app works offline. The only network use is the link-preview fetch (which can be disabled) and the auto-update check on GitHub builds (which fetches metadata, not clipboard content).
• There is no Edge-Drop cloud account. There is no Edge-Drop cloud sync. There is no plan for either. See why some clipboard apps will never sync.
• The source is open under Apache-2.0, so users can verify these claims. See Apache-2.0 clipboard tools you can actually audit.
• There is no telemetry. See telemetry-free desktop utilities: how to check.

What Edge-Drop does not ship:

• Cross-device sync. The user who wants this needs a different tool.
• Cloud backup of history. The user who wants this can manually copy the %APPDATA%\Edge-Drop folder to their backup location.
• An account system. There is no login.
• A web UI. There is no web app.

This is a deliberate product scope, not a missing feature. For the project's scope boundaries, see what Edge-Drop is not trying to become.

How to verify a clipboard app is local-first

Users who want to verify that a clipboard app is genuinely local-first can:

• Read the privacy policy. A cloud-first app will mention data processing, retention, and jurisdiction; a local-first app will say data is stored on the device.
• Inspect network traffic. Use Wireshark or a similar tool to capture the app's network traffic. A local-first app should make minimal network requests; any request that carries clipboard content is a red flag.
• Read the source (if open source). The clipboard poller, the storage layer, and the network layer should be inspectable. See reading an Electron app's IPC surface as a user.
• Check the permissions. A local-first app should request minimal network access. See how to audit whether a clipboard app talks to the network.
• Test offline. Disable network and verify the app still works.

For the broader topic, see privacy settings checklist for any clipboard manager.

Summary

Local-first means data lives on the user's device by default; cloud sync is opt-in and visible. For a clipboard app — where data includes passwords, customer details, code, and trade secrets — local-first is the only safe default. Edge-Drop is local-first by design: history is local and encrypted, the app works offline, there is no cloud account or sync, and the source is open under Apache-2.0. The trade-off is the loss of seamless cross-device sync, which local-first users accept in exchange for privacy. Users who want to verify a clipboard app is local-first can read the privacy policy, inspect network traffic, read the source, check permissions, and test offline.

Related reading

• How to Enable Clipboard History in Windows 11
• What Win+V Actually Opens on Windows 11
• How to Use Windows Clipboard History Day to Day
• How to Pin Items in Windows Clipboard History

Sources

• Ink & Switch — Local-first software — the canonical essay that articulated the local-first principles
• Microsoft Learn — Data Protection API (DPAPI) — documents the per-user encryption Edge-Drop uses for local history
• Microsoft Support — Windows clipboard history and sync — confirms that Win+V is local-first by default and that cloud sync is opt-in
• Electronic Frontier Foundation — Panopticlick — reference for how network traffic can fingerprint users; relevant to evaluating a clipboard app's network use
• OWASP — Privacy engineering cheat sheet — reference for the privacy-by-default principles that underpin local-first 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