BSD licence: history, characteristics, variants and usage

Key characteristics

• Permissive: Allows reuse in open and closed-source projects with few obligations.
• Attribution: Requires preservation of copyright notices and licence text in redistributions.
• Warranty disclaimer: Commonly disclaims liability and warranty.
• Compatibility: Often compatible with other licences, including permissive and copyleft licences in many cases.

History and origin

The licence family traces back to the University of California, Berkeley, where the BSD operating system was developed. Early BSD releases included a licence with an advertising clause that later proved controversial. Over time the wording evolved to remove that clause and to produce simpler variants. The project’s origins at University of California, Berkeley are why the name persists, and because the work was created in the United States, the U.S. spelling “license” is frequently used alongside other regional spellings.

Common variants and use

The main recognised variants are the original four-clause BSD licence, the three-clause (or "modified") BSD licence, and the two-clause (or "simplified"/"FreeBSD") licence. Each removes or relaxes conditions from the previous; the two-clause is the briefest and most permissive. BSD licences are widely used for operating systems, libraries, and academic code because they simplify commercial adoption and redistribution.

Distinctions and notable facts

BSD licences differ markedly from copyleft licences like the GPL: they do not require derived works to carry the same licence. That distinction affects project strategy—teams seeking broad adoption often choose BSD-style terms, while those prioritising reciprocal openness prefer copyleft. As with any licence, implementers should read the exact text or consult legal counsel when specific rights and obligations are at issue.