Skip to main content
FOSSA Logo
Free License Tool

Is MIT compatible with Apache 2.0?

MIT-licensed code is compatible with a Apache 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.

MITApache 2.0
Compatible

The short answer

Both licenses are permissive and place minimal restrictions on combining, modifying, and distributing the code.

Key obligations

Retain copyright notices and disclaimers for the MIT code.

Potential conflicts

None. Both licenses allow free incorporation into other works.

Distribution notes

Distribute under Apache 2.0, respecting the notice requirements of MIT.

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

MIT License is a permissive license and Apache License 2.0 is a permissive (+ patent grant) license. That combination is generally safe to ship: you can include the MIT library in a Apache 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 MIT Apache 2.0

  • Retain the original MIT copyright and license notices.
  • Record that your project bundles MIT-licensed components (e.g. in an attribution or NOTICE file).
  • Distribute the combined work under terms that satisfy Apache 2.0.
  • Re-check the verdict if you switch to SaaS delivery or start modifying the component.

About these licenses

MIT License

Library

A short, highly permissive license. Use it almost anywhere as long as you keep the copyright and license notice.

Type
Permissive
Patent grant
None
Source sharing
Not required

Apache License 2.0

Project

Permissive, 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

MIT and Apache 2.0: frequently asked questions

Common questions about combining MIT License and Apache License 2.0.

Is MIT compatible with Apache 2.0?

Both licenses are permissive and place minimal restrictions on combining, modifying, and distributing the code.

Can I use MIT code in a Apache 2.0 SaaS or cloud application?

Both licenses are permissive and place minimal restrictions on combining, modifying, and distributing the code.

What are my obligations when combining MIT and Apache 2.0?

Retain copyright notices and disclaimers for the MIT code. Distribute under Apache 2.0, respecting the notice requirements of MIT.

Explore related comparisons

The other direction

Get Started with FOSSA

Start managing your dependencies, licenses, and vulnerabilities today.