A software licence (sometimes spelled software license in United States English) is a legal instrument that sets the terms under which a particular piece of software may be used, copied, modified or shared. A licence is selected or drafted by the software developer or by a software publisher, and users normally must accept its terms—by clicking to agree, by opening packaged media, or by other means—before they may lawfully use the program. Licences clarify basic questions such as whether commercial use is permitted, whether the source code must be disclosed, and whether recipients may redistribute or change the program.

Core characteristics and common clauses

Despite wide variation in wording and scope, most software licences include a set of familiar elements. These provisions translate legal rights and restrictions into practical rules for users, contributors and distributors.

  • Grant of rights: the licence states what the licensee is allowed to do (run, copy, modify, distribute).
  • Scope: whether the licence applies to source code, binary builds, documentation or other assets.
  • Restrictions: prohibitions on reverse engineering, redistribution, commercial use, or certain fields of use.
  • Attribution and notices: requirements to preserve copyright notices and include licence text.
  • Patent and trademark clauses: sometimes licences include patent grants or patent retaliation terms.
  • Disclaimer of warranty and limitation of liability: common clauses that limit the author’s responsibility for defects.
  • Termination and redistribution rules: conditions under which rights end and how downstream recipients are treated.

Types of licences and well-known examples

Licences are commonly grouped by how permissive or restrictive they are. At one extreme are proprietary or closed licences that reserve nearly all rights to the owner; at the other extreme are free and open licences that grant broad reuse rights.

  • Proprietary / closed: these licences restrict copying, modification and redistribution; a common model for commercial software and some consumer products (proprietary software).
  • Permissive open licences: allow reuse with minimal obligations. The MIT License is a short, permissive licence that requires only attribution.
  • Copyleft / reciprocal licences: require that derivative works be released under the same terms. The GNU General Public License (often called the GPL) is the best-known copyleft licence and aims to preserve software freedom in downstream copies.
  • Corporate-friendly open licences: the Apache License is widely used by companies and projects that want an explicit patent grant and clear contributor terms; major technology firms such as Google and others often choose it for their projects.
  • Content licences: for non-software works, licences like Creative Commons offer a range of permissions and obligations for text, images and media.

These categories overlap with the idea of free software and open-source software, which place emphasis on user freedoms and collaborative development rather than on a specific legal text alone.

History and context

The modern landscape of software licences developed alongside the commercialization of computing and the rise of collaborative software communities. In the late twentieth century some authors and organisations asserted the right to share and modify code as a matter of principle; in response, a range of licences emerged to implement different policy goals—from preserving universal sharing to enabling commercial ecosystems. Over time, licence choice has become a strategic decision for projects, companies and institutions.

Practical issues: compliance, compatibility and enforcement

Accepting and complying with a licence is a legal obligation. Common practical concerns include how a licence is presented (clickwrap, shrinkwrap or browsewrap), how obligations travel with redistributed binaries versus source, and how licence terms interact when code from several licences is combined. Licence compatibility is especially important: some copyleft licences impose conditions that prevent combining code with incompatible licences, which affects distribution and productization strategies.

  • Compliance steps typically include auditing dependencies, retaining notices and attribution, and documenting licence choices for users.
  • Enforcement occurs through copyright and sometimes patent law; many disputes are resolved by negotiation, though litigation has occurred in high-profile cases.
  • Developers and organisations often use dual licensing, contributor license agreements, or explicit patent grants to manage rights and obligations.

Choosing a licence and final notes

Selecting a licence depends on objectives: whether a project aims for wide reuse, strict reciprocity, commercial exploitation, or a mix of those goals. Authors should read candidate licences carefully and, when in doubt, consult legal counsel or community guidance. For accessible introductions and official texts, readers can follow links to general resources on the meaning of licence types and to materials describing specific licences and terms. Understanding licence terms helps both creators and users navigate rights, responsibilities and the long-term viability of software ecosystems.