Copyleft is a licensing method that permits people to use, copy, modify, and redistribute a work while requiring specified downstream distributions to preserve the same freedoms. It operates through copyright, rather than by abandoning copyright: permission to exercise rights otherwise reserved to the copyright holder is granted subject to conditions. Its best-known expression is the GNU General Public License (GPL), although copyleft also appears in licenses for documentation, photographs, educational materials, databases, and other cultural works.
The defining feature of copyleft is continuing reciprocity. A recipient may generally distribute an original or modified work, including commercially, but may not impose restrictions that defeat the freedoms protected by the applicable license. In software, this usually includes an obligation to provide corresponding source code when distributing executable versions. In cultural licensing, it more commonly takes the form of a requirement to license shared adaptations under the same or an expressly compatible license.
Copyleft is not a single legal instrument, and its effects depend on the license text, the activity being undertaken, and the applicable law. Different licenses draw different boundaries around the material subject to reciprocity. Understanding copyleft therefore requires distinguishing its underlying objective from the particular rules governing distribution, software combinations, network services, license compatibility, and enforcement.
Legal foundations and defining characteristics
Copyright ordinarily gives a rights holder control over activities such as reproduction, adaptation, and distribution, subject to statutory exceptions and limitations. Copyleft uses intellectual property licensing to authorize those activities in advance. A license may allow anyone receiving a copy to reproduce and modify it, while making permission to distribute a modified version conditional on preserving specified rights for subsequent recipients. The mechanism is consequently different from a prohibition on copying: copying is encouraged, but certain forms of restrictive redistribution are not authorized.
This structure distinguishes copyleft from the public domain. A public-domain work generally has no applicable copyright restrictions, although other rights may still affect its use. Someone adapting such a work may obtain copyright in sufficiently original additions and distribute those additions under restrictive terms. Copyleft seeks to prevent an equivalent restriction of covered adaptations. It also differs from a permissive software license, such as the MIT License, which generally allows incorporation into proprietary products provided that notice requirements are observed. Both approaches can grant broad permissions, but only copyleft makes continuing reciprocal licensing central to its design.
The license does not normally transfer ownership of the original work. Contributors may retain copyright in their respective contributions, while recipients receive nonexclusive permissions. In a collaborative project, a modified version can therefore contain material owned by many people. A distributor needs permission for all protected material being distributed, either through the applicable public licenses or through separate arrangements. Copyleft permissions do not erase the distinction between ownership and authorization, nor do they automatically grant rights in every associated trademark, patent, or item of confidential information.
The boundary between a license condition and a contractual promise can affect enforcement. Depending on the legal system and the wording involved, noncompliance may support copyright claims, claims under contract law, or both. Activities that do not require the rights holder’s permission remain a separate matter. A license cannot simply eliminate a statutory exception such as fair use by describing an activity as covered, although questions about independently enforceable contractual obligations can arise.
Copyleft is also narrower than a general obligation to share everything. It does not ordinarily require disclosure of unrelated works, publication of every private modification, or surrender of revenue. Its obligations attach to defined material and specified acts. The common description of copyleft as “viral” obscures this legal structure: a license cannot create copyright ownership over independent material merely because that material is nearby or used on the same computer.
Origins in software-sharing communities
Copyleft emerged from the practical problems of software collaboration. In early computing environments, researchers and users often exchanged source code so that programs could be studied, corrected, and adapted to local machines. These practices varied widely and did not constitute a universal absence of proprietary software. As software markets expanded, licensing restrictions and nondisclosure arrangements increasingly separated users from the code needed to maintain or alter their systems.
Richard Stallman announced the GNU Project in September 1983, with development beginning in 1984. Its objective was a complete Unix-compatible system whose users would have the freedom to run, study, modify, and share its software. The Free Software Foundation, established in 1985, became a major institutional supporter. In this context, “free” referred to users’ freedoms rather than a requirement that copies be supplied without payment. Source-code access was essential because meaningful study and modification of software usually require the form in which programmers work.
Stallman adopted the word “copyleft” from a phrase used by programmer Don Hopkins in correspondence in 1984: “Copyleft—all rights reversed.” The word plays on “copyright,” but the legal strategy does not literally reverse copyright law. It uses the copyright holder’s existing power to authorize copying on reciprocal terms. Earlier and contemporary experiments in software sharing supplied part of the background, but GNU made this technique systematic and closely connected it to an explicit account of software freedom.
Before a general GNU license existed, GNU programs used program-specific licenses. GPL version 1 appeared in 1989, followed by version 2 in 1991 and version 3 in 2007. The move to a general license made it easier to combine and redistribute software across projects under a common set of conditions. In 1992, the Linux kernel adopted GPL version 2, contributing to the development of widely used systems combining the kernel with GNU tools and other software. The kernel’s licensing is specifically GPL version 2, rather than an unrestricted election of any later GPL version.
The appearance of the open-source software movement in 1998 introduced a different framing of broadly overlapping licensing practices. Open-source definitions include both copyleft and permissive licenses; open source is not synonymous with either approach. The Free Software Foundation emphasizes user freedom, while open-source advocacy has often stressed development methods and practical benefits. Copyleft has been used within both communities, and disagreement over its desirability has not prevented substantial technical collaboration.
Distribution, source code, and compliance obligations
For traditional software copyleft, the principal trigger is distribution of copies rather than private execution or modification. Someone who modifies a GPL-covered program for personal use ordinarily has no duty under that license to publish the changes. Likewise, changes made and used within one legal organization generally do not become public merely because they exist. Transfers to separate entities, contractors, or customers require closer attention to the facts and the relevant license provisions; “internal use” is not a substitute for identifying who receives copies and under what arrangement.
When executable software is distributed, source-code obligations make the freedom to modify practically usable. Source code is not simply any textual representation of a program. GPL licenses describe it in relation to the preferred form for making modifications. Obfuscated code or an automatically generated intermediate file may therefore fail to satisfy the requirement where developers actually modify a different form. Under GPL version 3, corresponding source can include scripts needed to control compilation and installation, together with other material necessary to generate, install, run, and modify the covered work, subject to specified exclusions.
The permitted methods of delivering source vary with the license and distribution method. GPL version 2 permits several arrangements, including accompanying object code with complete corresponding source or, in specified circumstances, a written offer valid for at least three years. GPL version 3 provides more detailed alternatives for physical products, network downloads, and other situations. A distributor cannot assume that pointing to an upstream project’s homepage satisfies its own obligations: the supplied source must correspond to the distributed version, including relevant modifications.
Copyleft does not invariably require public posting on an unrestricted website. Some obligations run to recipients of executable copies; certain written-offer mechanisms extend availability more broadly. The applicable provision determines who is entitled to request source and for how long. Recipients who obtain the source can generally redistribute it themselves. A distributor may charge for software copies or services, but cannot use an additional confidentiality agreement to nullify the redistribution permissions granted for covered material.
Compliance also involves preserving copyright notices, license texts, warranty disclaimers, and specified modification notices. In practice, failures may arise from incomplete build materials, omitted license information, or source releases that do not match shipped binaries. A company selling a device containing modified GPL software remains responsible for its own distribution even when the software originated with a supplier. Supply-chain agreements can allocate tasks and financial responsibility between businesses, but do not by themselves replace the permissions and duties governing the recipients’ copies.
Strong, weak, and network copyleft
“Strong” and “weak” copyleft are comparative descriptions, not standardized statutory categories. Strong copyleft generally requires a covered combined or adapted program to be distributed under reciprocal terms as a whole. Weak copyleft confines reciprocity more narrowly, for example to particular files or libraries, while allowing some surrounding software to use different terms. The practical boundary depends on the license wording and on whether the material forms a protected adaptation or combined work under applicable copyright law.
The GPL is the principal example of strong software copyleft. It distinguishes a covered whole from a mere aggregation of independent works on the same storage or distribution medium. Placing an independent proprietary application and a GPL program on one installation image does not automatically bring both under the GPL. Conversely, dividing a single integrated program among several files does not necessarily make its components independent. Technical packaging is relevant evidence, but it is not a complete legal test.
The GNU Lesser General Public License (LGPL) was designed to permit broader use of covered libraries by applications under other licenses. Its conditions preserve access to the library’s covered code and, in specified combinations, the ability to modify or replace the library. Requirements may differ according to whether linking is dynamic or static and according to the LGPL version. The Mozilla Public License version 2.0 uses a file-level model: covered files remain subject to its source-disclosure requirements, while a larger work can include separate files under other terms.
Whether linking creates a derivative or otherwise covered work has been a persistent area of disagreement. Static linking ordinarily incorporates library code into a resulting executable; dynamic linking connects components during loading or execution. Those technical differences can matter, but there is no universally applicable rule that every dynamically linked program is independent or that every form of communication creates a combined work. The Free Software Foundation takes a relatively broad view of some combinations, while legal assessment remains dependent on the facts, the license, and the jurisdiction. Communication through a standard application programming interface does not, by itself, settle every copyright question.
Network copyleft addresses a different boundary. A provider may modify software and allow users to interact with it over the internet without giving them software copies. Ordinary GPL distribution requirements do not generally compel source disclosure solely because of that interaction. The GNU Affero General Public License version 3, published in 2007, adds a requirement that a modified program supporting remote network interaction prominently offer interacting users an opportunity to receive its corresponding source. This does not extend automatically to every independent service communicating with the program.
Patents, locked devices, and the GPL version 3
The GPL version 3 revision addressed circumstances in which access to code did not necessarily provide practical control over software. One prominent concern involved products that incorporated GPL-covered software but accepted only manufacturer-authorized versions. Users might receive source code and permission to modify it yet be unable to install a modified executable on the device they owned. This issue became known as “tivoization,” after discussions concerning digital video recorders made by TiVo. The term describes a technical and licensing problem rather than a separate legal doctrine.
GPL version 3 responds through installation-information requirements for certain distributions involving a “User Product.” This category includes specified consumer products and items designed or sold for incorporation into a dwelling. Where the relevant conditions apply, a distributor must provide information needed to install and execute modified versions of covered software, including necessary authorization keys or procedures. The obligation is not an unrestricted requirement to reveal every device secret. It is tied to installing modified versions, and the license contains qualifications, including circumstances in which neither the distributor nor a third party retains the ability to install modified object code.
The license also addresses technological protection measures. Copyright statutes in some jurisdictions restrict circumvention of access controls separately from infringement. GPL version 3 includes provisions intended to prevent a distributor from using those rules to obstruct the exercise of permissions granted by the license. Their significance depends on the applicable national law. The broader distinction is between legal permission to alter software and the technical or legal barriers that may prevent the altered software from being used.
Patents introduce another potential restriction. Copyright permission to copy a program does not automatically authorize every patented technique that the program implements. GPL version 3 contains an express patent license from contributors covering defined essential patent claims and includes rules concerning certain patent arrangements associated with conveying covered software. These provisions seek to prevent some recipients from receiving effective freedoms while others face discriminatory patent restrictions. They cannot guarantee freedom from claims by unrelated patent holders who have not granted permission.
The revision also clarified terminology, international operation, termination, and compatibility with some other licenses. “Conveying” identifies propagation that enables other parties to make or receive copies, helping distinguish distribution-like activity from mere remote use. These provisions illustrate why the version of a license matters. GPL version 3 does not retrospectively replace GPL version 2 for all software, and a project licensed only under version 2 cannot simply be treated as version 3 code without the necessary authorization.
License compatibility, exceptions, and relicensing
License compatibility concerns whether material under different licenses can be combined and distributed while satisfying all applicable conditions. Two licenses may each qualify as free or open-source licenses and still be incompatible for a particular combination. The issue is not a ranking of openness but a conflict of obligations. One license may demand a term that another forbids, or each may require the combined work to remain exclusively under its own conditions.
Compatibility is often directional. Permissively licensed material can frequently be incorporated into a GPL-covered program because the permissive license allows redistribution subject to retaining notices, while the resulting covered combination is distributed under the GPL. That does not mean the original permissive material loses its existing licensing, or that GPL-covered additions can generally be extracted and redistributed under the permissive license alone. The permissions for each contribution must be traced separately.
Version clauses have important consequences. A program offered under “GPL version 2 or any later version” allows recipients to choose a later published GPL version within that authorization. A program offered under GPL version 2 only does not. GPL-version-2-only code and GPL-version-3-only code generally cannot be combined into a single covered work under either license without additional permission. Similarly, the Apache License version 2.0 is compatible with GPL version 3 for relevant combinations, but not with GPL version 2 alone. Compatibility analysis must identify the exact licenses, not merely their families.
Copyright holders can issue exceptions that relax particular conditions. A linking exception may authorize specified combinations with otherwise incompatible or proprietary components. Such an exception is a grant of additional permission, not evidence that copyleft has ceased to exist for the remaining covered code. The copyright holder can also offer the same work under alternative licenses. In dual licensing, a customer may choose between a copyleft license and a separately negotiated proprietary license, often where the supplier controls sufficient rights to offer both.
Relicensing a collaborative work can be much harder. A maintainer’s authority to accept changes or publish releases is not necessarily authority to alter every contributor’s copyright license. Projects may rely on contributor agreements, copyright assignments, preauthorized later-version clauses, or individual permissions. A new license for future original material cannot automatically withdraw rights already granted in earlier copies. This persistence is central to copyleft’s institutional effects: an existing authorized version can remain available even if a project’s owner changes the terms for later development.
Copyleft in culture, documentation, and databases
Outside software, copyleft usually appears as a share-alike condition. Instead of requiring buildable source code, a license requires certain shared adaptations to remain available under the same or a compatible license. Creative Commons Attribution–ShareAlike, commonly abbreviated CC BY-SA, is a leading example. It permits commercial use and adaptation, subject to attribution and other conditions, while requiring shared adapted material to use an authorized adapter’s license.
The distinction between an adaptation and a collection is especially important for cultural works. Translating an essay normally creates an adaptation, while placing several independent essays in an anthology does not necessarily make each essay an adaptation of the others. A photograph reproduced unchanged within a larger publication does not automatically impose its share-alike license on the entire publication. The result depends on the nature of the incorporation, the license definitions, and the copyright law governing adaptations. Attribution obligations may apply even where share-alike obligations do not.
Creative Commons licenses containing a NonCommercial restriction should not be conflated with unrestricted free-culture licensing. They prohibit uses falling within that restriction, even if they also include ShareAlike. NoDerivatives licenses, which restrict sharing of adapted material, likewise do not implement copyleft’s characteristic permission to distribute adaptations under reciprocal terms. The presence of the Creative Commons name therefore does not by itself identify a work as copyleft; the particular license elements matter.
Documentation has its own history. The GNU Free Documentation License (GFDL), first released in 2000, was developed for manuals and other texts. It includes mechanisms concerning invariant sections and cover texts, which have generated debate about suitability for different kinds of collaboration. In 2009, Wikimedia projects carried out a major transition that enabled eligible text previously licensed under the GFDL to be offered under CC BY-SA 3.0, using a special relicensing provision in GFDL version 1.3. Wikipedia became a prominent large-scale example of reciprocal licensing for collaboratively written reference material.
Databases pose additional complications because protection can attach separately to original selection or arrangement and, in some jurisdictions, to database investment. The European Union recognizes a sui generis database right distinct from ordinary copyright. The Open Database License addresses database rights and contains share-alike provisions; OpenStreetMap adopted it in 2012. Its treatment of derivative databases and outputs produced from databases differs from the treatment of software executables under the GPL. Creative Commons version 4.0 licenses also address sui generis database rights, demonstrating that the relevant legal subject matter must be identified before reciprocity can be assessed.
Enforcement and judicial treatment
Copyleft enforcement usually concerns whether a distributor has satisfied conditions attached to permission to copy or distribute. A typical dispute begins with a product containing covered software but lacking the required source, notices, or licensing information. Copyright holders or authorized representatives may seek compliance, negotiate a resolution, or bring proceedings. The available legal remedies depend on the jurisdiction, the claims, and the facts; they can include an injunction, damages, or orders connected with contractual performance.
Standing is a central issue. The fact that someone receives copyleft software does not automatically make that person a copyright owner entitled to bring an infringement claim. Copyright holders ordinarily enforce their own exclusive rights, while recipients may have other possible claims under contract or consumer law. Whether a recipient can enforce a particular promise as a contractual beneficiary is a distinct question. Organizations assisting with enforcement may act for rights holders or support litigation without owning all copyright in the relevant project.
European decisions provided early public examples. In 2004, the Munich Regional Court granted relief in litigation brought by Linux developer Harald Welte against Sitecom over GPL noncompliance. In 2006, the Frankfurt Regional Court ruled in another Welte case involving D-Link, recognizing enforceability of the GPL conditions at issue. These decisions established important practical precedents in Germany, but did not create a universal ruling on every question about software combinations or every clause of every copyleft license.
In the United States, Jacobsen v. Katzer in 2008 was influential even though it concerned the Artistic License rather than the GPL. The Court of Appeals for the Federal Circuit held that open-source license conditions at issue could be enforceable as copyright conditions, not merely as contractual covenants. The decision recognized that public licensing can confer legally meaningful benefits despite the absence of a conventional per-copy payment. Its significance for copyleft is therefore part of the broader legal recognition of conditional public permissions, rather than a direct interpretation of GPL scope.
Termination and restoration provisions also shape enforcement. GPL version 2 states that unauthorized copying, modification, sublicensing, or distribution terminates the violator’s rights, while compliant downstream recipients retain their licenses. GPL version 3 adds mechanisms for provisional or permanent reinstatement after violations cease, subject to stated conditions and notice periods. These rules make correction legally significant without erasing the violation itself. Enforcement practice often focuses on obtaining complete corresponding source and preventing recurrence, but the preferences of particular organizations should not be mistaken for limitations imposed by the license or by law.
Economic organization and continuing controversies
Copyleft supports commercial activity while limiting particular forms of exclusivity. Businesses can charge for distribution, integration, hosting, support, warranties, customization, and hardware containing covered software. The license normally does not require revenue sharing with upstream contributors. What it restricts is the ability to distribute covered material while withholding the permissions and information that the license requires recipients to receive. Consequently, the distinction between commercial and noncommercial activity is different from the distinction between proprietary and copyleft licensing.
Reciprocity can alter incentives in collaborative production. A contributor may be more willing to invest in a shared codebase if competitors cannot distribute improved covered versions as exclusively proprietary software. At the same time, the obligation to disclose covered changes can deter organizations whose business model depends on exclusive distribution rights. Permissive-license advocates emphasize reduced barriers to adoption and incorporation, while copyleft advocates emphasize durable downstream freedoms and reciprocal access to improvements. Neither argument establishes one license as optimal for every project, and adoption statistics depend heavily on what repositories, packages, or products are counted.
Copyleft also affects bargaining power and project governance. If a company abandons a project or changes licensing for later releases, recipients may continue developing an authorized older version as a software fork. This possibility can limit dependence on a single supplier. It does not guarantee a successful alternative: development expertise, infrastructure, community participation, and trademark rights may remain concentrated elsewhere. Legal permission to continue a project is a necessary resource, not a replacement for the practical capacity to maintain it.
Hosted services expose a recurring disagreement about the appropriate reach of reciprocity. Ordinary software copyleft centers on recipients of distributed copies; network copyleft extends specified obligations to users interacting with modified software remotely. Some providers view this as necessary to preserve access to improvements in service-based computing, while others regard its boundaries as difficult to integrate with proprietary systems. Licenses that impose broader business restrictions, such as prohibitions on offering competing hosted services, must be assessed separately: availability of source code alone does not make a license free, open source, or copyleft in the established sense.
New technical contexts continue to test older categories. In machine learning, the relationships among training software, training material, model parameters, and generated outputs do not map neatly onto the familiar distinction between a program’s source and executable forms. Merely running a copyleft-covered training program does not generally place all resulting output under that program’s license; protected material incorporated into an output can raise a different issue. Likewise, a dataset’s reciprocal license does not by its label alone resolve whether trained parameters constitute an adaptation under applicable law. These questions require analysis of the licensed subject matter, the permissions actually needed, and the particular terms, rather than an assumption that copyleft automatically follows every causal use of a work.