Edge-Drop: GitHub Installer or Microsoft Store Build?

Edge-Drop ships through two Windows distribution channels: a GitHub NSIS .exe installer and a Microsoft Store MSIX package. Both install the same product, but they differ in how they update, how sandboxed they are, and what they can do at runtime. The "edge-drop github vs microsoft store" question is not about which build is faster or prettier; it is about which trade-off fits the machine it is going on.

For the related decisions, see open source vs closed clipboard apps, should you pay for a clipboard manager in 2026, and best free clipboard manager for Windows.

What the two builds actually are

Both builds compile from the same source repository. The differences are in packaging and lifecycle, not in features. For the broader open-source discussion of how this code is audited, see Apache-2.0 clipboard tools you can actually audit.

Auto-update behaviour

The biggest practical difference is how each build receives updates.

GitHub installer. On launch, Edge-Drop checks the GitHub Releases API for a newer version than the one installed. If a newer version exists, the user is prompted to download and install. Updates are not silent; they require a click. Beta and pre-release versions are visible if the user opts in.

Microsoft Store package. Updates are handled by the Store. The Store checks for updates on its own schedule (typically every 24 hours, more often if the user opens the Store). The user can also trigger a manual check via the Microsoft Store library. Updates are silent and automatic.

For the deeper mechanics of how the GitHub build checks and installs updates, see how Edge-Drop updates on GitHub builds.

Sandbox and capability differences

This is where the choice becomes meaningful.

The GitHub installer runs as a normal desktop process. It has the same file system, registry, and network access as any other desktop app. It can write to %APPDATA%, read from anywhere the user can read, and open any file the user can open. This is necessary for drag-out — Edge-Drop uses real OS file handles (startDrag / OLE) to drag items into Photoshop, Word, Slack, and Explorer. A sandboxed process cannot do this with the same fidelity.

The Microsoft Store package runs in an AppContainer. The AppContainer restricts what the process can do: file system access is limited to the package's own data folders, registry access is virtualised, and network access is gated by capabilities declared in the manifest. This is a security improvement — a compromised or buggy Store build cannot do as much damage as a compromised or buggy Win32 build — but it changes what the app can do at runtime.

For Edge-Drop specifically, the Store package's sandbox means:

• Drag-out into other desktop apps works, but with caveats. Some targets accept files from a packaged app; others reject them because the source is running in a different integrity context. Photoshop and Office generally accept the drop; some legacy apps do not.
• Reading files from arbitrary folders (for the "drop a file into the shelf" feature) requires the user to pick the file through a brokered file picker. The app cannot silently enumerate C:\Users\name\Documents.
• Auto-start at login works through the Store's StartupTask API, not through registry Run keys. The user must approve the startup task in Settings → Apps → Startup. See how to launch Edge-Drop at login.

The trade-off: the Store package is safer to install and easier to manage; the GitHub installer is more capable and more current.

A decision tree

                ┌─ Do you need drag-out into legacy apps that reject MSIX sources?
                │   └─ Yes → GitHub installer
                │   └─ No  → continue
                ├─ Are you on a managed enterprise machine where only Store apps are allowed?
                │   └─ Yes → Microsoft Store
                │   └─ No  → continue
                ├─ Do you want beta releases as soon as they ship?
                │   └─ Yes → GitHub installer
                │   └─ No  → continue
                ├─ Is "no auto-update prompt, ever" the priority?
                │   └─ Yes → Microsoft Store
                │   └─ No  → continue
                └─ Default → Microsoft Store (cleanest install, automatic updates)

The default recommendation, for most users, is the Microsoft Store package. It is the cleanest install path, it auto-updates without intervention, and the sandbox limits the blast radius of any future bug. The GitHub installer is the right pick for users who need a feature the sandbox blocks, or who want to track beta releases.

When NOT to use Edge-Drop

Edge-Drop is one option among many. It is not the right pick for every user, and the distribution-channel choice is moot if the product itself is the wrong fit. The same caveats apply here as elsewhere in this cluster:

• If RAM is the deciding factor. Edge-Drop is an Electron app and uses roughly 130–160 MB of RAM at idle. Ditto, ArsClip, and the built-in Win+V are much lighter. On a low-RAM machine, Edge-Drop is the wrong choice regardless of which build is installed. See best clipboard manager for low-RAM PCs.
• If scripting is the deciding factor. CopyQ has a JavaScript-like scripting interface and a command-line client. Edge-Drop does not. Users who want to auto-redact tokens on copy, auto-route clips by source app, or run scripts on every capture should use CopyQ. See edge-drop vs CopyQ: drag shelf vs scriptable clipboard.
• If cloud sync is the deciding factor. Edge-Drop has no cloud sync. Users who need clipboard history on multiple devices should use Ditto with its sync feature, or Win+V with sync enabled (text only, same Microsoft account). See edge-drop vs Windows clipboard history (Win+V).
• If screenshot capture is the deciding factor. Edge-Drop is not a capture tool. ShareX is. The two pair well; see edge-drop vs ShareX: not competitors, how they pair.
• If text expansion is the deciding factor. Edge-Drop is not a text expander. Espanso and PhraseExpress are. See edge-drop vs Espanso: mouse staging vs typed shortcuts.

For the full picture, see cases where Edge-Drop is the wrong tool.

Other things that affect the choice

A few non-build factors that come up in this decision:

• Side-loading restrictions. Some enterprise machines block .exe installers that are not signed by a trusted publisher. The GitHub installer is developer-signed; if the enterprise only trusts Microsoft-signed binaries, the Store package is the only option. See questions to ask before installing a clipboard app.
• Group Policy. The Store can be disabled by Group Policy (Remove-AppxPackage on a schedule, or the "Disable Microsoft Store" policy). On those machines, the GitHub installer is the only option.
• Per-user vs per-machine. The GitHub installer can install per-machine (all users share one install) or per-user. The Store package is always per-user. For shared workstations, this matters.
• Uninstall cleanliness. Both builds uninstall cleanly. The GitHub installer removes its files and registry entries; the Store package removes its AppContainer and virtualised storage. Neither leaves clipboard history behind, because history is stored in the app's own data folder and is removed on uninstall. For the uninstall mechanics, see how to uninstall Edge-Drop cleanly and where Edge-Drop stores data on disk.

For the install procedure on either build, see how to install Edge-Drop on Windows 10 and 11 and your first ten minutes with Edge-Drop.

A short verdict

For most users: Microsoft Store package. The sandbox is a real safety improvement, auto-update is silent, and the install is clean. The trade-off (slightly less drag-out fidelity into legacy apps, slightly delayed updates) is acceptable for everyday clipboard use.

For power users, developers, and anyone who needs the latest release or a feature the sandbox blocks: GitHub installer. The auto-update model is faster, the process is unsandboxed, and the build tracks the project's release cadence directly.

Both builds are the same product. The choice is about packaging, not about features. Pick the one whose trade-offs match the machine it is going on.

Related reading

• Should You Pay for a Clipboard Manager in 2026?
• Scorecard: Pick a Windows Clipboard Tool in 10 Minutes
• Best Free Clipboard Manager for Windows
• How to Install Edge-Drop on Windows 10 and 11

Sources

• Microsoft Learn — MSIX app packaging — official documentation for the MSIX package format and the AppContainer sandbox that the Microsoft Store build of Edge-Drop runs in
• Microsoft Learn — AppContainer isolation — explains the file system, registry, and capability restrictions that the Store package's sandbox imposes
• Microsoft Learn — StartupTask API — the official mechanism for declaring a startup task in an MSIX package, used by the Store build for auto-start at login
• GitHub — NSIS documentation — official documentation for the Nullsoft Scriptable Install System, used to build the GitHub .exe installer
• Edge-Drop — GitHub README — official repository for Edge-Drop, including release notes that distinguish GitHub and Store distribution

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