{
  "id": "gnu-general-public-license",
  "title": "GNU General Public License",
  "lang": "en",
  "source_lang": "en",
  "summary": "The GNU General Public License is a free software license that preserves users’ rights to run, study, modify, and redistribute software through copyleft conditions.",
  "category": "society",
  "subcategory": "law",
  "type": "work",
  "aliases": [
    "GNU GPL",
    "GPL",
    "General Public License"
  ],
  "generated_at": "2026-11-03",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/gnu-general-public-license/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/gnu-general-public-license/",
      "json": "https://aiwiki.page/zh/gnu-general-public-license.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "The GNU General Public License (GNU GPL, or GPL) is a family of widely used free software licenses published by the Free Software Foundation (FSF). It permits recipients to run, study, modify, and redistribute software, including commercially, while requiring covered redistributions to preserve those freedoms. Its defining mechanism is copyleft: permission to distribute covered software and modified versions is conditional on providing the corresponding source code and passing on the applicable license rights.\n\nThe GPL operates through copyright, rather than by placing software in the public domain. Copyright holders retain ownership of their contributions but grant broad permissions subject to stated conditions. The license is central to the GNU Project and is used by numerous independent projects, including the Linux kernel, which is distributed under version 2 with a specific system-call clarification.\n\nThree principal versions appeared in 1989, 1991, and 2007. Their differences affect compatibility, patent provisions, source-code delivery, and software installed in consumer products. Understanding the GPL therefore requires distinguishing the general principle of reciprocal licensing from the exact obligations of the version chosen for a particular work."
    },
    {
      "heading": "Software freedom and the copyleft mechanism",
      "text": "The GPL is designed around the free software movement’s distinction between freedom and price. “Free software” refers to users’ permissions, not to whether a copy costs money. These permissions encompass running a program for any purpose, studying how it works, adapting it, redistributing copies, and distributing modified versions. Access to source code—the form of a program preferred for making changes—is necessary for meaningful study and modification. An executable alone may allow a program to run without providing a practical means to understand or alter it.\n\nCopyleft uses the exclusive rights granted by copyright to preserve these permissions downstream. A copyright holder can authorize copying, modification, and redistribution on specified terms. Under the GPL, a distributor who passes on a covered program must preserve the required notices, provide the applicable license, and satisfy the relevant source-code requirements. When a modified work falls within the license’s coverage, it must be licensed as a whole under the applicable GPL terms. Recipients consequently obtain rights directly from the relevant licensors rather than merely receiving whatever permissions an intermediary chooses to offer.\n\nThis arrangement distinguishes the GPL from permissive software licenses, such as the MIT and BSD licenses. Permissive licenses generally allow covered code to be incorporated into proprietary products, subject to comparatively limited requirements such as retaining notices. GPL copyleft instead prevents a distributor from taking covered code, distributing a covered modified work, and denying recipients the freedoms required by the license. It does not, however, eliminate authorship, copyright ownership, or all differences between upstream and downstream projects.\n\nThe GPL does not require every modification to be published. A person may modify a program and use it privately without releasing the changes. Use within an organization also does not ordinarily create a general obligation to publish source code, although transfers to separate legal entities and particular outsourcing arrangements require closer analysis. If covered copies are distributed to customers, the relevant obligations run to those recipients; the license does not invariably require a public website containing the source.\n\nCommercial activity is expressly compatible with this model. Copies, support contracts, customization, training, and warranties can be sold. Recipients nevertheless retain their own redistribution rights, so a distributor cannot use the GPL to guarantee exclusive control over further copying. The license also prohibits additional restrictions that conflict with its grants. For example, an agreement forbidding recipients from redistributing covered software would not become permissible simply because the distributor had supplied source code."
    },
    {
      "heading": "Origins and the development of successive versions",
      "text": "The GPL arose from the GNU Project, announced by Richard Stallman in September 1983 to develop a complete Unix-compatible operating system composed of free software. The Free Software Foundation was established in 1985 to support that work. Before a general license existed, GNU programs used program-specific copying permissions, including licenses associated with GNU Emacs and the GNU C Compiler. A common license made it easier to share code among programs and explain a consistent set of rights and obligations.\n\nVersion 1 of the GNU GPL was published in February 1989. Its principal concerns included the distribution of executable software without usable source code and the imposition of restrictions that would deprive downstream recipients of freedoms supplied by the original author. Rather than relying only on statements of intention, it attached conditions to activities controlled by copyright. This gave the free software model a reusable legal instrument applicable to works beyond the original GNU programs.\n\nVersion 2 followed in June 1991. One of its most consequential provisions was section 7, which addresses circumstances in which other obligations conflict with the GPL. If a distributor cannot satisfy both the GPL and an incompatible obligation, the license does not authorize distribution under reduced freedoms. The section specifically discusses patent-related restrictions, but its structure is broader. GPLv2 remained highly influential because major projects adopted it and because changing a project’s license can require permissions from numerous copyright holders.\n\nThe preparation of version 3 involved an extended public consultation process. A first discussion draft was released in January 2006, and the final text appeared on 29 June 2007. The FSF developed the text with legal assistance and published successive drafts for comment. The revision addressed concerns that had become more prominent since 1991: software patents, technical measures that prevented installation of modified software, international differences in copyright terminology, and compatibility with other free software licenses.\n\nNew GPL versions do not automatically replace earlier ones in every project. A licensing notice may specify “version 2 only,” “version 2 or any later version,” or another authorized formulation. An “or later” grant allows a recipient to choose a later FSF-published version under the terms of that grant; a version-specific grant does not supply that choice. The Linux kernel’s GPLv2-only licensing is therefore materially different from the GPLv3-or-later licensing used by many GNU packages.\n\nVersion history consequently remains an operational issue, not merely a chronology. A project can contain files with different version permissions, exceptions, or additional licenses. Determining how those files may be combined requires examining their actual notices rather than assuming that every reference to “GPL” denotes an interchangeable set of terms."
    },
    {
      "heading": "Legal structure, covered works, and distribution boundaries",
      "text": "The GPL grants permissions that would otherwise be restricted by copyright, notably copying, modifying, and distributing protected expression. It is therefore different from a rule governing all uses of a computer program. GPLv2 states that activities other than copying, distribution, and modification are outside its scope and that running a program is not restricted. GPLv3 similarly affirms permission to run an unmodified program and provides broad permissions for making and running covered works without conveying them.\n\nGPLv3 distinguishes “propagation” from “conveying.” Propagation broadly concerns acts that would require copyright permission, apart from specified exclusions. Conveying is propagation that enables other parties to make or receive copies. This vocabulary helps separate copying and distribution from remote interaction. Merely interacting with users through a computer network, without transferring a copy, is not conveying under GPLv3. Running modified GPL software on a server therefore does not, by itself, create a general duty to provide its source to the service’s users.\n\nThe boundary of a covered modified work is especially important. Copyright protects expression, not every idea, interface, or functional relationship. Whether a combination constitutes a derivative work can depend on the applicable law and the technical facts. The GPL does not make every independent program that communicates with GPL software subject to copyleft. It also expressly distinguishes an aggregate—a collection of separate and independent works distributed together—from a larger covered work.\n\nLinking raises difficult boundary questions because it combines software components in different ways. Static linking ordinarily incorporates library code into an executable; dynamic linking connects components through mechanisms used when programs load or run. The FSF interprets many linked combinations as single covered works, but that interpretation is not a universal judicial determination for every architecture or jurisdiction. Separate processes communicating through ordinary protocols present a different factual setting from components deliberately designed to operate as one program through intimate internal interfaces.\n\nOutput is another distinct issue. A program’s output is covered by the GPL only when its content itself constitutes a covered work. Compiling an independently written program with a GPL-licensed compiler does not, merely because of that use, make the resulting application GPL-licensed. Runtime code, templates, or other material copied into output can require separate analysis; some tools carry explicit exceptions for this reason.\n\nThe GPL also preserves rights that exist independently of its permissions. Applicable exceptions and limitations, including fair use where recognized, are not abolished by the license. Conversely, GPL permission does not automatically provide rights under unrelated trademark rules, third-party patents, or other bodies of intellectual property law."
    },
    {
      "heading": "Source-code delivery and redistribution obligations",
      "text": "Source-code availability is the practical foundation of GPL copyleft. Supplying an executable while withholding the material needed to modify it would leave recipients with only part of the promised freedom. The required material is not simply any human-readable text associated with the program. GPLv2 refers to the preferred form for making modifications and includes relevant interface definition files and scripts used to control compilation and installation. GPLv3 defines “Corresponding Source” in greater detail.\n\nCorresponding Source under GPLv3 includes the source needed to generate, install, run, and modify the object code, together with scripts controlling those activities. It does not normally include general-purpose tools or generally available free programs used unmodified in the process when they are not part of the work. System-library exclusions also limit what must accompany an application. These distinctions prevent the source obligation from expanding into a requirement to supply an entire operating environment in every case, while preserving the materials necessary for the covered work itself.\n\nDifferent distribution methods have different compliance paths. Under GPLv2, a distributor may accompany object code with complete corresponding machine-readable source or, under the relevant provision, provide a qualifying written offer valid for at least three years. That offer must be available to any third party and may charge no more than the cost of physically performing source distribution. GPLv2 also contains a narrower option for certain noncommercial redistributions that pass along an offer received with the program.\n\nGPLv3 sets out several alternatives adapted to physical products, network downloads, and other transfer methods. A qualifying offer accompanying object code in a physical product must remain valid for at least three years and for as long as the distributor offers spare parts or customer support for that product model. For object code downloaded from a designated place, equivalent access to Corresponding Source must be offered through the same place in the manner specified by the license, without an additional source-access charge. The exact requirements cannot safely be reduced to a single rule that all GPL distributions need only provide an upstream link.\n\nNotices are also substantive obligations. Required copyright notices and warranty disclaimers must be preserved, recipients must receive the applicable license, and modified versions must carry the change notices required by the relevant version. Merely stating that a product “contains open source” does not fulfill these conditions. The source supplied must correspond to the distributed binary, including relevant modifications, rather than to a similar upstream release.\n\nThese requirements make release management part of license compliance. Manufacturers distributing embedded software may need to retain build scripts, patches, and source archives for particular firmware versions. Purchasing a component from a supplier does not by itself transfer away the manufacturer’s own obligations when it redistributes covered copies."
    },
    {
      "heading": "GPLv3: installation information, patents, and technical restrictions",
      "text": "GPLv3 addressed a gap between access to source code and the practical ability to use modified software. A device can contain GPL software and provide its source while using cryptographic checks to refuse altered versions. This practice became known as “tivoization,” after discussions surrounding TiVo recording devices. GPLv2 did not contain GPLv3’s explicit requirement to provide installation information for specified products, making this a significant difference between the versions.\n\nUnder GPLv3, certain conveyances of object code in, with, or specifically for use in a “User Product” must be accompanied by the installation information necessary to install and execute modified versions. User Products include consumer products and items designed or sold for incorporation into dwellings. The required information may include procedures, authorization keys, or other material needed to overcome restrictions on installing modified covered software.\n\nThis requirement is qualified rather than universal. It applies under the conditions specified in section 6, including the relevant transfer of possession and use of the product. Installation information is not required if neither the distributor nor any third party retains the ability to install modified object code, as with software fixed in read-only memory. The license also does not require continued warranty, support, or updates for a recipient’s modified version. These limits distinguish freedom to install modifications from an obligation to maintain every altered device.\n\nGPLv3 separately addresses technological protection measures and anti-circumvention law. Section 3 provides that a covered work is not to be treated as part of an effective technological measure under the specified legal frameworks, and it limits reliance on anti-circumvention powers to prevent exercises of GPL-granted rights. This is a licensing commitment by the relevant parties, not a general repeal of anti-circumvention legislation.\n\nThe patent provisions are also more explicit than those of GPLv2. GPLv3 contains a contributor patent license covering essential patent claims for the contributor’s version. Its additional rules address knowing reliance on patent licenses and arrangements that give some recipients patent protection while leaving others exposed. The purpose is to prevent patent arrangements from undermining the permissions that the copyright license gives to recipients. The provisions do not amount to a guarantee against all patent claims by unrelated parties.\n\nFinally, GPLv3 reorganizes several aspects of the earlier text: it provides more detailed treatment of additional terms, clearer international terminology, compatibility mechanisms for particular license combinations, and opportunities to cure certain violations. Its practical effect must therefore be assessed provision by provision. A program’s move from GPLv2 to GPLv3 changes more than its version label, and recipients cannot make that move unless the existing grants authorize it."
    },
    {
      "heading": "License compatibility, exceptions, and relicensing",
      "text": "License compatibility concerns whether code under different licenses can be combined and distributed while satisfying all applicable conditions. It is not simply a measure of how similar two licenses sound. Two licenses may both permit commercial use and require source availability yet impose conflicting obligations. Conversely, code under a permissive license can often be included in a GPL-covered combination because its original conditions, such as preserving notices, can be satisfied alongside the GPL.\n\nCompatibility is frequently directional. For example, code under the two-clause or three-clause BSD licenses can generally be incorporated into GPL-covered works, but this does not give a recipient permission to remove the GPL from other code in the resulting work. The permissively licensed component retains its original licensing history. The combined distribution must satisfy the terms applicable to the whole covered combination as well as surviving conditions attached to its components.\n\nThe Apache License version 2.0 illustrates the importance of GPL versions. It is compatible with GPLv3, but not with GPLv2-only, because of differences involving requirements including patent-related provisions. An Apache-2.0 component can therefore be used in an appropriately GPLv3-licensed combination, whereas a GPLv2-only grant does not supply the permissions needed for the same result. If relevant GPLv2 code is licensed “or later,” selecting GPLv3 may resolve that particular incompatibility.\n\nGPLv2-only and GPLv3-only code likewise cannot ordinarily be combined into a single derivative work merely because both licenses belong to the GPL family. Version-selection clauses may provide a route to a common license, but only where the copyright holders granted that option. A project’s preferred policy cannot override a narrower grant in a contributed file.\n\nExceptions can authorize combinations that the unmodified GPL would not permit. A copyright holder might allow linking with specified proprietary libraries or grant an exception for runtime material incorporated into compiler output. The GNU Compiler Collection’s Runtime Library Exception is an important example of a carefully defined permission associated with GPLv3-covered code. Such exceptions must be read according to their actual scope; an exception attached to one component does not automatically apply to every component in a product.\n\nRelicensing depends on control of copyright. A sole copyright owner can offer the same code under several licenses or issue future versions on different terms. A project with many contributors may need additional permissions unless contributor agreements or existing grants already authorize the proposed change. Earlier copies remain usable under licenses validly granted for them. Dual licensing—offering a GPL option alongside a separate commercial license—therefore relies on having sufficient rights in the code, not on a general power to withdraw recipients’ existing GPL freedoms."
    },
    {
      "heading": "Related licenses and alternative reciprocity models",
      "text": "The GPL is one member of a broader group of licenses developed to address different relationships between software components and users. These related licenses are not interchangeable abbreviations for the same legal instrument. Their differences determine whether obligations apply to a complete combined program, a particular library, or software accessed over a network.\n\nThe GNU Lesser General Public License (LGPL), originally called the GNU Library General Public License, provides a more limited form of copyleft suited to libraries. Under its conditions, non-GPL applications can use a covered library without the entire application becoming GPL-licensed. Modifications to the library remain subject to the applicable copyleft requirements, and recipients must retain the required ability to modify or replace the library in the combined arrangement. The details differ between LGPL versions. LGPLv3 is structured as additional permissions supplementing GPLv3 rather than as an entirely independent replacement text.\n\nThe GNU Affero General Public License version 3 (AGPLv3) addresses modified software used to provide network services. Ordinary GPLv3 does not generally require source disclosure merely because users interact remotely with a server. AGPLv3 adds a requirement that, when a modified program supports remote network interaction, the modified version must prominently offer interacting users an opportunity to receive its Corresponding Source. This targets a situation in which users benefit from, and depend on, a modified program without ever receiving its executable.\n\nGPLv3 and AGPLv3 contain provisions allowing their covered works to be linked or combined under specified conditions. These provisions preserve the distinct application of the two licenses, including the AGPL’s network-interaction requirement for the combination. They do not simply convert every GPL program into AGPL software. As elsewhere, the permissions granted by the actual copyright holders remain decisive.\n\nOther licenses use narrower reciprocity boundaries. The Mozilla Public License 2.0 generally applies its source-sharing requirements at the file level and includes mechanisms relevant to compatibility with certain secondary licenses. Permissive licenses take another approach by allowing proprietary redistribution of modified code while preserving limited conditions. These alternatives reflect different choices about the boundary between shared infrastructure and separately controlled additions.\n\nThe GNU Free Documentation License is aimed at manuals and other documentation, not primarily at executable software. It has provisions, including possible invariant sections and cover texts, that differ substantially from software-license obligations. Likewise, Creative Commons licenses are widely used for cultural and educational works but are not generally designed to handle software-specific issues such as corresponding source and linking.\n\nA single software project may consequently use different licenses for program code, manuals, artwork, and examples. Calling the entire package “GPL software” can obscure those distinctions. The license attached to each relevant work determines its permissions, and a software license does not automatically govern every accompanying asset."
    },
    {
      "heading": "Enforcement, termination, and judicial treatment",
      "text": "GPL enforcement ordinarily concerns whether a distributor has permission to undertake acts reserved to copyright holders. If a distributor fails to satisfy applicable license conditions, its copying or distribution may no longer be authorized. A claimant must still establish the relevant rights, conduct, and legal basis under the law of the forum. The GPL is not a worldwide statute, and its interpretation interacts with national copyright law, procedural rules, and sometimes contract law.\n\nEnforcement commonly begins with investigation and requests for compliance rather than litigation. Typical issues include missing source code, incomplete build materials, absent license notices, and source that does not match the distributed binary. The copyright holders involved may seek cessation of noncompliant distribution, delivery of required materials, or other remedies. Organizations such as the FSF and Software Freedom Conservancy have undertaken compliance and enforcement work for software in which they hold rights or represent relevant developers.\n\nA significant early decision came from the Munich Regional Court in 2004 in proceedings involving Harald Welte, netfilter/iptables software, and Sitecom. The court upheld GPL-related conditions in granting relief over noncompliant distribution. The case became important evidence that free software licensing conditions could be judicially enforced rather than treated merely as informal community expectations. It did not settle every question about GPL scope or create a uniform rule for other jurisdictions.\n\nIn the United States, Jacobsen v. Katzer, decided by the Court of Appeals for the Federal Circuit in 2008, was influential in distinguishing enforceable copyright-license conditions from obligations that might support only contract claims. The license at issue was the Artistic License, not the GPL. Its relevance to GPL discussions lies in its treatment of open-source conditions and the economic interests supported by attribution and reciprocal collaboration, rather than in any direct adjudication of GPL text.\n\nGPLv2 and GPLv3 differ in their termination provisions. GPLv2 provides for automatic termination when a licensee copies, modifies, sublicenses, or distributes outside its permissions, while protecting compliant downstream recipients from losing their rights merely because an upstream party violated the license. GPLv3 adds express reinstatement mechanisms. These include provisional reinstatement after violations cease and permanent reinstatement under specified notice and cure conditions, including a first-notice opportunity to cure within 30 days.\n\nRemedies can include an injunction or damages, depending on the claim and jurisdiction, but the GPL’s source-sharing goal is not identical to maximizing monetary recovery. Whether a particular clause is a copyright condition, a contractual promise, or both can affect available remedies. Third-party-beneficiary theories and questions about who can demand performance are separate legal issues; the fact that someone possesses GPL software does not automatically establish every possible enforcement claim."
    },
    {
      "heading": "Adoption, project governance, and commercial use",
      "text": "The GPL became a major institutional framework for collaborative software development through GNU tools, the Linux kernel, and many applications. It provides a standardized legal basis on which unrelated contributors and organizations can exchange improvements without negotiating a separate redistribution agreement for every recipient. Its significance lies not only in the number of licensed files but also in the role of GPL-covered components within operating systems, development environments, and embedded devices.\n\nLinux illustrates both the reach and the limits of GPL licensing. The kernel is licensed under GPLv2, with licensing details and exceptions expressed in its source tree. A Linux-based operating system, however, includes many independent components under different licenses. Distributing a GPL kernel does not make every application on the system GPL-covered merely because the application uses normal system calls. Conversely, modifications to covered kernel code raise obligations that cannot be avoided by describing the whole product as a mixed-license system.\n\nThe WordPress project provides another prominent application-level example, with its core software distributed under GPLv2 or later. GNU compiler and development tools supply a different model: shared technical infrastructure used to build software that may itself have many different licenses. These examples show why adoption must be considered together with technical boundaries and any applicable exceptions, rather than treated as a single uniform business arrangement.\n\nCommercial models around GPL software include paid development, support subscriptions, hosted services, training, and distribution of hardware containing covered software. None inherently conflicts with the license. Because recipients may redistribute covered copies, businesses often charge for reliability, integration, maintenance, or access to services rather than relying solely on exclusive permission to copy a program. A separately negotiated commercial license can also be offered where the licensor controls the necessary rights, but GPL recipients retain the rights granted under their chosen GPL license.\n\nProject governance remains distinct from licensing. The GPL does not determine who becomes a maintainer, which patches are accepted, how releases are scheduled, or who controls a project’s name. It allows recipients to create a fork subject to the applicable obligations, but it does not guarantee that a fork will receive infrastructure, recognition, or upstream cooperation. Trademark rules may also require a modified distribution to adopt different branding even when copyright permissions allow redistribution.\n\nModern supply chains make these distinctions operationally important. A consumer device may contain a GPL kernel, LGPL libraries, permissively licensed utilities, and proprietary applications supplied by several vendors. Software inventories and a software bill of materials can help identify components and versions, but an inventory alone does not fulfill source-code or notice obligations. Compliance depends on the exact licenses, the relationships among components, and what copies are actually conveyed to recipients."
    }
  ],
  "links": [
    "copyleft",
    "copyright",
    "public-domain",
    "gnu-project",
    "source-code",
    "fair-use",
    "trademark",
    "intellectual-property",
    "legislation",
    "patent",
    "apache-license",
    "gnu-affero-general-public-license",
    "gnu-free-documentation-license",
    "creative-commons",
    "contract-law",
    "injunction",
    "damages",
    "software-fork"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}