Open Source License Generator (MIT, Apache, GPL, BSD)
Generate the canonical LICENSE file for your open source project. Fill in your name and year, pick a license, copy the text. Comparison panel explains the practical differences between the most-used licenses so you pick the right one.
Picking a license
| License | Permissive | Patent grant | Copyleft | Network use |
|---|---|---|---|---|
| MIT / ISC / BSD | Yes (very) | No (implicit) | No | — |
| Apache 2.0 | Yes | Explicit | No | — |
| MPL 2.0 | Partial | Explicit | File-level | — |
| LGPL 3.0 | — | Explicit | Library-level | — |
| GPL 3.0 | — | Explicit | Yes (whole-project) | — |
| AGPL 3.0 | — | Explicit | Yes | Yes (SaaS triggers) |
| Unlicense / CC0 | Public domain | — | No | — |
How to use the Open Source License Generator (MIT, Apache, GPL, BSD)
Fill in the form, copy the output, save as LICENSE (no extension) in your project root. Most package managers and GitHub's license detection pick up the file automatically.
Choosing and generating a license
Every open-source project needs a LICENSE file, and the choice carries weight: permissive licenses (MIT, ISC, BSD) let anyone reuse the code with little more than attribution, copyleft licenses (the GPL family) require derivative works to stay open, and the AGPL extends that obligation to software offered over a network. Omitting the file entirely leaves your terms ambiguous and the code effectively all-rights-reserved.
This fills the canonical text of eleven common licenses with your name and year for you to copy or download as a ready LICENSE file, alongside a comparison of permissiveness, patent grants, and copyleft scope so the decision is informed. It sits with the other project-setup tools — the .gitignore generator for a starter ignore file, the conventional commit builder for commit messages, and the package.json validator for your manifest.
Common use cases
- Start a repo — drop a correct LICENSE into a new project.
- Compare licenses — weigh permissive against copyleft at a glance.
- Add a patent grant — pick Apache 2.0 for explicit patent terms.
- Network copyleft — choose AGPL so SaaS use triggers source sharing.
- Public domain — use Unlicense or CC0 to waive rights.