← Back to Blog

Developers & Code | Published Aug 21, 2026 | Updated Nov 21, 2026 | 6 min read

Open-Source Clipboard Licenses: Apache vs GPL vs MIT

By Deepender Yadav

Open-Source Clipboard Licenses: Apache vs GPL vs MIT — Edge Drop Guide

Among open-source clipboard managers, Edge Drop and EcoPaste use the Apache License 2.0, Maccy and Microsoft PowerToys use MIT, and Ditto and CopyQ use GPL-3.0. For someone who just installs and uses the app, all three licences give the same practical rights: it's free to use, at home or at work, and you can read every line of the source. The differences start when you modify the code, redistribute it, or build it into another product.

Which clipboard tools use which licence

ToolWhat it isPlatformsLicence
Edge DropScreen-edge clipboard shelfWindowsApache-2.0
EcoPasteClipboard managermacOS, WindowsApache-2.0
MaccyClipboard managermacOSMIT
PowerToysUtility suite that includes Advanced PasteWindowsMIT
DittoClipboard managerWindowsGPL-3.0
CopyQScriptable clipboard managerWindows, macOS, LinuxGPL-3.0
EspansoText expanderWindows, macOS, LinuxGPL-3.0
ShareXScreenshot and capture toolWindowsGPL-3.0

Licences are as listed in each project's GitHub repository. Check the LICENSE file in the repository yourself before you rely on one, since projects can change licence between versions. The best open-source clipboard managers compares these apps on features rather than licences.

Apache-2.0 vs MIT vs GPL-3.0

Apache-2.0MITGPL-3.0
Use, modify and distribute, including commerciallyYesYesYes
Express patent grant from contributorsYesNoYes
Keep the licence and copyright noticesRequiredRequiredRequired
State changes you madeRequiredNot requiredRequired
Release your changes' source when you distributeNot requiredNot requiredRequired, under GPL-3.0
Ship a closed-source product built on itAllowedAllowedNot allowed

In short:

  • MIT is the shortest and most permissive. Keep the notice and you can do almost anything.
  • Apache-2.0 is also permissive, but adds an explicit patent licence from contributors, asks you to mark files you changed, and requires you to pass on any NOTICE file the project includes. It also says plainly that it grants no rights to the project's name or logo, so a fork has to use its own name.
  • GPL-3.0 is copyleft. If you distribute a modified version, you must release its source under the same licence. That keeps every distributed version open, but rules out closed-source products built on the code.

Can Apache-2.0 and GPL code be combined?

In one direction. The Apache Software Foundation, citing the Free Software Foundation, says Apache-2.0 code can be included in GPL-3.0 projects, but GPL-3.0 code can't be included in Apache-licensed projects. Apache-2.0 is not compatible with GPL version 2.

What the licence means for you as a user

At home: nothing changes. Every tool in the table is free to install and use.

At work: all of these licences permit commercial use. Your IT department may still have its own approval process for software, which is separate from the licence.

If you change the code for internal use: none of these licences forces you to publish changes you never distribute. GPL-3.0's source requirement applies when you give or sell the modified program to others.

If the project stops: any of these licences lets the community fork and continue it. What happens if a solo app goes quiet covers that risk in more detail.

A licence makes an audit possible, not automatic

Open source means you, or someone you trust, can check what the app does. It doesn't mean anyone has. To audit an open-source clipboard app, look at:

  1. Storage. Where history is saved, in what format, and what is encrypted. A clipboard history file is a record of what you've copied.
  2. Network code. Every outbound request the app can make, and when. Confirm it with a capture: how to check whether a desktop app has telemetry shows the method.
  3. What it refuses to capture. Whether it honours the clipboard formats password managers use to mark content as private.
  4. Dependencies. Each library in the dependency list is code you're also trusting.
  5. Release builds. Whether the published installer is built by a public CI workflow from a tagged commit, or on the maintainer's machine. If it's the latter, building from source yourself is the only way to be sure the binary matches the code.

For Electron apps, also check the window security settings and the API the preload script exposes; checking an Electron app's security settings walks through that.

Auditing Edge Drop

Edge Drop's source is public on GitHub under Apache-2.0. The places to start:

  • electron/store/ for storage. The history index (items.json) is encrypted with Windows DPAPI; saved images, long-text files and settings are not.
  • electron/clipboard/formats.ts for the checks that make Edge Drop skip a copy. It honours the standard Windows flags that mark content as excluded from clipboard history, cloud sync or monitoring.
  • electron/main/updater.ts for the update checks, which are the app's only automatic network requests (GitHub build only, and none when updates are set to Off). Edge Drop also fetches a web image only when you drop one onto the shelf.
  • package.json for dependencies. The runtime dependencies are @resvg/resvg-js, electron-updater, koffi, react and zustand, with no analytics or crash-reporting packages.

The repository's one CI workflow only counts installer downloads for the README badge. It builds and signs nothing, so releases aren't built by a public pipeline, and no one has published a third-party audit. If you need certainty that a binary matches the source, build Edge Drop from source.

FAQ

Is Edge Drop open source?

Yes. Edge Drop is licensed under the Apache License 2.0, and the full source is on GitHub.

Is an Apache-2.0 app safer than a GPL one?

No. The licence decides what you may do with the code, not how secure it is. Both let you read and check the source.

Can a company use a GPL-3.0 clipboard manager?

Yes. GPL-3.0 allows commercial use. Its extra obligations apply only if the company distributes a modified version.

Related reading

Sources

Deepender Yadav
Written by Deepender Yadav · Creator & Developer

Deepender Yadav created Edge Drop and builds and tests it, from the edge-hover shelf to each release. A B.Tech Computer Science Engineering student, Deepender writes the Edge Drop guides, comparisons and developer posts, and checks product details against the app's source code.

GitHub · LinkedIn

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

Free · Lightweight · Privacy First
Find us on CodeHype