GNU General Public License v3.0, explained
Strong copyleft GPL-3.0-only · GPL-3.0-or-later
GPL-3.0 is a strong copyleft: if you distribute software that includes or links GPL-3.0 code, the whole program must be offered under GPL-3.0 with its source, and users must be able to install modified versions.
Not legal advice. Read the licence text for the exact terms.
What it allows
- Use, study, change and run the code for any purpose
- Sell copies, under the GPL
- Combine it with Apache-2.0 code
What it requires
- Distribute the complete corresponding source with binaries
- License the whole combined work under GPL-3.0
- For consumer devices, provide the installation information needed to run modified versions
- Grant recipients a licence to any of your patents the code needs
When it matters
| Shipping an app (desktop, mobile, on-premises) | If your app includes or links the code, the combined work must be offered under the same GPL version, with its complete source code. A closed-source app cannot do that. |
|---|---|
| A hosted service (SaaS) | Running the code on your own servers is not distribution: the GPL does not require you to publish your source. It does if you ship code to users, such as JavaScript bundles, desktop agents or an on-premises version. |
| Internal use | Allowed with no conditions while the software stays inside your organisation (contractors working for you included, in the usual reading). |
Its family: strong copyleft
If you distribute software that includes or links this code (an installer, a mobile or desktop app, a container image you hand out, JavaScript sent to browsers), the whole combined work must be offered under the same licence, with its source code. Running it only on your own servers is not distribution.
Questions
Can I use GPL-3.0 code in a SaaS?
Yes: running it on your servers is not distribution. AGPL-3.0 is the variant that covers network use.
Can I use GPL libraries in a commercial app?
You can sell GPL software, but a closed-source app that includes or links GPL code and is distributed cannot keep its source closed.
Other licences
Related free tools
Dependency licence check
Upload a lockfile and see every dependency's licence. GPL, AGPL, unknown and changed licences are flagged for your kind of project. Free.
SBOM summary generator
Upload a lockfile and get an SBOM summary by email: components, licences, vulnerabilities and AI components. CycloneDX and SPDX files with Pro.
Published ; awaiting review.