BSD 3-Clause "New" or "Revised" License, explained
Permissive BSD-3-Clause · BSD-2-Clause
BSD-3-Clause is a permissive licence: use the code anywhere, closed source included, keep the notice, and do not use the authors' names to promote your product. BSD-2-Clause is the same without the last condition.
Not legal advice. Read the licence text for the exact terms.
What it allows
- Use the code commercially and in closed-source products
- Modify and redistribute it
What it requires
- Keep the copyright notice, conditions and disclaimer in source copies
- Reproduce them in the documentation of binary distributions
- BSD-3-Clause only: do not use the names of the authors to endorse your product without permission
When it matters
| Shipping an app (desktop, mobile, on-premises) | Allowed, closed source included. Include the licence text and copyright notice, usually in a third-party notices file or an "About" screen. |
|---|---|
| A hosted service (SaaS) | Allowed. Nothing to publish; the notice requirement applies when you distribute the code, and JavaScript sent to browsers counts, so keep notices in your bundles. |
| Internal use | Allowed, with no conditions to meet while the code stays inside your organisation. |
Its family: permissive
You can use, change and ship the code in any product, including closed-source ones. You must keep the copyright and licence notice (usually in a third-party notices file); Apache-2.0 also asks you to state changes and keep its NOTICE file.
Questions
Is BSD-3-Clause compatible with GPL?
Yes, BSD-3-Clause and BSD-2-Clause code can be included in GPL projects.
Other licences
Related free tools
Dependency licence check
Upload a lockfile and see every dependency's licence. GPL, AGPL, unknown and changed licences are flagged for your kind of project. Free.
SBOM summary generator
Upload a lockfile and get an SBOM summary by email: components, licences, vulnerabilities and AI components. CycloneDX and SPDX files with Pro.
Published ; awaiting review.