Is GPL 3.0 compatible with AGPL 3.0?
GPL 3.0-licensed code is compatible with a AGPL 3.0 project. Here is what that means for your obligations, conflicts, and distribution.
The license of the code you want to use.
The license you are applying to your project.
The short answer
GPL v3.0 and AGPL v3.0 were explicitly designed to work together. You can combine GPL v3.0 code into an AGPL v3.0 project; the AGPL's network-use clause then applies to the combined work.
Key obligations
Retain the GPL v3.0 notices and release the combined work under AGPL v3.0, including offering source to network users.
Potential conflicts
None for combining. The AGPL's Section 13 network-copyleft obligation will extend to the combined work.
Distribution notes
Distribute (and, for network use, offer source of) the combined work under AGPL v3.0.
Deep-dive resources
Stop guessing. Start automating.
Modern applications pull in hundreds of transitive dependencies. A manual check can't keep up.
Disclaimer: This tool offers general guidance based on widely accepted open source community norms and does not constitute legal advice. For commercial use, always consult legal counsel or use a dedicated compliance platform like FOSSA to analyze your specific dependency graph.
What this means in practice
GNU GPL v3.0 is a strong copyleft license and GNU AGPL v3.0 is a network copyleft license. That combination is generally safe to ship: you can include the GPL 3.0 library in a AGPL 3.0 project as long as you meet the notice and distribution requirements below. Internal-only use rarely triggers copyleft obligations, while shipping binaries or running a public network service is more likely to.
Compliance checklist for GPL 3.0 → AGPL 3.0
- Retain the original GPL 3.0 copyright and license notices.
- Record that your project bundles GPL 3.0-licensed components (e.g. in an attribution or NOTICE file).
- Distribute the combined work under terms that satisfy AGPL 3.0.
- Re-check the verdict if you switch to SaaS delivery or start modifying the component.
About these licenses
GNU GPL v3.0
LibraryStrong copyleft with patent and anti-tivoization protections. Designed to be compatible with Apache 2.0.
- Type
- Strong copyleft
- Patent grant
- Express
- Source sharing
- Entire combined work
GNU AGPL v3.0
ProjectNetwork copyleft. Closes the "SaaS loophole" — offering the software over a network triggers the obligation to share source.
- Type
- Network copyleft
- Patent grant
- Express
- Source sharing
- Combined work + network use
GPL 3.0 and AGPL 3.0: frequently asked questions
Common questions about combining GNU GPL v3.0 and GNU AGPL v3.0.
Is GPL 3.0 compatible with AGPL 3.0?
GPL v3.0 and AGPL v3.0 were explicitly designed to work together. You can combine GPL v3.0 code into an AGPL v3.0 project; the AGPL's network-use clause then applies to the combined work.
Can I use GPL 3.0 code in a AGPL 3.0 SaaS or cloud application?
GPL v3.0 and AGPL v3.0 were explicitly designed to work together. You can combine GPL v3.0 code into an AGPL v3.0 project; the AGPL's network-use clause then applies to the combined work.
What are my obligations when combining GPL 3.0 and AGPL 3.0?
Retain the GPL v3.0 notices and release the combined work under AGPL v3.0, including offering source to network users. Distribute (and, for network use, offer source of) the combined work under AGPL v3.0.