About LICENSE File Generator

MIT, Apache 2.0, BSD 3-Clause, GPL 3.0, Unlicense — year + holder. Part of the DevTools Surf developer suite. Browse more tools in the Generators collection.

Use Cases

• Add a LICENSE file to a new open-source repo
• Update the year and copyright holder after a fork
• Compare license text when choosing between MIT and Apache
• Switch from MIT to Apache 2.0 when publishing a corporate release

Tips

• MIT is the most permissive — recommended for open-source libraries
• Apache 2.0 adds an explicit patent grant — good for corporate contributors
• GPL 3.0 requires derivative works to also be GPL (copyleft)

Fun Facts

• The MIT license has ~30% of all GitHub repos — by far the most popular open-source license.
• The 'BSD vs GPL' debate in the 1990s shaped the entire open-source movement. Linux chose GPL, while FreeBSD chose BSD — and Apple built macOS on top of FreeBSD's permissive code.
• The WTFPL (Do What The F*** You Want To Public License) is a real OSI-recognized license created by French programmer Sam Hocevar in 2004.

FAQ

Which licenses are included?

MIT, Apache 2.0, BSD 2-Clause, BSD 3-Clause, GPL v3, AGPL v3, LGPL v3, MPL 2.0, Unlicense, ISC. Covers 95% of open-source projects.

Does it set the year correctly?

Current year by default — adjust if you're creating a LICENSE for a project that started earlier. Copyright year should be the earliest year of substantial contribution.

How do I choose between MIT and Apache?

MIT for maximum simplicity. Apache 2.0 adds patent grants — crucial if your code could be patented. For libraries that ship binaries, Apache is safer.

What about dual licensing?

The tool generates one LICENSE file. For dual licensing, create a LICENSE section in README explaining the dual terms and put both licenses in separate files.