About the License Generator
License Generator writes the LICENSE file for your open-source project. Pick one of the short, permissive licences, MIT, BSD 2-Clause, BSD 3-Clause, ISC, Zero-Clause BSD or the Unlicense, type your name or company and the year, and the page shows the full standard text with your copyright line filled in. Copy it or download it as a file called LICENSE and put it in the root of your repository. A one-line description of each licence and its SPDX identifier helps you choose, and a note explains where to get the longer Apache 2.0 and GPL texts.
Updated October 2026
How to use the License Generator
- 1Choose a licence from the list and read its one-line summary.
- 2Type the copyright holder: your name or your company.
- 3Type the year, or a range such as 2024-2026.
- 4Check the licence text.
- 5Copy it or download the LICENSE file and add it to the root of your project.
Permissive licences in a nutshell
The licences here are permissive: anyone may use your code in any project, including commercial ones, as long as they keep your copyright notice. They are short, easy to understand and compatible with almost everything, which is why most popular libraries use them.
Choosing between them
If you are unsure, use MIT. Pick another when you have a reason.
- MIT: the default choice, short and clear
- BSD 2-Clause: same effect, different wording
- BSD 3-Clause: also forbids using your name for promotion
- ISC: shorter wording, popular in the Node.js world
- Zero-Clause BSD or Unlicense: no strings attached
After you add the file
Commit the LICENSE file and mention the licence in your README and package manifest. GitHub then shows the licence on the project page. If someone else wrote code in your project, check that their licence is compatible with the one you choose.
Related tools
Create your ignore list with the .gitignore Generator, compare versions with the Diff Checker and write a Privacy Policy Generator document for apps and sites. The Hash Generator can fingerprint release files.
Features
- MIT, BSD 2 and 3-Clause, ISC, 0BSD and Unlicense
- Your name and year filled in
- Short plain summary of each licence
- SPDX identifier shown
- Copy and download
- Private: nothing is uploaded
Frequently asked questions
Why does my project need a licence?
Without a licence, the law says nobody may use, copy or change your code, even if it is on GitHub. A licence tells others what they may do.
Which licence should I choose?
MIT is the most popular and the simplest. BSD and ISC are almost the same in effect. Choose Apache 2.0 if you want an explicit patent grant, or the GPL if you want changes to stay open, and copy those texts from their official sites.
What is the difference between MIT and BSD?
They are very close. BSD 3-Clause adds a rule that nobody may use your name to promote their product. MIT is shorter.
What is the Unlicense?
A way to place your code in the public domain. Some countries do not recognise a public-domain dedication, so a permissive licence such as MIT or 0BSD is often safer.
What do I put as the copyright holder?
Your legal name or the name of your company. If many people contribute, many projects use the name of the project or a group, such as The Project Authors.
Do I need to update the year?
The year of first publication is enough in most places. Some projects use a range to show ongoing work.
Where should the file go?
In the root of the repository, called LICENSE or LICENSE.md. Also name the licence in your package file, for example the license field in package.json.
Is this legal advice?
No. These are the standard texts, but choose carefully if your project is commercial and consult a lawyer for a big decision.