This open source license generator produces the full text of any of 15 common software licenses with your name and year pre-filled. Use the comparison table to choose the right license for your project, then download a ready-to-use LICENSE file.
License Settings
License Comparison
License Text
How to Choose and Generate an Open Source License
Choosing a software license is one of the most consequential decisions for an open-source project. It determines who can use your code, whether they can include it in commercial products, and whether derivative works must also be open source. This license generator makes it easy to produce the exact text you need.
Step 1: Choose the Right License Type
Permissive licenses (MIT, Apache 2.0, BSD, ISC) let anyone use your code for any purpose, including proprietary software, with minimal requirements. MIT is the most popular choice for open-source libraries. Apache 2.0 adds a patent clause, making it preferred by larger organizations. If you want maximum adoption, use MIT or Apache 2.0.
Copyleft licenses (GPL 3.0, AGPL 3.0) require anyone who distributes modified versions to also open-source their changes under the same license. This prevents large companies from taking your code and keeping improvements private. AGPL extends this to network use — if you run GPL code as a service, you must release the source. Use GPL if you want to ensure your code always remains open.
Weak copyleft (LGPL, MPL 2.0) is a middle ground. LGPL is designed for libraries — programs can link to your LGPL library without becoming LGPL themselves, but modifications to the library itself must stay LGPL. MPL 2.0 applies copyleft at the file level — modified files must stay open, but unmodified files can be combined with proprietary code.
Step 2: Fill in Your Details
Enter your full name or organization name in the Author field. The year is pre-filled with the current year — update this if you're retroactively licensing older work. Adding a project name is optional but helps when the license refers to the specific software.
Step 3: Download and Add to Your Repository
Download the LICENSE file (no extension) for GitHub compatibility — GitHub will automatically detect and display the license badge when you use this filename. Place it in your repository root. For projects that also serve documentation, download LICENSE.md for a rendered Markdown version. Add a brief copyright notice at the top of each source file referencing the LICENSE file.
Creative Commons vs Software Licenses
Creative Commons licenses (CC BY, CC BY-SA, CC0) are designed for creative works — documentation, artwork, datasets, written content. They are not recommended for software code, where GPL/MIT are better established. CC0 is an exception — it is commonly used for small code snippets, reference implementations, and public domain dedications where you want truly no restrictions. Use CC licenses for non-code assets and software licenses for code.
FAQ
Is this license generator free?
Yes, completely free with no account required. All generation runs locally in your browser — nothing is sent to a server.
Which licenses does it support?
The generator supports 15 common licenses: MIT, Apache 2.0, GPL 3.0, BSD 2-Clause, BSD 3-Clause, ISC, MPL 2.0, Unlicense, CC BY 4.0, CC BY-SA 4.0, CC0, WTFPL, AGPL 3.0, LGPL 3.0, and Artistic License 2.0.
What is the difference between MIT and Apache 2.0?
Both are permissive licenses that allow commercial use, modification, and distribution. Apache 2.0 adds an explicit patent grant — if you contribute code, you implicitly grant patent rights to users. MIT has no patent clause. For most projects, both work the same way. Apache 2.0 is preferred by larger projects where patent risk matters.
What is the difference between GPL and LGPL?
GPL (copyleft) requires any software that uses your code to also be GPL-licensed (viral). LGPL is 'Lesser GPL' — software can link to LGPL libraries without adopting the GPL license. LGPL is designed for libraries, GPL for standalone applications.
Do I need to put the license in every source file?
Best practice is to include a full LICENSE file in your repository root, then optionally add a short copyright header in each source file. Tools like git hooks can verify headers. For most open-source projects, a single LICENSE file in the root is sufficient.
Can I use the generated license for commercial projects?
Yes. Generate any permissive license (MIT, Apache, BSD, ISC) and use it for commercial or proprietary projects. Copyleft licenses (GPL, AGPL) have restrictions on how derivative works can be distributed.
What does CC0 mean?
CC0 (Creative Commons Zero) is a public domain dedication. You waive all copyright and related rights, making your work as close to 'no copyright' as legally possible. It is commonly used for datasets, reference implementations, and content you want anyone to use with no restrictions whatsoever.