Skip to content
BENIBIX Learn

MIT License vs GNU GPL

The MIT License and the GNU GPL are both open source licenses, but they differ on what you must give back to others. MIT lets you do almost anything, even put the code in a closed app, if you keep the notice. The GPL says that if you share a changed version, you must share its code under the GPL too. MIT is free to take; the GPL keeps code open.

Development🚀 Product & Releases

MIT License

A short open source license. You may do almost anything if you keep the notice.

The MIT License is a short open source license with very few rules. You may use it, change it, sell it and put it in closed apps. The one rule is to keep the copyright and license notice with the code. It also says the code comes with no warranty. It is one of the most used licenses, and React and Node.js use it.

Example
Jack puts the MIT License on his small date library. A big company uses it in a paid app, which is fine as long as his notice stays in.
Why it matters
It is simple and lets anyone use your code. That makes it easy for others to pick up.
Full entry
Development🚀 Product & Releases

GNU General Public License (GPL)

An open source license. Changes you share must stay open source too.

The GNU GPL is an open source license that keeps code open after others change it. You may use, change and share the code. But if you share a changed version, you must share its code under the GPL too. This rule is called copyleft. Linux uses version 2, and the newest is version 3, from 2007.

Example
Lucy builds an app on a GPL library and starts selling copies. Because she gives the app to others, she must also offer them its source code under the GPL.
Why it matters
It stops companies from taking open code, changing it and closing it off. Everyone keeps the right to see the code.
Full entry

In one line

MIT License
A short open source license. You may do almost anything if you keep the notice.
GNU General Public License (GPL)
An open source license. Changes you share must stay open source too.