License Picker
Quiz (8 questions with live recommendations), Browse (30+ licenses: MIT, Apache 2.0, GPL family, MPL, BSL, Elastic, CC variants, ODbL, Unlicense), Compare (side-by-side or compatibility matrix), generator with placeholders and downloadable LICENSE / LICENSE.md.
Quiz
Answer the questions below — recommendations update after every choice. You can skip any question.
Answered 0 of 8
1What kind of work are you licensing?
This narrows the legal regime — software vs. CC for creative work.
2Allow commercial use?
Most open-source licenses allow it. Pick 'no' for non-commercial only.
3Can users modify and redistribute?
Drives whether you end up with a permissive, copyleft, or proprietary path.
4Must derivative works be shared back?
This determines copyleft strength.
5Require credit (attribution)?
Most licenses require keeping the original notices.
6Need an explicit patent grant?
Recommended for enterprise / corporate contributions.
7Protect your name / trademark?
Forbids contributors from using your brand to endorse derivatives.
8Provide a warranty?
Almost everyone ships 'AS IS' — saying yes is unusual.
Recommendation so far
Your top matches based on the answers given.
Frequently asked questions
Quick answers to the most common license questions.
What does "copyleft" mean?
Copyleft licenses require that derivative works be distributed under the same (or compatible) license. Strong copyleft (GPL) covers the whole combined work; weak copyleft (LGPL, MPL) typically covers only the modified files; network copyleft (AGPL) extends the rules to software offered over a network.
Can I change the license later?
Yes for new versions, but you cannot retroactively change the license of versions you've already published — those remain available under the original terms forever. To relicense significantly, you may need agreement from every contributor (or a CLA in place that allows it).
Do I need to register my license?
No. Copyright applies automatically in nearly every country. Just include a LICENSE file at the root of your repository and a short notice near the top of source files. Some projects also use SPDX-License-Identifier headers.
What's the difference between permissive and copyleft?
Permissive licenses (MIT, Apache 2.0, BSD) allow downstream users to redistribute under almost any terms — including closed-source. Copyleft licenses (GPL, MPL) require that downstream distributions stay under the same license.
Do I need a Contributor License Agreement (CLA)?
Optional. A CLA gives the project owner clear rights to relicense or sublicense contributions, which is useful if you may want to dual-license later or want stronger legal cover. Many large projects (Apache, Google) require one; many smaller projects don't.
What if I don't include a license?
Default copyright applies — no one else has any rights to use, modify or distribute your code. "No license" is effectively the most restrictive option, even if the source is public.
Can I dual-license?
Yes. Many projects offer a copyleft license (e.g. AGPL) for free and a commercial license for users who want different terms. You need to own (or have CLAs covering) the rights to do this.