Apache 2.0 grants you a perpetual, worldwide, royalty‑free patent license from every contributor as soon as code is submitted. The license covers only the claims that your use of the contributed work necessarily infringes, excluding unrelated patents. The grant stays effective until you file an infringement lawsuit or violate the license. It shields you from patent suits by contributors and mandates that you preserve the original copyright and NOTICE files. You will uncover further details below.

Key Takeaways

• Perpetual, worldwide, royalty‑free patent license automatically granted to any contributor’s patents covering the submitted code.
• Grant applies only to claims infringed by the contribution or its combination with the project’s code; unrelated patents are excluded.
• Grant remains until the licensee files a patent infringement lawsuit, after which it terminates for that party but protects downstream recipients.
• Apache 2.0’s patent‑defense clause obliges contributors to defend the licensee against claims they file, as long as the grant is active.
• Third‑party patents fall outside the grant; users must obtain separate clearance, though defensive patent networks can extend coverage beyond the license’s grant.

What Is the Apache License Patent Grant?

The Apache License Patent Grant is a specific legal mechanism embedded within the Apache License 2.0 that confers a perpetual, worldwide, non‑exclusive, no‑charge, royalty‑free patent license to every user of the software. You’re granted this patent license when you integrate code that a contributor submits to an Apache‑licensed project. The license activates upon contribution and revokes under termination provisions, without a separate agreement. Its scope is narrow: only patent claims the contributor owns and that are necessarily infringed by your contribution or by combining it with the project’s code. The original phrase “Each Contributor hereby grants…” appears in Section 3, embodying the history of the Apache Software Foundation’s 2004 decision to include a rebuttal clause. This legal phrasing balances openness with patent‑litigation risk, ensuring you may make, use, and distribute the software without royalty payments. These rights apply only to patents licensed by the developer, not to every claim. Each contribution comes with a patent grant that protects users from litigation.

Which Rights Are Covered by the Apache License Patent Grant?

A contributor grants you a perpetual, worldwide, non‑exclusive, royalty‑free patent license when you incorporate their contribution into the Apache‑licensed work. The License Scope covers rights to make, have made, use, offer to sell, sell, import, and transfer the Work, and extends to combinations of your contribution with the Work as submitted. These Use Rights are irrevocable except under the patent retaliation clause, which terminates the grant if you initiate litigation against the software. You may sublicense the granted rights, thereby extending protection downstream, but the grant remains limited to patents licensable by the contributor and to claims infringed solely by the contribution. The rights are royalty‑free and enforce non‑charge terms. The license also covers all patents belonging to the contributor that are necessarily infringed by the contribution. See the table below:

Which Patents Are Covered by the Apache License Patent Grant?

Because you submit code under the Apache License, the contributor grants you a perpetual, worldwide, royalty‑free patent license limited to claims that are infringed solely by the contribution or by the contribution combined with the Work. The scope is strictly narrowed by Scope Filters, which exclude any patents not directly tied to the code you provide. Only patents owned or controlled by the contributor, and directly infringed by the Contribution alone—or by its combination with the Work—are eligible for the grant. The clause also defines a Claim Trigger: any patent claim that is infringed by implementing the contribution in any manner within the licensed software activates the license automatically upon submission. Unrelated patents, such as those pertaining to unrelated subsystems, are expressly excluded. Consequently, the grant covers those claims you hold that are activated by your contribution under the Claim Trigger, ensuring end‑users get protection for that portion. If a licensee files a lawsuit alleging contributory infringement, the patent grant is automatically terminated as of the filing date.

Do Third‑Party Patents Fall Under the Apache License Patent Grant?

Following our earlier examination of the scope filters that limit the patent grant to claims tied to a contributor’s contribution, we must now determine whether patents held by third parties fall within the licence.

Reexamine if third‑party patents are encompassed by the contributor‑specific grant.

• Scope Clarification: the grant extends to claims tied to a contributor’s contribution, excluding third‑party patents not owned or controlled by the contributor.
• Exclusion Rules: a contributor cannot license patents held by external entities, so those patents remain completely outside the Apache 2.0 licence’s scope entirely forever.
• Section 1 clauses reinforce that only “claims licensable by such Contributor” may be granted, ensuring that third‑party patents are explicitly not inadvertently covered.
• Licence language requires the contributor to possess ownership, making any claim owned by an outsider ineligible for protection under the licence.
• Patent clearance must be sought separately; users note that the lack of an implied licence underscores the need for patent clearance.

You stay vigilant, always.

How Does Apache License Grant Protect Users From Suits?

Since the Apache 2.0 License’s Patent Grant confers a irrevocable license on every patent claim that a Contributor can license and that its contribution necessarily infringes, you receive a definitive defense against any claim a Contributor might bring for patent infringement related to that contribution. You thereby mitigate litigation risk by limiting indemnity to only those claims directly tied to your contributed code. In risk assessment, you identify patent scope, the contributor’s ownership, and the intended use of the work; this narrowing prevents broad, undifferentiated suits. Case studies from the Android and OpenStack projects illustrate how the grant blocked aggressive patent claims from aftermarket developers, preserving downstream confidence. The statutory “defensive termination” clause further protects you—any litigation by a contributor terminates the aggressor’s rights instantly while safeguarding downstream users. Consequently, your build and distribution processes remain unimpeded, and you can focus on innovation rather than defending against patent ambush.

Indeed, 90%+ of commercial firms now rely heavily on open-source software.

When Does the Apache License Grant Terminate Due to Litigation?

Even though the grant offers a durable shield against rogue patent claims, this protection evaporates if you initiate litigation.

The patent licence covers only patents that are essential contribution patents, and not the contributor’s broader portfolio.

• The filing of a suit claiming direct or contributory infringement constitutes the Termination Trigger.
• All patent licenses granted under the Apache License 2.0 for that Work terminate automatically upon filing.
• The effect applies only to the licensee who initiates litigation, not downstream users.
• Termination does not affect unrelated patents or broader portfolios, only those tied to contributed code.
• The Litigation Effect extends to withdrawals of sovereign, royalty‑free rights regardless of the lawsuit’s target within the project.

Consequently if you file such litigation, you forfeit the license’s patent grant, including all royalty‑free, irrevocable rights, and lose protection against contributor claims. This automatic cessation does not require any notice; it triggers immediately upon filing. Downstream users retain their rights, because termination is limited to the only initiating party’s licenses, preserving community trust.

How Can You Verify the Apache Grant on a Project?

How can you confirm that a project truly carries an Apache‑licensed patent grant? First, inspect the top‑level LICENSE file; it must contain the unaltered Apache 2.0 text, including Section 3’s patent clause. A license‑scanning tool—such as FOSSology or SPDX‑identifier parsing—will flag any deviation from the standard wording. Next, examine the NOTICE file; its presence and lack of removal of canonical patent attributions signal continuity of the grant. Follow with CLA verification: verify that every contributor’s ICLA or corporate CLA is recorded in the public registry, and cross‑reference commit history to confirm all code lines originate from licensed contributors. Check the repository’s branch protection rules and audit the Git blame history for attribution consistency. Finally, run a third‑party scanner like Black Duck to confirm that no custom patent language has been inserted. The Apache License contains an explicit patent grant for all contributions. If every audit step passes, you have legal confidence that the Apache grant applies for all its distributed artifacts.

How Does the Grant Compare to MIT and GPLv3?

• Classifies patents explicitly under Apache 2.0
• MIT relies on implicit patent allowance
• GPLv3 syncs Apache grant with copyleft
• Apache terminates upon patent litigation
• GPLv3 mandates source disclosure

Apache 2.0 also requires users to include a NOTICE file that outlines any modifications.

What Actions Must Developers Take to Preserve the Grant?

After reviewing how the Apache licence’s patent grant contrasts with the implicit allowance in MIT and the copyleft‑embodied grant in GPL v3, you’ll need to take concrete steps to preserve that grant. You must keep the original copyright notice in every distribution and attach a full copy of Apache License 2.0. Your NOTICE file should track attribution details, ensuring Notice Tracking across all codebases. Each modified file must contain a prominent change‑notice, a requirement some developers call a minor hassle. In every altered source file, you must document significant changes with a Change Logging statement. These requirements prevent license termination. You must also avoid patent litigation or counterclaims that could trigger termination of the granted rights in releases. When redistributing, provide either source or object forms with all required notices, describe modifications, and if you use a different license, sublicense the patent rights to downstream recipients. Persisting with these measures preserves the perpetual, worldwide, royalty‑free grant granted by contributors and protects downstream users for downstream recipients.

How Do Defensive Networks Complement the Apache Grant?

Because defensive aggregators such as LOT and OIN pool patents from member contributors, they give you a licensing mechanism that extends beyond the Apache 2.0 grant. You can then rely on their shared immunity model and network synergy to counter external claims against your software cooperatively. The aggregation covers non‑contributor patents, providing a wider broad shield that the original grant omits securely. When litigation arises, the network’s termination clause mirrors Apache’s, enabling coordinated retaliation. Your compliance process therefore benefits from both individual contributor rights and a collective defense that deters aggressors.

Defensive aggregators like LOT and OIN extend Apache 2.0 with shared immunity, non‑contributor patent coverage, and coordinated retaliation.

Using a shared tools and libraries approach reduces development time and enhances collaboration across the community.

• License coverage extends to non‑contributor third‑party patents, filling Apache’s gaps.
• Termination rights synchronize with Apache’s, allowing simultaneous claim egress for all members globally.
• Shared immunity triggers when any member files suit, effectively protecting all affiliates.
• Network synergy furnishes prior‑art documentation to rebut infringement allegations, enhancing defense.
• Compliance monitoring pairs with defensive pools, reducing audit burdens and litigation exposure.

Frequently Asked Questions

Can I Redistribute Code With Another License Under Apache 2.0 With the Patent Grant?

Yes, you’ll redistribute code under a different license, provided the new license is compatible with Apache 2.0 and respects dual licensing terms.

However, you’ll need to preserve the Apache 2.0 copyright notice and maintain the original patent grant for your contribution.

The patent license travels with the redistributed work, so downstream recipients inherit it regardless of the new license chosen.

Ensure you comply, and your redistribution remains compliant with license.

Does the Apache Patent Grant Apply to Derivative Works Built in Other Programming Languages?

Picture you as a cartographer forging new maps from existing trails; each ridge you translate into another language is a passage, not a new creation. The Apache 2.0 patent grant follows the contributions you port, regardless of language translation or the porting overhead it imposes. Consequently, your derivative work in Rust retains the grant’s royalty‑free license for the elements, while any changes you’ll make must be noted per the license.

What Obligations Exist if I Sell a Proprietary Product Containing Apache‑Licensed Components?

You must provide notice that the product contains Apache‑licensed components, include the full license text, retain copyright, patent, trademark, and attribution notices in source or object forms, and make modifications evident. Additionally, you must include the Apache License 2.0 terms in all distributions, ensuring downstream recipients receive the same patent safeguards, without obligating you to disclose proprietary code. The product remains closed‑source, as the license not require disclosure of modifications.

How Long Does the Apache License Patent Grant Remain Valid After Project Termination?

Imagine 90% of open‑source projects terminate, yet you retain a perpetual patent shield. Post‑termination, the Apache license grants you an irrevocable, worldwide, royalty‑free patent license that persists forever. You enjoy that same grace—grant continuity—regardless of the project’s end. No expiration or buy‑back clause applies unless you initiate litigation. Consequently, the patent grant endures indefinitely, safeguarding your downstream deployments, including any future integrations or third‑party distributions and keeping your commercial viability.

Can a Contributor Revoke Their Patent Grant After Accepting a Contribution?

No, you can’t revoke the patent grant you offered once your contribution is accepted. The license requires that your grant be royalty‑free, irrevocable, and perpetual. Consequently, a retraction possibility is explicitly excluded; only an initiatory filing of patent litigation by you (the licensee) may terminate the license. Hence, the grant stays permanent, and retracting it is legally impossible. Consequently you may rely on the right to use the software, fear.

Conclusion

By embracing the Apache License patent grant, you install a protective framework that safeguards your code and users alike. The grant functions like a lighthouse, illuminating the path through patent litigation’s turbulent seas. You retain the right to modify, distribute, and build upon the work, while the grant simultaneously bars any patent claims against you. Consequently, you are empowered to innovate confidently, knowing that the license’s patent clauses act as an ironclad shield for all.

James Bateson

Lawyer