# GNU Lesser General Public License (LGPL)

> A copyleft rule made for libraries. Your app can stay closed. Fixes to the library get shared.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** LGPL, LGPLv3, LGPL-3.0, Lesser GPL

## Think of it like

It is like a shared tool you may use in your own shop. If you fix the tool, you share the fix.

## Definition

The LGPL is a weaker copyleft license made for libraries. A closed or paid program may use an LGPL library without opening its own code. But if you change the library itself, you must share those changes under the same license. Users must also be able to swap in their own copy of the library. It sits between the MIT license and the GPL.

## Example

Emma's paid video app uses an LGPL library to read files. Her app stays closed, but a bug fix she makes to the library is shared.

## Why it matters

Paid apps can use a free library like this. The library itself still stays open for all.

## Common mistake

Treating it like the MIT license. Changes to the library must be shared, and users must be able to swap it. This is a plain summary, not legal advice.

## Three principles

- **For libraries.** Made for code other apps use.
- **Your app can stay closed.** Only the library stays open.
- **Share library changes.** Fixes to it go back out.

## Related terms

- [Copyleft](https://learn.benibix.com/term/development/copyleft)
- [GNU General Public License (GPL)](https://learn.benibix.com/term/development/gnu-gpl)
- [Software Library](https://learn.benibix.com/term/development/library)
- [Software License](https://learn.benibix.com/term/development/software-license)
- [Mozilla Public License 2.0 (MPL)](https://learn.benibix.com/term/development/mozilla-public-license)

## Told apart from

- [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.

![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/lgpl
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.
