# Edge-Drop: a hover-activated clipboard shelf for Windows 10 and 11

> Edge-Drop is an Electron and React desktop app that hides on a screen edge and opens when the cursor approaches, so you can drag text, links, images and files straight into another application. It is Windows-only, and the README does not document rollback or a portable build.

**Deepender25/Edge-Drop** — Edge-Drop is like a Dynamic Island for your desktop clipboard. It hides on the edge of your screen and opens when you hover near it, letting you easily store and drag text, links, images, and files directly into any application.

- Repository: https://github.com/Deepender25/Edge-Drop
- Website: https://www.edgedrop.app/
- Stars: 615 · Forks: 39
- Language: TypeScript
- License: Apache-2.0
- Published: 2026-09-17 · Updated: 2026-09-17 · Language: en
- Canonical page: https://hysenlabs.com/projects/deepender25-edge-drop

## The friction Edge-Drop is aimed at

The README opens with a complaint rather than a feature list: clipboard managers force you to copy something, switch apps, paste, and then hunt through Win+V history with arrow keys or a tray menu. It calls that sequence multi-step, modal and slow. Whether or not you agree with the phrasing, the target user is named clearly: developers and designers who juggle screenshots, code snippets, file paths, design assets and reference links across many windows at once.

The distinction that matters is drag-out versus paste-in. A conventional clipboard history is a list you open, scroll and select from, and the result lands wherever your cursor already is. Edge-Drop inverts that. The item sits on a shelf that is already visible at the edge of the screen, and you pull it into the target application with the mouse. The README's claim is that this removes shortcuts, window switching and modal dialogs from the loop. For someone moving a screenshot into a chat window or a file path into a terminal, the gesture is shorter. For someone who mostly pastes text into the same editor all day, the older keyboard flow is probably still faster, and the README does not argue otherwise.

## How the edge shelf actually behaves

The mechanism described in the README has three parts. First, the app anchors to the screen edge of a monitor as a transparent, always-on-top, click-through surface. Click-through is the detail that makes it usable: while the shelf is closed, mouse events pass to whatever is underneath, so the overlay does not steal clicks from your normal work. Second, when the cursor approaches the edge, the shelf springs open. The repository lists Framer Motion v11 among its dependencies, which is consistent with the spring-physics animation the README advertises. Third, items leave the shelf by drag and drop into another desktop application, and the README also describes merging several clipboard items into one stack, ungrouping a stack back into individual cards, and a preview flyout for inspecting high-resolution images, formatted text and code with zoom.

The stack model is the part worth understanding before you commit. A file stack is treated as one card until you ungroup it, and multiple items can be merged into a single stack. That is a different mental model from a flat history list, and it is the reason the v0.3.0 release notes mention rich file stacks alongside refined drag and drop. The build itself is Electron v34, React v19 and TypeScript 5.7, with electron-vite as the build tool and Vitest as the test runner. The repository states 364 passing tests in a README badge; treat that as a claim from the project, not as an independent measurement.

## Installing Edge-Drop on Windows 10 or 11

The README gives two distribution paths: the Microsoft Store listing and a signed-style .exe installer linked from the latest GitHub release. Pick one. The Store route handles updates through Microsoft's channel; the installer route means you track releases yourself. There is no documented macOS or Linux build, and the platform badge in the README reads Windows 10 / 11 only.

If you want to build from source instead, the package manifest defines the usual electron-vite workflow. Install dependencies, then start the development build:

```bash
npm install
npm run dev
```

The dev script runs electron-vite dev, which starts the main process and the renderer with hot reload. After the window appears, the first real use is the edge trigger: move the cursor toward the screen edge the app has claimed and the shelf should spring open. If nothing happens, the likeliest cause is a conflict with the taskbar or another always-on-top overlay, not a build failure.

For a distributable Windows build, the manifest exposes separate targets for the GitHub installer and the Store package:

```bash
npm run build:win
npm run build:store
```

build:win maps to build:github, which runs electron-vite build and then electron-builder with the nsis target and buildTarget=github. build:store uses the appx target with buildTarget=store. Output goes to the dist directory configured under build.directories. Before shipping anything you built yourself, run npm run typecheck and npm test, which the manifest defines as tsc against the node and web tsconfigs and vitest run respectively.

## Where Edge-Drop gets in the way

The click-through overlay is the design decision that carries the most risk. An always-on-top surface parked on a screen edge has to coexist with the taskbar, with other always-on-top windows, and with full-screen applications. The v0.3.0 release notes mention smarter multi-monitor triggering, which suggests the trigger logic across displays needed work and was revised. If you run a multi-monitor setup, that is the first thing to exercise on your own hardware rather than assume.

The second limitation is platform. Windows 10 and 11 only. If your team is mixed, half of it cannot use this at all, and the README offers no roadmap for other platforms.

The third is that the README does not document rollback. There is no stated procedure for reverting to a previous version after an upgrade breaks your setup, and there is no mention of a portable build. If you install through the Microsoft Store, you inherit whatever update Microsoft delivers on its schedule. If you install the .exe, you keep the installer for the version you chose, which is the only rollback mechanism the README implies.

Finally, the privacy question. The repository contains a PRIVACY.md file, but its contents are not reproduced here, so the handling of clipboard contents is something to read in that file directly before you run this on a work machine with sensitive material.

## Edge-Drop compared with Win+V and dedicated clipboard managers

The obvious alternative on Windows is the built-in Win+V clipboard history. The difference is not feature count, it is the interaction model. Win+V is a keyboard-triggered list that appears near the cursor and pastes into the focused field; it handles text and images that pass through the system clipboard. Edge-Drop is a persistent shelf at the screen edge that you drag out of, and the README extends it to file stacks that can be merged and ungrouped, which the system clipboard history does not model.

A second class of alternative is a dedicated clipboard manager with search, pinning and sync. Those tools generally assume you will paste rather than drag, and they often run on more than one operating system. If cross-platform consistency matters more than the drag gesture, that class of tool is the better fit, and Edge-Drop is the wrong choice. The honest framing is that Edge-Drop is not competing on history depth or search. It competes on how few actions sit between an item and the application that needs it, and it only wins that comparison for people who work with the mouse and move mixed content types.

## Maintenance, licence and upgrade cost

The last push to the default branch was on 2026-09-15, and the repository is not archived. Releases have been frequent through the 0.3.x line: v0.2.9 on 2026-08-21, v0.3.0 on 2026-08-27 and v0.3.1 on 2026-09-08. That cadence means upgrade cost is a real line item rather than a theoretical one, because each release has changed user-visible behaviour: v0.2.9 added a custom hotkey recorder and filter-scoped history clearing, v0.3.0 reworked multi-monitor triggering and file stacks, v0.3.1 added an emoji picker and UI polish. If you build from source you are tracking a moving target and should expect to re-run the typecheck and test scripts after pulling.

The project is licensed Apache-2.0, which permits commercial and private use and requires that you preserve the licence and notice files when you redistribute. The package manifest marks the package as private, which concerns publishing to a registry rather than your rights under the licence. Nothing here is legal advice; if you plan to redistribute a modified build inside a company, read the LICENSE file and PRIVACY.md in the repository yourself.

## Conclusion

Adopt Edge-Drop if your workday is mostly Windows and you move screenshots, file paths and code snippets between many windows, because the drag-out model is the part that differs from a keyboard-history clipboard manager. Do not adopt it if you need macOS or Linux, or if you want a clipboard history you can search and paste from rather than drag from. Before installing, verify three things on your own machine: that the trigger edge does not collide with the docked taskbar, that the multi-monitor trigger behaves on your display layout, and that the release you download is the one whose notes you have read, since the README does not document a rollback path to an earlier version.

## FAQ

### What is Edge-Drop?

Edge-Drop is a desktop clipboard shelf that anchors to the edge of your screen as a transparent, always-on-top, click-through surface. It opens when the cursor approaches and lets you drag text, links, images and files into other applications.

### How do I use Edge-Drop?

Move the cursor toward the screen edge the app has claimed and the shelf springs open. From there you drag an item into the target application, or merge several items into a stack and ungroup it later.

### How do I access Edge-Drop?

The README lists two access routes: the Microsoft Store listing and the .exe installer linked from the latest GitHub release. The README does not describe a separate web interface.

## Sources

- [Deepender25/Edge-Drop on GitHub](https://github.com/Deepender25/Edge-Drop)
- [License: Apache-2.0](https://github.com/Deepender25/Edge-Drop/blob/main/LICENSE)
- [Project website](https://www.edgedrop.app/)
- [README](https://github.com/Deepender25/Edge-Drop/blob/main/README.md)
- [Releases](https://github.com/Deepender25/Edge-Drop/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/deepender25-edge-drop