The Apache License is a permissive software license maintained by the Apache Software Foundation (ASF). It allows software to be used, copied, modified, and redistributed, including within proprietary products, subject to conditions concerning license notices, attribution, and identification of modifications. Its principal modern version, Apache License, Version 2.0, also includes an explicit patent license from contributors. It is widely used for open-source software both within and outside ASF projects.
History and status
The license developed alongside the Apache HTTP Server project. Earlier versions included Apache License 1.0 and version 1.1, released in 2000. Version 2.0 was released in January 2004, revising the terms to clarify redistribution requirements, formalize contributions, and provide explicit patent provisions.
Version 2.0 is recognized by the Open Source Initiative as an open-source license and by the Free Software Foundation as a free software license. These classifications concern recipients’ freedoms and the license’s terms, not whether copies must be distributed without charge.
The SPDX identifier for version 2.0 is Apache-2.0. SPDX identifiers provide standardized labels for licenses in package metadata, source files, and software inventories. Earlier Apache license versions have separate identifiers and should not be treated as interchangeable with version 2.0.
Permissions and scope
Copyright permissions
Under version 2.0, each contributor grants a perpetual, worldwide, nonexclusive, royalty-free copyright license, described as irrevocable subject to the license’s terms. The grant covers reproduction, preparation of derivative works, public display, public performance, sublicensing, and distribution of the work and its derivative works in source or object form.
These permissions allow activities such as:
- Using the software privately or commercially.
- Modifying it for internal purposes without publishing the modifications.
- Distributing original or modified copies.
- Incorporating covered code into a larger product, including proprietary software.
- Charging for copies, support, warranties, or related services.
The license does not generally require distributors to publish source code. Unlike a copyleft license, it does not require an entire derivative work to remain under the same license. However, adding different terms to modifications or to a larger product does not remove the Apache License obligations that continue to apply to the incorporated Apache-licensed material.
Source and object forms
The license defines “Source” broadly as the preferred form for making modifications. This can include software source code, documentation source, and configuration files. “Object” form includes forms resulting from mechanical transformation or translation, such as compiled code and generated documentation.
Its definition of “Derivative Works” excludes works that remain separable from the licensed work, or merely link or bind by name to its interfaces. This distinction helps define the license’s scope, although the legal characterization of a particular combination can also depend on applicable copyright law.
Redistribution requirements
Section 4 of version 2.0 sets out the central redistribution conditions. These apply when distributing the work or derivative works, with or without modifications, in source or object form.
License copy and modification notices
Recipients must receive a copy of the Apache License. Distributors must also cause modified files to carry prominent notices stating that those files were changed. This is a requirement to identify changes, not a general obligation to publish a detailed change history or disclose modified source code.
Preservation of notices
In the source form of distributed derivative works, distributors must retain copyright, patent, trademark, and attribution notices from the source form of the original work. Notices that do not pertain to any part of the derivative work may be excluded.
This requirement is distinct from the obligation to provide the license text. Supplying the license alone does not necessarily satisfy all applicable notice requirements.
The NOTICE file
If the original work includes a NOTICE text file, distributed derivative works must include a readable copy of the relevant attribution notices it contains. The license permits those notices to appear in one or more specified locations:
- A
NOTICEfile distributed with the derivative work. - Source code or documentation supplied with it.
- A display generated by the derivative work, wherever such third-party notices normally appear.
Notices unrelated to the derivative work may be omitted. The contents of NOTICE are informational and do not modify the license. Additional attribution notices may be added, provided they cannot be construed as changing its terms.
The Apache License does not itself require every project to create a NOTICE file. The redistribution obligation arises when the licensed work includes one.
Patent provisions
Version 2.0 contains an explicit patent license from each contributor. It covers patent claims that the contributor can license and that are necessarily infringed by the contributor’s contribution alone, or by the combination of that contribution with the work to which it was submitted.
The grant includes rights to make, have made, use, offer to sell, sell, import, and otherwise transfer the work. Its scope is limited: it is not a license to every patent held by a contributor and does not guarantee that third parties hold no relevant patents.
The license also contains a patent-termination provision. If a recipient institutes patent litigation against any entity, including through a cross-claim or counterclaim, alleging that the work or a contribution incorporated within it constitutes direct or contributory patent infringement, patent licenses granted to that recipient under the Apache License for that work terminate as of the filing date.
This provision concerns the specified patent grants; it is not worded as automatic termination of all copyright permissions.
Contributions and trademarks
Submission of contributions
Unless explicitly stated otherwise, contributions intentionally submitted for inclusion in a work by its copyright owner, or an authorized representative, are submitted under the Apache License without additional terms or conditions. The license defines submission to include certain communications through project mailing lists, source-control systems, and issue trackers.
Communications conspicuously designated in writing as “Not a Contribution” are excluded from that definition. The license also preserves the effect of separate agreements concerning contributions. A contributor license agreement, where used by a project, is therefore a separate instrument rather than a requirement imposed universally by the Apache License.
Trademark limits
The license does not grant general permission to use contributors’ trade names, trademarks, service marks, or product names. It allows the use reasonably required to describe the work’s origin and reproduce NOTICE content.
Consequently, permission to redistribute code does not automatically include permission to market a modified product under the original project’s name or logo. Copyright licensing and trademark permissions address different rights.
Compatibility with other licenses
License compatibility concerns whether material under different licenses can be combined and distributed while satisfying all applicable conditions.
The Free Software Foundation considers Apache License 2.0 compatible with version 3 of the GNU General Public License (GPL). Apache-licensed code can therefore be incorporated into an appropriately licensed GPLv3 combined work, with the Apache conditions continuing to be respected.
The same organization considers Apache License 2.0 incompatible with GPL version 2 alone. This distinction matters for software designated “GPL-2.0-only” rather than software whose license permits use of a later GPL version. Compatibility with GPLv3 also does not mean that GPLv3-covered material can simply be redistributed under Apache License 2.0.
Compared with the MIT License and common BSD licenses, Apache License 2.0 states more detailed rules concerning patents, contributions, modifications, and attribution. All are commonly classified as permissive licenses, but their specific obligations differ.
Use and limitations
Apache License 2.0 is used by projects including Apache Hadoop, Apache Spark, and TensorFlow. Its use is not restricted to software developed by the ASF, and adopting it does not make a project an ASF project.
The license contains no network-use source-disclosure requirement. Running modified software as a hosted service does not, merely because users interact with it over a network, create a general obligation under this license to publish its source.
The work is supplied on an “AS IS” basis, without warranties or conditions, except where applicable law requires otherwise or a written agreement provides them. The license also limits contributors’ liability, subject to its stated exceptions. Distributors may offer support, warranties, indemnities, or other liability obligations on their own behalf, rather than on behalf of other contributors.
Finally, a project’s main license does not establish that every bundled component has identical terms. Dependencies, separately licensed files, documentation, and other assets may carry their own conditions. The Apache License grants rights within the scope of the contributors’ grants; it does not establish ownership of all material in a distribution or eliminate third-party intellectual-property claims.