MIT vs BSD-3-Clause License

MIT License compared with BSD 3-Clause "New" or "Revised" License: what each licence allows, and whether code under one can be used in a project under the other. Results are generated by the open-source license compatibility checker.

Quick Answer

Compatibility is directional, so both directions are answered separately (distributed software):

MIT code in a project licensed under BSD-3-Clause

Generally Compatible

Using MIT-licensed code in a project under BSD-3-Clause is generally compatible in this scenario.

MIT permits commercial use.

BSD-3-Clause code in a project licensed under MIT

Generally Compatible

Using BSD-3-Clause-licensed code in a project under MIT is generally compatible in this scenario.

BSD-3-Clause permits commercial use.

Key Differences

Trademark rights granted: MIT: not addressed; BSD-3-Clause: no.

Comparison Table

	MIT	BSD-3-Clause
Type	Open source	Open source
OSI approved	Yes	Yes
Commercial use	Permitted	Permitted
Modification	Permitted	Permitted
Distribution	Permitted	Permitted
Copyleft	None	None
Network-use (SaaS) clause	No	No
Source disclosure	Not required	Not required
Same licence for distributed changes	No	No
Attribution / notices	Yes	Yes
Mark modified files	No	No
Express patent licence	No	No
Patent termination clause	No	No
Trademark rights granted	Not addressed	No

Commercial Use

MIT: permitted.
BSD-3-Clause: permitted.

MIT code in a project licensed under BSD-3-Clause: MIT permits commercial use.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause permits commercial use.

Proprietary Software

MIT code in closed-source commercial software

Generally Compatible

Using MIT-licensed code in a proprietary project is generally compatible in this scenario.

MIT generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

BSD-3-Clause code in closed-source commercial software

Generally Compatible

Using BSD-3-Clause-licensed code in a proprietary project is generally compatible in this scenario.

BSD-3-Clause generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

MIT code in closed-source commercial software: MIT generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.
BSD-3-Clause code in closed-source commercial software: BSD-3-Clause generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

SaaS

Network-use clause: MIT: no; BSD-3-Clause: no.

MIT code in a closed-source SaaS

Generally Compatible

Using MIT-licensed code in a proprietary project is generally compatible in this scenario.

MIT generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

BSD-3-Clause code in a closed-source SaaS

Generally Compatible

Using BSD-3-Clause-licensed code in a proprietary project is generally compatible in this scenario.

BSD-3-Clause generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

MIT code in a closed-source SaaS: MIT has no network-use (SaaS) clause.
BSD-3-Clause code in a closed-source SaaS: BSD-3-Clause has no network-use (SaaS) clause.

Modification

MIT: permitted.
BSD-3-Clause: permitted.

Modifying MIT code used in closed-source software

Generally Compatible

Using MIT-licensed code in a proprietary project is generally compatible in this scenario.

MIT generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

Modifying BSD-3-Clause code used in closed-source software

Generally Compatible

Using BSD-3-Clause-licensed code in a proprietary project is generally compatible in this scenario.

BSD-3-Clause generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

Modifying MIT code used in closed-source software: MIT permits modification.
Modifying BSD-3-Clause code used in closed-source software: BSD-3-Clause permits modification.

Distribution

MIT: permitted.
BSD-3-Clause: permitted.

MIT code in a project licensed under BSD-3-Clause: MIT permits distribution.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause permits distribution.

Copyleft

MIT: none copyleft.
BSD-3-Clause: none copyleft.

MIT code in a project licensed under BSD-3-Clause: MIT has no copyleft.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause has no copyleft.

Source Disclosure

MIT: not required.
BSD-3-Clause: not required.

MIT code in a project licensed under BSD-3-Clause: MIT does not require you to publish source code.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause does not require you to publish source code.

Attribution

MIT: Include the copyright notice and permission notice in all copies or substantial portions.
BSD-3-Clause: Retain the copyright notice, conditions and disclaimer in source redistributions.
BSD-3-Clause: Reproduce the copyright notice, conditions and disclaimer in documentation or other materials for binary redistributions.

MIT code in a project licensed under BSD-3-Clause: MIT requires the copyright and licence notices to be kept with copies you distribute.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause requires the copyright and licence notices to be kept with copies you distribute. BSD-3-Clause prohibits using the copyright holder's or contributors' names to endorse or promote your product without permission.

Patent Considerations

Express patent licence: MIT: no; BSD-3-Clause: no.
Patent termination clause: MIT: no; BSD-3-Clause: no.

MIT code in a project licensed under BSD-3-Clause: MIT contains no express patent licence. Any patent permission would depend on implied licence doctrines, which vary by jurisdiction.
BSD-3-Clause code in a project licensed under MIT: BSD-3-Clause contains no express patent licence. Any patent permission would depend on implied licence doctrines, which vary by jurisdiction.

Common Scenarios

Scenario	MIT code in a project licensed under BSD-3-Clause	BSD-3-Clause code in a project licensed under MIT
Use as a dependency / library	Generally Compatible	Generally Compatible
Copy source code into the project	Generally Compatible	Generally Compatible
Modify the component	Generally Compatible	Generally Compatible
SaaS / network service (not distributed)	Generally Compatible	Generally Compatible
Internal / private use only	Generally Compatible	Generally Compatible
Resell the software	Generally Compatible	Generally Compatible
White-label / rebrand	Generally Compatible	Generally Compatible

FAQ

Can I use MIT code in a project licensed under BSD-3-Clause?

Using MIT-licensed code in a project under BSD-3-Clause is generally compatible in this scenario. MIT permits commercial use.

Can I use BSD-3-Clause code in a project licensed under MIT?

Using BSD-3-Clause-licensed code in a project under MIT is generally compatible in this scenario. BSD-3-Clause permits commercial use.

Can MIT-licensed code be used in closed-source commercial software?

Using MIT-licensed code in a proprietary project is generally compatible in this scenario. MIT generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

Can BSD-3-Clause-licensed code be used in closed-source commercial software?

Using BSD-3-Clause-licensed code in a proprietary project is generally compatible in this scenario. BSD-3-Clause generally allows the code to be included in proprietary software without releasing your source code, provided its notices are kept.

Do I have to publish my source code when I use MIT code?

MIT does not require you to publish source code.

Do I have to publish my source code when I use BSD-3-Clause code?

BSD-3-Clause does not require you to publish source code.

Can I use MIT code in a closed-source SaaS?

Can I use BSD-3-Clause code in a closed-source SaaS?

Try the Interactive Checker

Change the scenario, say whether the code is modified, distributed or offered as SaaS, and see every rule that applies.

Check MIT in a BSD-3-Clause project Check BSD-3-Clause in a MIT project

Related Comparisons

Authoritative Sources

This tool provides general software licensing information and is not legal advice. License obligations may depend on how software components are combined, modified, distributed and used. For high-risk results, review the actual license text before relying on this result.