# GNU General Public License (GPL)

> An open source license. Changes you share must stay open source too.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** GPL, GNU GPL, GPLv3, GPLv2

## Think of it like

Think of it like a shared toy. If you add to it and give it away, others may add to it too.

## Definition

The GNU GPL is an open source license that keeps code open after others change it. You may use, change and share the code. But if you share a changed version, you must share its code under the GPL too. This rule is called copyleft. Linux uses version 2, and the newest is version 3, from 2007.

## Example

Lucy builds an app on a GPL library and starts selling copies. Because she gives the app to others, she must also offer them its source code under the GPL.

## Why it matters

It stops companies from taking open code, changing it and closing it off. Everyone keeps the right to see the code.

## Common mistake

Putting GPL code in a closed app you hand to customers. That breaks the license unless you share your code too.

## Three principles

- **Use and change freely.** Like other open licenses.
- **Share alike.** Changes stay open.
- **Called copyleft.** Openness passes on.

## Related terms

- [Software License](https://learn.benibix.com/term/development/software-license)
- [Open Source Software](https://learn.benibix.com/term/development/open-source)
- [MIT License](https://learn.benibix.com/term/development/mit-license)
- [Proprietary Software](https://learn.benibix.com/term/development/proprietary-software)
- [Copyleft](https://learn.benibix.com/term/development/copyleft)
- [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)

## Told apart from

- [MIT License vs GNU GPL](https://learn.benibix.com/compare/mit-license-vs-gpl): The MIT License and the GNU GPL are both open source licenses, but they differ on what you must give back to others. MIT lets you do almost anything, even put the code in a closed app, if you keep the notice. The GPL says that if you share a changed version, you must share its code under the GPL too. MIT is free to take; the GPL keeps code open.
- [GNU GPL vs AGPL](https://learn.benibix.com/compare/gpl-vs-agpl): People think the GPL makes you share code for a web app, and it does not. With the GPL, the duty to share starts when you hand out copies. Running changed code on your own server is not handing it out. The AGPL adds that rule, so users of the web service can ask for the code too.
- [GNU GPL vs LGPL](https://learn.benibix.com/compare/gpl-vs-lgpl): People think the LGPL is just a short name for the GPL, and it is not. The GPL covers the whole program that uses the code, so that program must be open too. The LGPL is made for libraries. A closed app may use an LGPL library, as long as changes to the library itself are shared.

---

Source: https://learn.benibix.com/term/development/gnu-gpl
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-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
