GPL 3.0 vs LGPL 3.0: what is the difference?
Last updated
TL;DR: GPL 3.0: commercial use, modification, redistribution: Yes. LGPL 3.0: the same uses: Yes. GPL 3.0: Run, study, change and share the software, including commercially. If you convey it or a work based on it, you must do so under the GPL with the corresponding source. LGPL 3.0: Use the library in any program, including proprietary ones; changes to the library itself, when conveyed, stay under the LGPL with source, and users must be able to relink a modified version.
Is gPL 3.0: commercial use, modification, redistribution allowed under GNU General Public License v3.0?
Yes. Every use you described is granted by GPL 3.0, and nothing you described is prohibited.
License: GNU General Public License v3.0 (GPL-3.0-only, curated)
Duties: attribution, license_notice, state_changes, share_alike, source_disclosure
Is lGPL 3.0: the same uses allowed under GNU Lesser General Public License v3.0?
Yes. Every use you described is granted by LGPL 3.0, and nothing you described is prohibited.
License: GNU Lesser General Public License v3.0 (LGPL-3.0-only, curated)
Duties: attribution, license_notice, share_alike, source_disclosure
How do GPL-3.0-only and LGPL-3.0-only compare?
The table lists each license's duties and notes side by side.
| License | Duties | Notes |
|---|---|---|
| GPL-3.0-only | attribution, license_notice, state_changes, share_alike, source_disclosure | Sublicensing is not allowed; every recipient receives a license from the original licensors (sections 2 and 10). Running the software, including as a network service, does not by itself trigger the duty to share source; conveying copies does. |
| LGPL-3.0-only | attribution, license_notice, share_alike, source_disclosure | The copyleft duties apply to the library and modified versions of it, not to an application that only links to it. |
Combined in one work: compatible.
What else should I know?
- The duties differ: compare the duties and notes listed for each license below.
What are the sources?
How can I check it myself (free, no key)?
{
"tool": "check_license",
"arguments": {
"license": "GPL-3.0-only",
"intended_use": {
"commercial_use": true,
"modification": true,
"redistribution": true
}
}
}Computed from a2ally's license profiles; not legal advice. JSON · Markdown
Get a free API key in one call
No card and no email needed. 100 free credits; the license and policy checks stay free without a key.
curl -s -X POST https://www.a2ally.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export A2ALLY_API_KEY=rs_... # the api_key from the reply (shown once)
curl -s https://www.a2ally.com/v1/licenses/check -H "Authorization: Bearer $A2ALLY_API_KEY" \
-H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'
