# Copyleft

> A rule in some open licenses. If you share a changed copy, its code must stay open.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** Copyleft License, Copyleft Licence, Share-Alike License

## Think of it like

It is like a toy you may change and pass on. The next child gets the same deal.

## Definition

Copyleft is a rule in some open source licenses that keeps changed copies open too. You may use, change and share the code. But if you hand out a changed version, you must share its code under the same license. So nobody can take the code, close it and sell it as a secret. The GNU GPL is the best-known copyleft license.

## Example

Jack changes a GPL tool and sells copies to customers. Copyleft means he must give those customers his changed code too.

## Why it matters

It keeps a shared project shared. Some companies avoid copyleft code in closed products, so check before you use it.

## Common mistake

Thinking copyleft bans selling the code. You may sell it; you must also share the code. This is a plain summary, not legal advice.

## Three principles

- **Stays open.** Changed copies keep the same license.
- **Share on hand-out.** The rule starts when you give it out.
- **Strong or weak.** Some cover a whole app, some one file.

## Related terms

- [Software License](https://learn.benibix.com/term/development/software-license)
- [Permissive License](https://learn.benibix.com/term/development/permissive-license)
- [GNU General Public License (GPL)](https://learn.benibix.com/term/development/gnu-gpl)
- [GNU Affero General Public License (AGPL)](https://learn.benibix.com/term/development/agpl)
- [GNU Lesser General Public License (LGPL)](https://learn.benibix.com/term/development/lgpl)
- [Mozilla Public License 2.0 (MPL)](https://learn.benibix.com/term/development/mozilla-public-license)

## Told apart from

- [Permissive License vs Copyleft](https://learn.benibix.com/compare/permissive-license-vs-copyleft): People think a permissive license and copyleft are both just open source, so the rules match, and they do not. A permissive license asks you to keep the notice, and your own code can stay closed. Copyleft asks more. If you hand out a changed copy, you must share its code under the same license.

![A line of licences from the fewest rules on the left to the most on the right. Permissive: MIT, BSD and Apache 2.0, where you only keep the notice. Weak copyleft: LGPL and MPL 2.0, where you share changes to the library or the file. Strong copyleft: GPL, where you share the code of the whole program you hand out. Network copyleft: AGPL, where running it as a web service counts too.](https://learn.benibix.com/diagrams/dev5-license-spectrum.svg)

---

Source: https://learn.benibix.com/term/development/copyleft
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
