Skip to main content
License encyclopedia

License comparison

BSD-2-Clause vs BSD-3-Clause: endorsement

The two BSD versions share the same source and binary notice duties: retain the copyright notice, conditions and disclaimer in source, and reproduce them in materials provided with binaries. BSD-3-Clause adds the restriction on using copyright holder or contributor names to endorse a derived product without permission. BSD-2-Clause omits that clause; it does not remove the shared notice duties.

Compare the permissions, limits and obligations recorded in each guide. Read the license text for the full conditions that apply to your release.

Permissions

BSD-2-Clause

  • Commercial use

    You may ship the code inside a paid product. The license does not restrict commercial use.

  • Modify

    You may change the code, including keeping those changes private, unless a later obligation says otherwise.

  • Distribute

    You may give copies to others. Distribution is what usually turns notice and source duties into real work.

  • Sublicense

    You may include the code under your own product terms, so long as you still meet this license's conditions.

  • Private use

    Use inside your company, including internal forks, does not by itself trigger distribution duties.

BSD-3-Clause

  • Commercial use

    You may ship the code inside a paid product. The license does not restrict commercial use.

  • Modify

    You may change the code, including keeping those changes private, unless a later obligation says otherwise.

  • Distribute

    You may give copies to others. Distribution is what usually turns notice and source duties into real work.

  • Sublicense

    You may include the code under your own product terms, so long as you still meet this license's conditions.

  • Private use

    Use inside your company, including internal forks, does not by itself trigger distribution duties.

Limits

BSD-2-Clause

  • Hold liable

    The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.

  • Use trademark

    The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.

  • Patent grant

    The text does not grant patents. If buyers want an express patent grant, Apache-2.0 is the usual alternative.

BSD-3-Clause

  • Hold liable

    The authors disclaim warranty. Recipients cannot hold them liable for damages arising from the software, except where law forbids that disclaimer.

  • Use trademark

    The license is not a trademark license. Names, logos and product marks stay with their owners unless a separate grant says otherwise.

  • Patent grant

    The text does not grant patents. If buyers want an express patent grant, Apache-2.0 is the usual alternative.

  • Endorse with names

    You may not use the names of the University, the authors, or contributors to endorse derived products without prior written permission.

Obligations

BSD-2-Clause

  • Include copyright

    Keep the copyright line with every copy or substantial portion you distribute.

  • Include license

    Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.

  • Binary materials

    BSD-2-Clause has the same source and binary notice pair as BSD-3-Clause, without a non-endorsement clause. Source keeps the list of conditions. Binaries keep that text in accompanying materials.

BSD-3-Clause

  • Include copyright

    Keep the copyright line with every copy or substantial portion you distribute.

  • Include license

    Keep the license text with every copy or substantial portion you distribute. A web page is not a substitute for notices inside a shipped artifact.

  • Binary materials

    For a binary, reproduce the copyright, the conditions, and the disclaimer in the documentation or other materials that accompany it, not only in the source tree.

License texts

Practical guidance for procurement review, not legal advice. Confirm high-stakes use with counsel.

Cookies on sourcetrust.dev

We use essential cookies for security, including abuse prevention on our site scan and walkthrough request form. With your permission, we also use optional analytics and diagnostics (Google Tag Manager on this site, and the Sentry browser SDK on the SourceTrust application when configured). See our cookie policy.