CopyQ vs ClipboardFusion: Scripts vs Vendor Macros

Automation buyers should not start with "best clipboard manager." They should start with where the code will live.

CopyQ is an open-source manager whose power is a command language, a CLI, and tabs. Lukas Holecek's project stores any format, runs commands on clipboard change, and talks to scripts via copyq on the path.

ClipboardFusion is a Binary Fortress product whose power is C# macros, a trigger system, optional Pro sync, and a supported Windows installer. The free tier remains useful after the 30-day Pro trial.

Both will store history. Both will embarrass Win+V on depth. Neither is a hover shelf. Neither is a text expander. If the user only needed persistence and search, Ditto is still the smaller brain.

Official CopyQ surface

hluk.github.io/CopyQ and the docs:

• Windows, Linux, macOS.
• Tabs of items; edit, tag, note, sort, drag inside the manager.
• Command dialog (F6): run on shortcut or on clipboard change.
• Ignore copies from certain windows or matching text.
• CLI: copyq add, read, clipboard, copy, write images from files.
• Appearance customization, Vim-like editor option.
• GPLv3, GitHub Actions builds, Scoop/Chocolatey/installer.

The scripting environment is CopyQ's own language plus the ability to shell out. That is freedom and a documentation tax.

Official ClipboardFusion surface

clipboardfusion.com:

• Strip formatting automatically or by hotkey.
• Replace strings.
• C# macros in an integrated editor; community macro library.
• Triggers for event-driven actions (advanced actions on Pro).
• Sync via Binary Fortress Account, 256-bit encryption stated, mobile companions. Pro.
• Manager window: history, pins, online items, macros.
• Free forever after trial for basic use; Pro SKUs listed around $19 Standard / $29 Personal per machine on the compare/purchase pages (confirm live).
• Actively shipped (6.3 stable in late 2025; 6.4 beta on .NET 10 in 2026).

C# plus a vendor editor is a different tax: Visual Studio familiarity helps; the macros are not as portable to Linux as CopyQ tabs.

Win+V is the non-automation baseline

25 items, 4 MB, text/HTML/bitmap, restart wipe, optional Microsoft text sync. No scripts. If the written job does not include "when I copy X, do Y," buy nothing. Enable history. Stop.

PowerToys Advanced Paste covers a few named transforms (plain, Markdown, JSON, OCR) without either of these apps. Check that list before committing to a macro platform.

Side-by-side

Open scripts

CopyQ wins when:

• The same rules must run on a Linux box and a Windows box.
• History tabs are part of the workflow ("inbound," "clean," "images").
• CI or a terminal needs copyq clipboard.
• The user refuses a vendor account.
• Ignore rules are the privacy model.

CopyQ loses when:

• The user does not want to read copyq --help.
• The desired action is "make paste plain" and they will never write another rule — ClipboardFusion or PowerToys is faster to first value.
• A boss wants a phone number on a support contract.

Put CopyQ commands in version control. That is the hidden product: clipboard behavior as code.

Vendor macros and paid sync

ClipboardFusion wins when:

• C# is already the house language.
• Format scrubbing should be a checkbox, not a weekend.
• Triggers plus a GUI are how the team will maintain rules.
• Phone/PC text sync is a written requirement and Microsoft's text pipe is not enough.
• The environment already trusts Binary Fortress (DisplayFusion, etc.).

ClipboardFusion loses when:

• Sync is enabled "because Pro" and now OTPs roam.
• The user needed Linux.
• The user needed a CLI in a build script (CopyQ).
• Paying per machine for what a 20-line CopyQ command does is silly.

Encryption on the sync channel does not decide whether the *contents* should leave. Treat CF sync like 1Clipboard: off until the job is non-secret text on two devices.

A fair bake-off

Write three rules on paper. Examples:

1. If the copy is a URL, strip utm_*.
2. If the copy is from Chrome, paste as plain text by default.
3. If the copy matches a password-manager window, ignore it.

Implement all three in CopyQ commands. Implement all three in ClipboardFusion macros/triggers (Pro if needed). Time to working, time to debug, and whether rule 3 actually fired.

Then copy a 5 MB screenshot and a folder of files. Neither tool's automation story should be judged on drag-out — that is Edge-Drop's aisle — but both should survive the copy without crashing.

If rule 1 took an hour in both, consider whether a browser extension should own UTM stripping instead.

Do not stack automation platforms

CopyQ + ClipboardFusion both watching the clipboard is a race. One rewriter will see the other's output and fire again. Pick one automation host. Ditto can still be the search UI only if it is not also transforming — in practice, pick one historian-plus-engine.

A shelf can sit beside *one* engine if capture is assigned carefully. Most automation buyers never need the shelf.

Decision

The logo is not the product. The language is. Choose the language the next person on the team can read.

A starter rule that both can implement

Goal: copies from a browser arrive as plain text, except when the user explicitly asks for HTML.

CopyQ approach: a command that matches the browser window, replaces the clipboard with the text/plain representation, and optionally stores the original HTML on a second tab. Check the current docs for the exact command syntax; the CLI copyq clipboard text/plain is the debugging hammer.

ClipboardFusion approach: an automatic formatting-removal option, or a trigger that fires on clipboard change from the browser process, or a C# macro bound to a hotkey if automatic is too aggressive.

Both can fail in Edge when the only available format is HTML. Both can surprise Word users who wanted the styles. Write the exception down ("Ctrl+Shift+V keeps HTML" or similar) so the team does not fight the tool.

If implementing this single rule takes more than an hour in both apps, the team may only have needed PowerToys' paste-as-plain-text shortcut. Automation platforms earn their keep on the fifth rule, not the first.

Leave Microsoft text sync off while rules are being debugged. A rewritten clipboard that then uploads is a confusing incident report.

The product-level comparison is PhraseExpress vs Ditto: Expander or Manager?.

Related reading

• ShareX vs Snipping Tool vs a Clipboard Manager
• PhraseExpress vs Ditto: Expander or Manager?
• Best Clipboard Managers for Windows in 2026
• Does Windows Clipboard Sync Upload What You Copy?

Sources

• CopyQ official site — commands, CLI, tabs, platforms.
• CopyQ documentation — scripting reference.
• hluk/CopyQ on GitHub — releases and license.
• ClipboardFusion homepage — macros, triggers, sync, free/Pro.
• ClipboardFusion compare — paid feature split and listed prices.
• Using the clipboard (Microsoft Support) — non-automation baseline.

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