Open Source License Chooser
Answer 3 questions to find the right open-source license for your project — MIT, Apache 2.0, GPL 3.0, or BSD.
About this tool
Choosing an open-source license can feel like a legal maze — MIT? Apache? GPL? This tool asks 3 plain-language questions and recommends the right license for your project, with the full license text ready to copy into a LICENSE file.
The wizard covers the four most widely used open-source licenses: MIT (simple permissive), Apache 2.0 (permissive with patent grant), GPL 3.0 (strong copyleft), and BSD 3-Clause (permissive with no-endorsement clause). BSD 2-Clause is also included as an alternative.
Example: if you answer "derivatives can be proprietary" → "include patent protection" → the tool recommends Apache 2.0 and shows the full license text. If you change your mind after seeing the result, switch to any other license with one click.
FAQ
What is the difference between MIT and Apache 2.0? ›
Both are permissive, but Apache 2.0 adds an explicit patent grant from contributors and requires that modified files carry a notice of changes. MIT is shorter and simpler. If patent risk is a concern (e.g. larger projects, corporate adoption), prefer Apache 2.0.
Does GPL mean I cannot sell my software? ›
No — you can sell GPL-licensed software. The condition is that anyone who receives the software must also get the source code and the right to redistribute it. GPL restricts what recipients can do, not what you can charge.
Can I change the license of my project later? ›
Yes, but only for future versions. The old code remains under the old license, and you cannot revoke the license from copies already distributed. For permissive licenses like MIT this is straightforward; for GPL you generally need agreement from all contributors (or a CLA — Contributor License Agreement).
What if none of these licenses fit my needs? ›
These four cover the vast majority of open-source projects. If you need a weak copyleft (library that allows proprietary linking), consider LGPL. For network-service copyleft, consider AGPL. For a public-domain dedication, look at the Unlicense or CC0. This tool focuses on the most common choices.