What Is License Compatibility Checker?
License Compatibility Checker is a free online tool by TechnSols that checks whether two open source licenses can be combined in one project. You pick the license of a library you want to use and the license of your own project, and the tool gives a verdict: Compatible, Conditional, or Incompatible, with the reason and the license the combined work must carry. Nothing is uploaded, and the check runs in your browser.
Mixing licenses is the quiet risk in open source. A permissive library can join almost any project, but a copyleft library can force the whole project to change its license, and an Apache library cannot join a GPL 2.0 project at all. The FSF license list explains the rules the checker follows: which licenses are compatible, which are not, and which need conditions such as keeping notices or sharing source.
The checker holds a bundled matrix of the common licenses: MIT, Apache 2.0, BSD 2-Clause, BSD 3-Clause, ISC, MPL 2.0, LGPL 3.0, GPL 2.0, GPL 3.0, AGPL 3.0, and the Unlicense. Pick any two and the verdict appears with the obligations, such as keeping the copyright notice or releasing the combined work under the stronger license. If the verdict is Incompatible, the License File Generator tool can generate the replacement license once you pick a different one.
People use it before they add a dependency, before they release a project, and before they accept a contribution under a different license. It is general guidance, not legal advice: it follows the widely published compatibility rules, but it cannot read your contracts, your jurisdiction, or how the code is actually combined.
How To Use License Compatibility Checker?
Here is how to check license compatibility online in three quick steps. Using License Compatibility Checker is simple. There is no software to install and no account to make. Pick two licenses and read the verdict. If the project has no license yet, the License File Generator tool writes the LICENSE file once you choose one.
Step 1: Pick The Library License
Choose the license of the code you want to use, such as MIT, Apache 2.0, or GPL 3.0. This is the license on the library, the snippet, or the dependency you are adding to your project. The list holds the common open source licenses, each with a short note on what it requires.
Step 2: Pick Your Project License
Choose the license of your own project, the license the combined work would carry. If your project has no license yet, pick the one you plan to use, or pick Proprietary when the project is closed source. The checker reads the pair from its bundled matrix.
Step 3: Read The Verdict And Obligations
Read the verdict: Compatible means the two can be combined, Conditional means they can be combined only with stated conditions, and Incompatible means they cannot. The result also lists the obligations, such as keeping notices or sharing source. If the pair is Incompatible, the README Generator tool can update the README once the license changes.
The whole job takes a minute. A check before you add a dependency beats a license problem after the release, and the check never leaves your browser.
Why License Compatibility Checker?
A license is a permission slip, and two permission slips can disagree. MIT asks only for a notice, so it fits almost anywhere. GPL asks for the source of the whole combined work, so it fits only where the project accepts that. The checker makes those rules visible before you commit to a dependency, when changing course still costs nothing. If the project needs a license file at all, the License File Generator tool writes it.
The matrix follows the published positions of the Free Software Foundation and the Open Source Initiative. The OSI license list lists the approved licenses the checker covers, with the full text of each one. Because the verdicts come from those published rules, they match what a license review would say for the common pairs.
Permissive Licenses Fit Almost Anywhere
MIT, ISC, BSD, and the Unlicense ask so little that they can join a permissive project, a copyleft project, or a closed source product. The only obligation is usually keeping the copyright notice. That freedom is why permissive licenses are the safe default for libraries.
Copyleft Licenses Set The Terms
GPL and AGPL require the combined work to carry the same license, so adding a GPL library to an MIT project turns the whole project into GPL. The checker shows that result plainly, so the trade is clear before you add the dependency.
Apache And GPL 2.0 Do Not Mix
Apache 2.0 adds patent terms that GPL 2.0 treats as an extra restriction, so the pair is incompatible. The classic fix is GPL 3.0, which was written to accept Apache 2.0. The checker flags the conflict and names the fix.
What Can You Do With License Compatibility Checker?
License checks fit any project that uses other people’s code. These are the jobs this checker handles best.
Check A Dependency Before You Add It
Before you add a library, check its license against your project license. A Compatible verdict means you can add it now, and an Incompatible one means you pick a different library or a different license. The Changelog Generator tool records the dependency in the release notes.
Audit The Licenses In A Project
A project with many dependencies can hide a conflict. Check each license against the project license in turn, and the conflicts stand out. That audit is the cheapest license review a project can get, and it takes minutes.
Choose A License For A New Project
A new project with no license yet can test the licenses of the code it already uses. Pick the project license that stays compatible with all of them, and the release starts clean. The API Documentation Builder tool builds the API docs for the newly licensed project.
Quality And Settings
The checker covers eleven licenses plus Proprietary, with a verdict for every pair: Compatible, Conditional, or Incompatible. Each verdict names the license the combined work must carry and lists the obligations, such as keeping notices, sharing source, or offering source to network users. The Text to PDF tool turns a written summary of the verdict into a PDF to share.
- Eleven open source licenses plus Proprietary, in one matrix.
- Verdicts: Compatible, Conditional, or Incompatible.
- Each verdict names the license for the combined work.
- Obligations listed: notices, source sharing, patent terms.
- The Apache 2.0 and GPL 2.0 conflict is flagged with its fix.
There are no settings beyond the two licenses, because the verdict comes from the matrix itself. Check every pair you plan to combine, and re-check when a dependency changes its license.
How License Compatibility Checker Works
The checker looks up the pair in a bundled matrix built from the published FSF and OSI positions. The matrix is directional: the library license is the code you use, and the project license is the license of the combined work. A permissive library into a copyleft project is Compatible, while a copyleft library into a permissive project is Incompatible. The Word Counter tool counts the words in a license note while you write it.
Two limits are worth knowing. The checker gives general guidance from published rules, and it is not legal advice: it cannot read your contracts, your jurisdiction, or how the code is actually combined, linked, or distributed. For a commercial product with real exposure, have a lawyer review the choice before you commit it.
Privacy
Everything you pick stays in your browser. The check runs on your own computer, and nothing you enter is uploaded to a server, stored, or shared with anyone. Closing the tab clears the selection, so the licenses you checked never leave your device.
Because no account is needed, there is no name, email, or history tied to what you check. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make License Compatibility Checker work smoother, whether you are checking one pair or a whole project.
- Check the dependency before you write code against it.
- Keep the copyright notices of every permissive library you use.
- Re-check when a dependency changes its license in an update.
- Treat AGPL as GPL plus a network rule, not as plain GPL.
- Ask a lawyer before a commercial release with copyleft code.
When the verdict is Compatible, note the obligations in the README so the next contributor sees them. The Character Counter tool counts the characters in a license note while you keep it short.
More Tools For The Same Job
These tools handle the same kinds of jobs: picking, writing, and explaining the licenses a project carries.
- License File Generator: writes the LICENSE file once you have picked a license.
- README Generator: writes the README that states the license you picked.
- Gitignore Generator: writes the .gitignore that keeps build files out of the licensed code.
- Changelog Generator: writes the release notes that record a license change.
- API Documentation Builder: builds API docs for a project whose license is now clear.
- Code Comment Generator: writes comment blocks, including the license header for a file.
- Markdown Documentation Editor: edits the docs that explain the license choice.
- OpenAPI Documentation Previewer: previews the API docs of a licensed project.
- Word Counter: counts the words in a license note while you write it.
- Case Converter: changes the case of headings in a license notice.
FAQ
Common questions about checking license compatibility, answered plainly.
Is License Compatibility Checker by TechnSols Free?
Yes, License Compatibility Checker by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can use it as often as you like, and everything you type stays in your browser, so nothing is uploaded or stored anywhere.
Is This Tool Legal Advice?
No, this tool gives general guidance from the published compatibility rules of the Free Software Foundation and the Open Source Initiative, and it is not legal advice. It cannot read your contracts, your jurisdiction, or how the code is actually combined. For a commercial product with real exposure, have a lawyer review the choice before you commit it.
What Does Conditional Mean?
Conditional means the two licenses can be combined only when you meet stated conditions. The common conditions are keeping the copyright notice, sharing the source of the combined work, or offering source to network users for AGPL code. Read the obligations in the result, because the verdict alone does not tell you what you must do.
Why Is Apache 2.0 Incompatible With GPL 2.0?
Apache 2.0 adds patent termination terms that GPL 2.0 treats as an additional restriction, which GPL 2.0 does not allow. GPL 3.0 was written to accept those terms, so Apache 2.0 and GPL 3.0 are compatible. The checker flags the GPL 2.0 conflict and names GPL 3.0 as the fix.
Can I Use GPL Code In A Closed Source Project?
No, GPL code requires the combined work to be distributed under GPL, with the source available, so it cannot stay closed source. A closed source project can use permissive libraries such as MIT, BSD, and Apache 2.0, which only ask you to keep the notice. Check the pair here before you add the dependency.
Pick the two licenses, read the verdict, and follow the obligations. A compatible project is a project anyone can legally use, and that is the whole point of sharing code.