Is GPL 3.0 compatible with GPL 2.0?
GPL 3.0-licensed code is not compatible with a GPL 2.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
Two different strong-copyleft licenses usually clash because each demands the whole combined work be distributed under its own terms.
Key obligations
Cannot combine without an explicit exception.
Potential conflicts
Mutually exclusive copyleft demands.
Distribution notes
Prohibited.
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 GPL v2.0 (Only) is a strong copyleft license. Combining them in a single distributed work is not permitted because their terms conflict. You can often still use the GPL 3.0 component if you keep it at arm's length — behind a separate process or network boundary — or by choosing an alternatively-licensed dependency.
Compliance checklist for GPL 3.0 → GPL 2.0
- Do not combine GPL 3.0 and GPL 2.0 code in the same distributed binary.
- Isolate the GPL 3.0 component behind a process or network boundary if you must use it.
- Evaluate an alternatively-licensed library, or re-license your project to resolve the conflict.
- Get legal sign-off before shipping anything that links the two.
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 GPL v2.0 (Only)
ProjectStrong copyleft. Distributing a combined work means releasing all of it under GPL v2.0. The "only" variant is incompatible with the GPL v3 family.
- Type
- Strong copyleft
- Patent grant
- None
- Source sharing
- Entire combined work
GPL 3.0 and GPL 2.0: frequently asked questions
Common questions about combining GNU GPL v3.0 and GNU GPL v2.0 (Only).
Is GPL 3.0 compatible with GPL 2.0?
Two different strong-copyleft licenses usually clash because each demands the whole combined work be distributed under its own terms.
Can I use GPL 3.0 code in a GPL 2.0 SaaS or cloud application?
Two different strong-copyleft licenses usually clash because each demands the whole combined work be distributed under its own terms.
What are my obligations when combining GPL 3.0 and GPL 2.0?
Cannot combine without an explicit exception. Prohibited.