Is Apache 2.0 compatible with MPL 2.0?
Apache 2.0-licensed code is compatible with a MPL 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
Permissive licenses like Apache 2.0 carry few restrictions, so they can be absorbed into copyleft projects like MPL 2.0.
Key obligations
Retain the original copyright notices and license text for the Apache 2.0 components.
Potential conflicts
None. The copyleft terms supersede the permissive terms for the combined work.
Distribution notes
The combined work as a whole must be distributed under MPL 2.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
Apache License 2.0 is a permissive (+ patent grant) license and Mozilla Public License 2.0 is a weak copyleft license. That combination is generally safe to ship: you can include the Apache 2.0 library in a MPL 2.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 Apache 2.0 → MPL 2.0
- Retain the original Apache 2.0 copyright and license notices.
- Record that your project bundles Apache 2.0-licensed components (e.g. in an attribution or NOTICE file).
- Distribute the combined work under terms that satisfy MPL 2.0.
- Re-check the verdict if you switch to SaaS delivery or start modifying the component.
About these licenses
Apache License 2.0
LibraryPermissive, with an express patent grant and a NOTICE-file requirement. Its patent terms make it incompatible with GPL v2.0.
- Type
- Permissive (+ patent grant)
- Patent grant
- Express
- Source sharing
- Not required
Mozilla Public License 2.0
ProjectWeak, file-level copyleft. You must share changes to MPL-covered files, but the rest of your project can use another license.
- Type
- Weak copyleft
- Patent grant
- Express
- Source sharing
- Modified files only
Apache 2.0 and MPL 2.0: frequently asked questions
Common questions about combining Apache License 2.0 and Mozilla Public License 2.0.
Is Apache 2.0 compatible with MPL 2.0?
Permissive licenses like Apache 2.0 carry few restrictions, so they can be absorbed into copyleft projects like MPL 2.0.
Can I use Apache 2.0 code in a MPL 2.0 SaaS or cloud application?
Permissive licenses like Apache 2.0 carry few restrictions, so they can be absorbed into copyleft projects like MPL 2.0.
What are my obligations when combining Apache 2.0 and MPL 2.0?
Retain the original copyright notices and license text for the Apache 2.0 components. The combined work as a whole must be distributed under MPL 2.0.