How Is Edge-Drop Different From Ditto (Without Copying It)?

Ditto is the default Windows clipboard manager. It has been maintained for roughly 20 years, it is GPL-3.0, it uses tens of megabytes of RAM, and it holds thousands of items in a SQLite database. Beating Ditto at what Ditto does is not a realistic strategy for a new tool. Edge-Drop's strategy is to compete on different axes: drag-out into desktop apps, and spatial access via a screen edge. This page is transparent about where Edge-Drop wins, where it loses, and where the two are simply different tools for different workflows. For related reading, see what Edge-Drop is not trying to become, how to cite open-source tools in a roundup fairly, what local-first software means for clipboard apps, and why some clipboard apps will never sync.

What Ditto is, briefly

Ditto is a Windows clipboard manager written in C++ against the Win32 API and MFC. Its data store is a SQLite file in %APPDATA%\Ditto\. Its UI is a list with search, pin, and a context menu. It has a scripting interface via DittoAddin, but it is C++ and minimally documented. It can hold thousands of items, it uses tens of megabytes of RAM, and it has been the default recommendation for serious Windows clipboard users for most of its life.

Ditto's strengths:

• RAM. Tens of megabytes at idle. No other mainstream Windows clipboard manager is lighter.
• History. Thousands of items, with search, in a SQLite database that survives restarts and is easy to back up.
• Maturity. 20 years of development, a stable API, a known set of edge cases and workarounds.
• Network sync (legacy). Ditto had a sync feature; it is mostly deprecated in favour of file-based export.

Ditto's weaknesses:

• UI. The list is functional but visually dated. There is no card view, no thumbnail strip, no spatial layout.
• Drag-out. Ditto can drag items out, but the interaction is list-first, not shelf-first. Dragging an image from Ditto into Photoshop works, but it is not the primary interaction.
• Cross-platform. Windows-only. No macOS, no Linux.
• Scripting surface. Exists, but is C++ and minimally documented. Most users never touch it.

Where Edge-Drop loses

The honest list of where Ditto wins:

RAM

Ditto uses tens of megabytes. Edge-Drop uses 130–160 MB, because it is Electron. This is a real objection for users on low-RAM hardware, and the honest response is to point them to Ditto or Win+V. Edge-Drop does not compete on RAM and should not be sold as if it does. For more, see how much RAM a clipboard manager should use and best clipboard manager for low-RAM PCs.

History depth

Ditto holds thousands of items. Edge-Drop is designed for short-range staging, not long-term archive. Users who want to search a year of clipboard history should use Ditto. Edge-Drop's history is real — items are stored on disk, encrypted with DPAPI, and persist across restarts if pinned — but the design intent is "what did I copy in the last hour," not "what did I copy last quarter."

Scripting

Ditto has a scripting interface. It is not as polished as CopyQ's, but it exists. Edge-Drop does not have one, and does not plan one. Users who want scripted transformations should use CopyQ or Ditto, not Edge-Drop. For more, see the plugin SDK question: when custom formats matter.

Maturity

Ditto has 20 years of development. Edge-Drop is at version 0.2.7 as of mid-2026. For users who prioritise stability and a known set of edge cases, Ditto is the safer bet. For more on the trade, see bus factor: what if a solo app goes quiet.

Where Edge-Drop wins

The honest list of where Edge-Drop wins:

Drag-out into desktop apps

Edge-Drop's drag-out uses Electron's webContents.startDrag, which initiates a real Win32 OLE drag with a file handle. The receiving app — Photoshop, Word, Slack, Explorer — sees a real file drop, not a webpage drag. Ditto can drag items out, but the interaction is list-first and the file-handle path is less central.

For users whose workflow is "stage a set of assets, drag them one by one into a desktop app," Edge-Drop is the better tool. For users whose workflow is "find an item I copied last week and paste it into a document," Ditto is the better tool.

Spatial access via a screen edge

Edge-Drop lives at a screen edge, opens on hover, and closes when the cursor leaves. The interaction is pointer-first, not click-first. For users who work with visual items and prefer spatial access to list access, this is a meaningful difference.

Ditto lives in the system tray, opens on click, and shows a list. The interaction is click-first, list-based. For users who want a list, this is the right interaction. For users who want a shelf, it is not. For more on the trade-offs, see why tray icons lost to edges and launchers.

Visual UI

Edge-Drop's UI is a vertical shelf with thumbnails for images, previews for files, and one-line snippets for text. Ditto's UI is a list with small icons. For users who work with images and files, the visual UI is a real productivity win; for users who work with text only, it is decorative.

Modern stack

Edge-Drop is React 18, TypeScript, Zustand, Framer Motion. The codebase is modern, which makes contribution easier for developers familiar with the current web stack. Ditto is C++/MFC, which is a higher barrier for new contributors. This is a long-term consideration, not a user-facing feature, but it matters for the project's future.

Where the two are simply different

A few axes are not "wins" or "losses" — they are differences in design intent:

Local-first posture

Both Ditto and Edge-Drop are local-first. Neither ships cloud sync by default. Both store data on the device. The difference is that Ditto's sync feature exists (deprecated but present), while Edge-Drop's does not exist at all. For users who want to be sure sync is off, Edge-Drop is the simpler choice; for users who want the option to sync, Ditto (or Win+V's cloud sync) is the more flexible choice. For more, see why some clipboard apps will never sync.

License

Ditto is GPL-3.0. Edge-Drop is Apache-2.0. Both are open-source. The difference is copyleft vs permissive, which matters for downstream use but not for end users. For more, see Apache-2.0 clipboard tools you can actually audit.

Target user

Ditto is for the power user who wants long history, low RAM, and a list. Edge-Drop is for the designer or multi-tasker who wants drag-out, spatial access, and a shelf. The two tools are for different users, and the honest recommendation depends on which user is asking.

A summary table

The pattern: Ditto wins on RAM, history, scripting, and maturity. Edge-Drop wins on drag-out and spatial access. The two are different tools for different workflows, and the honest recommendation depends on the workflow.

The strategy, stated plainly

Edge-Drop's strategy is not "be better than Ditto at everything." That strategy would fail, because Ditto is older, lighter, and more mature. Edge-Drop's strategy is "be the best tool for the specific workflow of drag-out and spatial access, and accept that Ditto is the best tool for long-history list use."

This is the honest case for Edge-Drop's existence. It does not require Ditto to be bad. It requires Edge-Drop to be different, in a way that serves a specific user, and to be honest about where it loses. For more on this, see what Edge-Drop is not trying to become and the case for boring clipboard software.

How to choose

For users choosing between Ditto and Edge-Drop, the practical questions:

1. Is RAM a constraint? If yes (low-RAM hardware, multiple heavy apps already running), Ditto wins.
2. Is long-history search the bottleneck? If yes (you often need to find items from weeks ago), Ditto wins.
3. Do you want scripted transformations? If yes (auto-redact tokens, auto-strip formatting), Ditto or CopyQ wins.
4. Do you drag assets into desktop apps frequently? If yes (Photoshop, Word, Slack, Explorer), Edge-Drop wins.
5. Do you want a visual shelf rather than a list? If yes, Edge-Drop wins.

The two tools are not exclusive. A user who does both long-history search and drag-out can run both, with Ditto as the long-term store and Edge-Drop as the staging surface. For more on running multiple tools, see can you run two clipboard tools at once and agency stack: designers, PMs, and devs differ.

Related reading

• How to Cite Open-Source Tools in a Roundup Fairly
• Donations, Stores, and Keeping a Free App Alive
• What Local-First Software Means for Clipboard Apps
• How to Enable Clipboard History in Windows 11

Sources

• Ditto — GitHub README — official source, license, and platform support for the clipboard manager Edge-Drop is compared against
• Electron — webContents.startDrag — official API reference for the drag-out API that is Edge-Drop's primary differentiator
• Microsoft Learn — OLE drag and drop — official documentation for the Windows OLE drag-and-drop surface that both Ditto and Edge-Drop use
• Apache Software Foundation — Apache License 2.0 — full text of the Apache-2.0 license Edge-Drop uses, for comparison with Ditto's GPL-3.0
• Microsoft Support — Using the clipboard on Windows — official Windows clipboard documentation, the baseline both tools build on

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