Can You Run Two Clipboard Tools at Once?
Running two clipboard tools at once is sometimes necessary, sometimes fine, and sometimes a recipe for duplicate captures and conflicting hotkeys. The honest answer depends on which two tools. Two clipboard managers running together is usually a bad idea; a clipboard manager plus a screenshot tool or a text expander is a sensible pairing. This guide covers the cases and what to watch for in each.
For the related context, see migration plan: leaving Ditto for a visual shelf and what "best" means in clipboard roundups.
Why two clipboard managers usually conflict
Most Windows clipboard managers work the same way: they listen for clipboard updates via AddClipboardFormatListener (the modern API) or SetClipboardViewer (the legacy chain), and they write each update to their own history. When two managers are running, both receive every clipboard update, and both capture every copy.
This produces three problems:
- Double capture. Every copy appears in both histories. This is harmless to the OS, but it doubles the storage cost and produces duplicate entries when the user searches either history.
- Hotkey conflicts. Most clipboard managers bind a global hotkey to open their history window. Ditto defaults to
Ctrl+~; CopyQ toCtrl+Shift+C; Edge-Drop toAlt+Cand hover; ArsClip toCtrl+Shift+Insert. These do not always conflict directly, but if the user has customised any of them, collisions are common. - Paste behaviour. Some clipboard managers simulate paste by sending
Ctrl+Vafter placing the item on the clipboard. If two managers are running, the second manager captures the item the first manager placed, producing a feedback loop in the histories.
The third problem is the most annoying. When the user clicks an item in Ditto's history to paste it, Ditto places the item on the clipboard and sends Ctrl+V. Edge-Drop, also running, sees the clipboard update and captures the item — even though the user did not "copy" it in any meaningful sense. The result is that Edge-Drop's history fills up with items the user only ever pasted, never copied.
For this reason, the recommendation is: do not run two clipboard managers long-term. Run them in parallel only during a migration week (see migration plan: leaving Ditto for a visual shelf), and disable one as soon as the migration is complete. For the dedicated failure-mode article, see two clipboard managers fighting each other.
Case 1: Two clipboard managers
Pairings to avoid:
- Ditto + Edge-Drop. Both watch the clipboard. Both capture every copy. Double capture, plus the paste-feedback loop described above. Pick one.
- Win+V + Ditto. Same problem. Win+V is built-in, so it is easy to forget it is running. If a third-party manager is installed, consider disabling Win+V via Settings → System → Clipboard → Clipboard history → Off. See how to turn clipboard history off completely.
- CopyQ + Edge-Drop. Same problem. CopyQ's scripting makes the feedback loop worse, because CopyQ may transform the item before re-capturing it.
- ArsClip + Ditto. Same problem. Two tray-based managers fighting for the same role.
There is one legitimate reason to run two clipboard managers: the transition week during a migration. In that case, the duplicate capture is a known cost, and it goes away when one manager is uninstalled.
Case 2: Clipboard manager + screenshot tool
This pairing is fine, and is common among designers and writers.
A screenshot tool (ShareX, Snipping Tool, Greenshot) captures a region or window to the clipboard. The clipboard manager (Ditto, CopyQ, Edge-Drop) sees the bitmap on the clipboard and captures it into history.
The pairing works because the screenshot tool is a producer, not a consumer. It writes to the clipboard; it does not maintain its own clipboard history. There is no double capture, no hotkey conflict (screenshot tools bind to Win+Shift+S or Print Screen, not to clipboard-manager hotkeys), and no feedback loop.
Edge-Drop pairs particularly well with ShareX, because ShareX can be configured to write the screenshot to the clipboard (so Edge-Drop captures it) and to a file on disk (so the user can drag it into Slack, Word, or Photoshop from Edge-Drop's shelf later). See edge-drop vs ShareX: not competitors, how they pair and choose ShareX first if capture is the job.
Things to watch:
- Screenshot tool's own history. ShareX has an "upload history" that is separate from the clipboard. It is not a clipboard manager; it is a list of what ShareX has captured. Do not confuse the two.
- Format. Screenshots land on the clipboard as bitmaps. Bitmaps are large (a 1080p screenshot is ~6 MB as a raw bitmap, ~200 KB as PNG). Win+V caps each item at 4 MB and may truncate large bitmaps. Ditto, CopyQ, and Edge-Drop handle large bitmaps by storing them on disk and keeping a thumbnail in history. See what the Windows clipboard can and cannot store and 4K screenshots blow past clipboard limits.
Case 3: Clipboard manager + text expander
This pairing is also fine, and is common among developers and writers.
A text expander (Espanso, PhraseExpress, TextExpander) replaces typed shortcuts with longer text. It writes the expanded text to the clipboard, sends Ctrl+V, and restores the previous clipboard content. The clipboard manager sees the expanded text briefly, captures it, and continues.
The pairing works because the text expander is a producer of one-shot clipboard writes, not a consumer of clipboard updates. There is no double capture of ongoing copies, no hotkey conflict (expanders bind to typed shortcuts, not to global keys), and the feedback loop is minimal — the expander restores the clipboard after each expansion, so the manager's history sees the expanded text only briefly.
Edge-Drop pairs well with Espanso, because the two cover different jobs: Espanso handles typed shortcuts (snippets the user types often), Edge-Drop handles spatial staging (items the user drags around). See edge-drop vs Espanso: mouse staging vs typed shortcuts and choose an expander first if you type the same text.
Things to watch:
- Espanso's clipboard restore. Espanso restores the clipboard after expansion by default. If the user disables this (in
config/default.yml), every expansion will overwrite the clipboard history. Keep the restore on. - PhraseExpress's clipboard cache. PhraseExpress has its own clipboard cache, which can conflict with a dedicated clipboard manager. Disable PhraseExpress's cache if a dedicated manager is also running.
- Expansion feedback. If the clipboard manager captures the expanded text on every expansion, the history fills with expansion results. Most expanders restore the clipboard fast enough that the manager does not capture the expansion. Verify this in the first hour of use.
Case 4: Clipboard manager + cloud sync tool
This pairing is uncommon but comes up in enterprise environments.
A cloud sync tool (Microsoft's own Win+V sync, a third-party sync relay) syncs clipboard text across devices. The clipboard manager runs locally on each device. The pairing works because the sync tool writes to the clipboard on the receiving device, and the manager captures the synced item just like any other copy.
Things to watch:
- Sync is text-only for Win+V. Microsoft's clipboard sync sends text only, not images or files. See Windows clipboard settings, line by line and clipboard sync says on but devices disagree.
- Sync latency. Synced items may appear in the manager's history seconds or minutes after they were copied on the source device. This is normal.
- Privacy. Cloud sync sends clipboard text through Microsoft's infrastructure. On machines handling production credentials, sync should be off. See best clipboard manager if you care about privacy.
A decision table
| Pairing | OK? | Watch for |
|---|---|---|
| Clipboard manager + clipboard manager | No (except migration week) | Double capture, hotkey conflict, paste feedback |
| Clipboard manager + screenshot tool | Yes | Screenshot tool's own history is separate; bitmap size |
| Clipboard manager + text expander | Yes | Expander's clipboard restore; expansion feedback |
| Clipboard manager + cloud sync | Yes | Sync is text-only for Win+V; privacy on credential machines |
When NOT to use Edge-Drop
Edge-Drop is a clipboard watcher. The "do not pair two watchers" rule applies to it the same way it applies to Ditto, CopyQ, and ArsClip. Specifically:
- Do not pair Edge-Drop with Ditto. Pick one. Edge-Drop wins on drag-out; Ditto wins on search, RAM, and sync. See edge-drop vs Ditto: hover shelf or tray history.
- Do not pair Edge-Drop with CopyQ. Pick one. Edge-Drop wins on drag-out; CopyQ wins on scripting. See edge-drop vs CopyQ: drag shelf vs scriptable clipboard.
- Do not pair Edge-Drop with Win+V. Pick one. Win+V is built-in and free; Edge-Drop wins on files, drag-out, and encryption at rest.
- Edge-Drop + ShareX is fine. ShareX is a producer, not a watcher.
- Edge-Drop + Espanso is fine. Espanso is an expander, not a watcher.
For the full picture, see when NOT to use Edge-Drop.
A short verdict
Two clipboard managers running together is almost always a bad idea outside a migration week. The duplicate capture is harmless to the OS but pollutes both histories, and the paste-feedback loop is annoying.
A clipboard manager plus a screenshot tool, a text expander, or a cloud sync tool is a sensible pairing, because the second tool is a producer or a transport, not a competing consumer. The two roles do not overlap, and the user gets the benefit of both without conflict.
For the broader question of which clipboard manager to pick in the first place, see scorecard: pick a Windows clipboard tool in 10 minutes and best free clipboard manager for Windows.
Related reading
- What 'Best' Means in Clipboard Roundups
- Red Flags in Clipboard App Marketing
- Best Free Clipboard Manager for Windows
- How to Install Edge-Drop on Windows 10 and 11
Sources
- Microsoft Learn — AddClipboardFormatListener function — official documentation for the modern Windows clipboard listener API used by Ditto, CopyQ, and Edge-Drop
- Microsoft Support — Using the clipboard on Windows — official Win+V limits (25 items, 4 MB per item, text-only sync) referenced in the screenshot and sync sections
- ShareX — GitHub README — official ShareX repository documenting the screenshot-to-clipboard workflow and the upload history feature
- Espanso — GitHub README — official Espanso repository documenting the clipboard restore behaviour that determines whether the clipboard manager captures expansions
- Edge-Drop — GitHub README — official Edge-Drop repository documenting the concealed-format skip list, the hover activation, and the pairing model with ShareX and Espanso
Deepender Yadav is a B.Tech Computer Science Engineering student and software developer interested in building practical software and open-source projects.
GitHub · LinkedInCopy. 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
Free · Lightweight · Privacy First