Key features
- LICENSE file generation — Fill in the year and copyright holder in any of 16 license texts, then copy it or download it as a LICENSE file. Companion files such as Apache-2.0's NOTICE and LGPL-3.0's COPYING are created too.
- License wizard — Six questions — source disclosure scope, patent clause, copyright notice, GPL-2.0 compatibility and more — produce three candidates with reasons.
- SPDX file headers — Creates SPDX-License-Identifier and SPDX-FileCopyrightText lines in seven comment styles, and can add the official notices for GNU, Apache, MPL and Boost.
- Comparison table and compatibility checker — Compare all 16 licenses at a glance in a permissions/conditions/limitations matrix, and check whether code can go into a project under another license, with the conditions.
- License explanations and guides — Covers each license's obligations and common misconceptions, plus concepts such as copyleft, dual licensing and SPDX.
How to use
- Choose a license in the Generator tab. If you are not sure which one to choose, answer the questions in the 'License wizard' tab.
- Enter the year and copyright holder (a person or organization name). The project name is used in NOTICE and GNU notices.
- Check the preview on the right and click 'Download' to save the LICENSE file, then place it at the root of your repository.
- In the 'File header' tab, choose the comment style for your language and paste it at the top of each source file.
Frequently asked questions
What happens if I don't add a license?
Under copyright law the default is 'all rights reserved'. Even if the code is public, others have no right to copy, modify or distribute it, so it is not open source. For a public repository it is best to include a LICENSE file.
Which is better, MIT or Apache-2.0?
Both are permissive. MIT is short and simple, while Apache-2.0 has an express patent grant, a clause terminating that grant upon patent litigation, and rules on change notices and NOTICE files. Many choose Apache-2.0 when there are many corporate contributors or patents are a concern, and MIT for something lightweight. Offering both as 'MIT OR Apache-2.0' is also common.
If I use GPL code, do I always have to publish my code?
If you only use it internally without distributing, there is no obligation to publish. When you distribute a program combined with GPL code to others, you must provide the source of the whole under the GPL. Running it only on a server is not distribution under the GPL, but the AGPL requires source to be provided for modified versions.
What year should I write?
It is common to use the year of first publication, and ranges such as '2019-2026' are also used. There is no legal obligation to update the year every year.
Who should be listed as the copyright holder?
The individual who wrote the code, or, for code written as part of a job, usually the employer. When many people contribute, something like 'The Example Authors' is also used. Check your employer's policy.
Is the name I enter stored on a server?
No. The LICENSE text and headers are generated in your browser and your input is never sent to a server. For convenience on your next visit, it is kept only in this browser's local storage, and you can clear it at any time.
Can I change the license of code I have already released?
The copyright holder can apply a different license to future versions, but permissions already granted for released versions generally cannot be revoked. If other contributors' code is included, their consent (or a CLA) is needed.
Data sources and licenses
- License texts and the permissions/conditions/limitations classification: choosealicense.com (GitHub, Inc. and contributors, MIT License) —
_licensesdata in the github/choosealicense.com repository, as of the 2026-09-10 commit. - Text verification: SPDX License List 3.29 (released 2026-09-16, spdx.org/licenses). Identifiers follow the SPDX list.
- Compatibility verdicts: the compatibility matrix in the FSF 'Frequently Asked Questions about the GNU Licenses' and the text of each license.
- The license texts themselves are included under the terms each license sets (e.g. the GPL's 'verbatim copying and distribution permitted'). The texts have not been modified; only the [year] and [fullname] placeholders of MIT, BSD, ISC and 0BSD are replaced with your input.
choosealicense.com — Copyright (c) GitHub, Inc. and contributors
MIT License (see LICENSE.md in the repository for the full text)