Software and IP License Agreements: Exclusive Versus Nonexclusive and How the Grant Controls Everything Else

By Hank FasthoffJuly 6, 2026

A license grants permission to use someone else's intellectual property under defined conditions while the licensor keeps ownership. When you license software, a patent, a trademark, or a copyrighted work, the licensor retains ownership and gives you the right to use the IP within the boundaries of the license grant. Every other provision in the agreement, including territory, duration, payment, sublicensing rights, and termination, flows from the scope of that grant. If the grant is ambiguous, every downstream provision is ambiguous too.

License grant clauses are the most litigated provision in IP licensing because their scope determines what the licensee can do, where, for how long, and under what conditions. A licensee who exceeds the scope of the grant may be committing infringement on top of breach of contract. Under copyright and patent law, that overreach opens up statutory damages, injunctive relief, and attorney's fees that wouldn't be available in an ordinary contract dispute.

Exclusive Versus Nonexclusive

An exclusive license grants the licensee the sole right to use the licensed IP within the defined territory, field of use, and duration. Nobody else can use the IP in the licensed scope, including the licensor. If a software company grants an exclusive license for its platform in the healthcare industry in the United States, neither the licensor nor any other licensee can use that platform in healthcare in the U.S. during the license term.

Under the Copyright Act (17 U.S.C. § 101), an exclusive license is a "transfer of copyright ownership," which means it must be in writing and signed by the owner of the rights conveyed. An oral exclusive license won't be enforced as exclusive. It may create an implied nonexclusive license, but it won't give the licensee the exclusivity it expected.

Because exclusivity prevents the licensor from licensing the same IP to others (and from using it in the licensed scope), exclusive licenses command higher fees, longer terms, and more detailed performance obligations. A licensor granting exclusivity wants assurance that the licensee will exploit the IP aggressively. If the licensee holds an exclusive license without commercializing the product, the licensor loses revenue it could have earned by licensing to others. Minimum royalty guarantees, milestone-based performance requirements, and "use it or lose it" provisions protect the licensor against an underperforming exclusive licensee.

A nonexclusive license permits the licensee to use the IP, but the licensor retains the right to grant identical licenses to other parties and to use the IP itself. Most software licenses are nonexclusive, because the licensor's business model depends on licensing the same product to multiple customers. Nonexclusive licenses are simpler, less expensive, and don't restrict the licensor's ability to monetize the IP through other channels.

Under 17 U.S.C. § 205(e), a nonexclusive copyright license survives a transfer of the underlying copyright if the license was granted before the transfer and is evidenced by a written instrument signed by the copyright owner. This means that if the licensor sells its copyright to a third party, the licensee's nonexclusive license remains valid, provided the license was in writing and was granted before the sale.

Territory

Territory defines where the licensee can use the licensed IP. A worldwide license imposes no geographic restriction. A license limited to the United States confines the licensee's rights to U.S. territory. A license limited to Texas and Louisiana confines rights to those two states.

For patent licenses, territory can't exceed the geographic reach of the licensed patents. A U.S. patent provides no rights outside the United States, so a patent license that purports to grant worldwide rights based on a U.S. patent doesn't accomplish what it describes. If the licensor has patents in multiple countries, the license should identify which patents are licensed in which territories.

For software and copyright licenses, territorial restrictions are contractual rather than inherent in the IP right (because copyright protection is territorial but a copyright owner's rights aren't limited to the country of registration). Territorial restrictions in software licenses are often tied to export control compliance, because exporting certain software or technology to restricted countries may violate the Export Administration Regulations (EAR) or the International Traffic in Arms Regulations (ITAR).

Field of Use

Field of use limits the licensee's rights to a specific industry, application, or market segment. A pharmaceutical company might license a drug formulation for veterinary use only while the licensor retains rights for human therapeutics. A software company might license its platform for use in financial services while retaining the right to license separately for healthcare.

Field-of-use restrictions let licensors segment markets and maximize licensing revenue by granting different licenses to different licensees in different industries. For licensees, field-of-use restrictions can be a trap if the licensee's business evolves beyond the licensed field. A company that licenses technology for "consumer electronics" may discover that its most profitable application falls outside that definition, and using the technology in an unlicensed field is an infringement, not just a contract breach.

Define the field of use with enough specificity to be enforceable but enough breadth to accommodate the licensee's reasonable business evolution. Use defined terms ("Licensed Field" in a schedule) rather than embedding the definition in the grant clause, so the field can be amended later without restructuring the license grant itself.

Duration and Renewal

License duration can be perpetual (lasting indefinitely, subject to termination for cause), fixed-term (a stated period, such as five years, with or without renewal options), or tied to the life of the underlying IP (lasting until the patent expires or the copyright enters the public domain).

Perpetual licenses are common for purchased software and are appropriate when the licensee is paying a one-time fee for a permanent right to use the product. Fixed-term licenses are common for subscription software, technology partnerships, and trademark licenses where the licensor wants periodic opportunities to renegotiate terms or terminate underperforming licensees.

Renewal provisions should specify whether renewal is automatic or requires affirmative action, the notice period for declining renewal (to prevent inadvertent auto-renewal), whether the royalty rate or license fee changes at renewal, and whether the licensee's exclusivity continues into the renewal term on the same conditions.

Sublicensing

A sublicense grants a third party the right to exercise some or all of the licensee's licensed rights. Without an affirmative grant of sublicensing rights, the licensee can't sublicense. Most software licenses prohibit sublicensing entirely.

When sublicensing is permitted, the license should address whether the licensor's consent is required for each sublicense or whether a blanket right is granted, whether sublicenses to affiliates (subsidiaries, parent companies) are permitted without separate consent, whether the sublicensee's terms must be at least as protective of the licensor's IP as the head license, what happens to sublicenses if the head license terminates (do sublicenses survive or terminate automatically), and whether the licensee is responsible for the sublicensee's compliance with the license terms.

Reservation of Rights

Every license should include an express reservation of rights. "All rights not granted in this Agreement are reserved by Licensor." This single sentence prevents arguments that the licensor's silence on a particular use should be interpreted as permission. Without a reservation clause, a licensee may argue that the licensor's failure to prohibit a specific use implies that the use is licensed.

A reservation of rights clause works together with the scope limitations in the grant to define the boundaries of the license. Everything inside the grant is licensed. Everything outside the grant is reserved. If the grant is ambiguous, the reservation clause reinforces that the ambiguity should be resolved in the licensor's favor.

Exceeding the Scope

When a licensee uses licensed IP in a way that falls outside the scope of the license (outside the territory, outside the field of use, beyond the permitted number of users or installations), the licensor has two potential theories of recovery.

Breach of contract treats the scope limitation as a contractual covenant. The remedy is damages for breach, which are typically limited by the contract's limitation of liability clause. The licensor recovers its expectation damages (the royalties or fees the licensee should have paid for the expanded use) but can't recover statutory damages or attorney's fees.

Infringement treats the scope limitation as a condition of the license. If the licensee's use falls outside the conditions of the license, the use is unlicensed, and the licensor can bring an infringement action under copyright law (17 U.S.C. § 501) or patent law (35 U.S.C. § 271). Infringement remedies include statutory damages (up to $150,000 per work infringed for willful copyright infringement), injunctive relief (a court order stopping the infringing use), and attorney's fees in exceptional cases.

Whether a scope violation is breach or infringement turns on whether the violated term is a "condition" of the license (breach of which constitutes infringement) or a "covenant" (breach of which is actionable only as a contract claim). Courts evaluate this distinction under the applicable state's contract law, and the outcome can depend on how the license agreement is drafted. Drafting scope limitations as conditions rather than covenants preserves the licensor's access to infringement remedies, which are significantly more powerful than contract remedies.

Payment Structures

How the licensee pays for the license affects both parties' incentives and risk allocation.

A lump-sum license fee (one payment for a perpetual or fixed-term license) is simple and provides the licensee cost certainty. But it provides the licensor no upside if the licensed product succeeds beyond expectations, and no ongoing revenue stream.

Running royalties (a percentage of net sales, typically 2 to 10 percent depending on the industry and the IP's value) align the licensor's revenue with the licensee's commercial success. If the product sells well, both parties benefit. Royalty arrangements require the licensee to report sales periodically (monthly or quarterly) and give the licensor audit rights to verify the reports.

Per-unit or per-seat pricing (a fixed fee per copy sold, per user, or per installation) is common in software licensing and provides predictable per-unit economics for both parties.

Minimum royalty guarantees require the licensee to pay a stated minimum amount regardless of sales performance, protecting the licensor against a licensee who licenses the IP and then underperforms. Minimums are particularly common in exclusive licenses, where the licensor has given up the right to license to others and needs assurance that the exclusivity is producing revenue.

Effect of Termination on the License

What happens to the license when the agreement terminates is one of the most consequential provisions in the agreement and one of the most commonly overlooked.

If the license terminates, the licensee must stop using the licensed IP immediately. Any continued use after termination is infringement. If the license survives termination (because it's perpetual and paid-up, or because the agreement provides that certain license grants survive), the licensee retains the right to use the IP on the terms specified in the surviving grant.

For software licenses, termination provisions should address whether the licensee must delete or return all copies of the software, whether any transition period is provided for the licensee to migrate to an alternative, and whether previously created works (documents, reports, designs produced using the software) can continue to be used after the license ends.

Practical Recommendations

Draft the license grant with precision. Identify the licensed IP (by name, version, patent number, or registration number), the licensed rights (to use, reproduce, modify, distribute, publicly display, publicly perform), the scope limitations (territory, field of use, duration, number of users), and any restrictions (no sublicensing, no modification, no reverse engineering).

Include a reservation of rights clause. Every right not granted should be reserved, and the agreement should state so.

Address what happens when the licensee exceeds the scope. Specify whether scope limitations are conditions (breach constitutes infringement) or covenants (breach is a contract claim only). If the licensor wants infringement remedies, draft accordingly.

Define payment terms with precision. If the license is royalty-bearing, define "net sales" (the royalty base), the royalty rate, the reporting period, the payment deadline, and the licensor's audit rights.

Specify the effect of termination on the license. State whether the license survives or terminates, what the licensee must do with the licensed IP after termination, and whether any transition period applies.

For exclusive licenses, include performance obligations that prevent the licensee from sitting on the IP. Minimum royalty guarantees, commercialization milestones, and reversion to nonexclusive (or termination) for failure to meet milestones protect the licensor against a licensee who locks up the IP without exploiting it.