End-user License Agreements, Click-Wrap to Shrink-Wrap and What Each One Binds
End-user license agreements are the contracts between software publishers and the people installing or using the software. Every shipped end user license agreements package allocates three things: the scope of the license grant, the restrictions on the user's conduct, and the risk between publisher and user when something breaks. The three formation patterns, click-wrap, browse-wrap, and shrink-wrap, decide whether the EULA is enforceable in the first place, and the federal opinions below set the rule for each.
Click-Wrap
Affirmative click on an I-Agree button before install or activation.
Strong. Federal courts uphold click-wrap regularly under ProCD v. Zeidenberg, 86 F.3d 1447 (7th Cir. 1996), as long as the terms are reasonably visible at the click moment.
Typical: SaaS sign-up, mobile app install, desktop software activation.
Browse-Wrap
Hyperlinked license in page footer; continued use treated as assent.
Weak. Often struck under Specht v. Netscape, 306 F.3d 17 (2d Cir. 2002), unless the user is on actual or inquiry notice of the terms.
Typical: Free websites, content platforms, marketing pages.
Shrink-Wrap
Breaking the package or opening the disc envelope binds the buyer.
Mixed. Enforceable where the buyer has a chance to read the terms and to return the product if they disagree.
Typical: Retail boxed software, OEM hardware bundles, legacy media.
What End User License Agreements Actually Bind
An end user license agreements package is a contract that combines a copyright license with a service agreement. The publisher owns the underlying software through copyright protection under 17 U.S.C. § 102 and the patent statute where applicable. The publisher does not sell the software; the publisher sells a license to use the software within the boundaries the EULA defines. That distinction matters, because the user never owns the code, never owns the copy, and never owns the right to redistribute. The EULA is what authorizes the use in the first place.
The contractual frame layered on top of the copyright license is ordinary contract law. Restatement (Second) of Contracts § 211 governs standardized agreements offered on a take-it-or-leave-it basis. Section 211 directs courts to enforce a standardized agreement against the user only as to terms the user would have assented to had they actually read the agreement, and to refuse enforcement of any term that the user could not reasonably have expected. That section is the doctrinal anchor for the unconscionability challenges that most EULA disputes turn on.
Two practical implications follow from that frame. First, an EULA that is conspicuous, clearly presented, and reasonable in its allocation of risk will be enforced. Second, an EULA that hides the consequential terms (binding arbitration, class waiver, limitation of liability) below the affirmative-click moment, or inside dense text the user cannot reasonably parse, will be challenged successfully under section 211. The case law that settles those challenges is the next layer.
For business contracts that sit alongside software licensing in commercial transactions, the foundational frame is the same. The laws of contracts walkthrough covers the offer, acceptance, consideration, and mutual-assent elements that make any agreement, including a license, binding in the first place.
Why Software Publishers Ship End-user License Agreements at All
Software publishers ship end-user license agreements for four overlapping reasons, and any one of them would justify the document standing alone. The first reason is the copyright license itself. Without an affirmative grant of permission to install and run the software, every install is an infringement. The EULA is the affirmative license grant, and the scope of that grant (single user, single device, perpetual, term, subscription) is the publisher's primary lever for monetizing the work.
The second reason is risk allocation. Publishers ship software that runs in environments they cannot test for, on data they cannot inspect, alongside other software they did not write. A commercial-grade EULA pairs a warranty disclaimerof merchantability and fitness for a particular purpose with alimitation of liability capped at the price paid for the license, and shifts to the user any liability the user causes by misusing the product. Without those clauses, every database corruption incident or compatibility failure would expose the publisher to uncapped consequential damages.
The third reason is dispute-resolution control. Most EULAs include a binding arbitration clause that routes any user dispute to a single-forum, single-arbitrator proceeding under the rules of AAA or JAMS. They also routinely include aclass-action waiver that bars users from joining together in a class. Both mechanisms drive disputes into a forum the publisher prefers and cap the size of any single proceeding. The Federal Arbitration Act, 9 U.S.C. § 1 et seq., generally enforces those clauses against users where the EULA was properly formed.
The fourth reason is data and feedback rights. Modern EULAs include a license-back of telemetry, usage data, error reports, and any feedback the user volunteers about the product. The publisher uses that data to improve the product and to train downstream models. The clause is unobjectionable in a consumer context but matters significantly for enterprises whose data sets are themselves valuable assets, which is why enterprise license agreements override the standard EULA on the data clause.
Anatomy of a Working End-user License Agreement
A working end-user license agreements document organizes the same recurring sections regardless of vertical. The sections below appear in the order most publishers ship them. The license grant comes first because everything else is a modification of the grant; restrictions narrow it, warranty disclaimers cap exposure inside it, dispute resolution channels any conflict over it.
1License Grant
Names the licensee, identifies the licensed software, and sets the scope: number of users, number of devices, internal business use only, single tenant, and whether the grant is perpetual or term-limited.
2Restrictions on Use
Lists the user's negative covenants: no reverse engineering, no sublicense, no derivative works, no notice removal, no competing-product creation, no excessive seat sharing.
3Ownership and IP
Confirms the publisher retains all copyright, patent, and trade secret rights in the software. License is not a sale. User keeps any user data; publisher takes a license-back of feedback and telemetry.
4Warranty Disclaimer
Disclaims implied warranties of merchantability and fitness for a particular purpose. Provides software AS-IS. State law may carve out a narrow consumer-protection exception.
5Limitation of Liability
Caps publisher's exposure at the license fee paid in the preceding twelve months. Excludes consequential, incidental, indirect, and punitive damages. Survives termination.
6Indemnification
User indemnifies publisher for harm caused by the user's misuse, integration with third-party software, or violation of acceptable-use rules. Publisher's reciprocal indemnity covers IP infringement claims tied to the licensed code.
7Termination
Publisher's right to terminate for breach, with a cure window where applicable. User's right to terminate for convenience. Effects of termination: license ends, user destroys copies, surviving clauses persist.
8Dispute Resolution
Choice of governing law. Choice of forum. Binding arbitration clause and class-action waiver where used. Carve-outs for injunctive relief, IP enforcement, and small-claims actions.
Six Recurring User Restrictions, Drafted as Negative Covenants
User cannot disassemble, decompile, or attempt to derive source code from the licensed binary, except as expressly permitted by law.
User cannot transfer, lease, lend, or sublicense the software to any third party. Enterprise grants name the licensee and bind to that entity only.
User cannot create derivative works based on the software's code, structure, or non-public APIs without the publisher's separate written permission.
User cannot remove or alter copyright notices, trademark notices, or other proprietary legends embedded in the software or the documentation.
Use is limited to the named purpose: single user, single device, single tenant, internal business operations only. Resale or service-bureau use is barred.
User must use the software in compliance with applicable export controls, data protection laws, and the publisher's posted acceptable-use policy.
Companies extending a software license alongside a confidentiality relationship pair the EULA with a separate non-disclosure agreement template that covers the user's exposure to confidential code, design documents, or beta features. The two documents work together: the EULA governs use, the NDA governs disclosure.
When Federal Courts Enforce, and When They Strike, End-user License Agreements
Two federal opinions still set the rule for whether an EULA binds the user. The 7th Circuit's opinion in ProCD remains the foundational authority for upholding click-wrap and shrink-wrap where formation is conspicuous. The 2nd Circuit's opinion in Specht remains the foundational authority for striking browse-wrap when the user is never required to see the terms. Together, the two cases describe the formation spectrum every EULA sits on.
Survived: Click-wrap with conspicuous assent
ProCD v. Zeidenberg, 86 F.3d 1447 (7th Cir. 1996). The 7th Circuit upheld a shrink-wrap license that limited a database to non-commercial use, with Judge Easterbrook reasoning that buyers had ample opportunity to read the terms and return the product. The decision became the foundational authority for click-wrap enforcement when the formation moves online.
Struck: Browse-wrap without notice of terms
Specht v. Netscape, 306 F.3d 17 (2d Cir. 2002). The 2nd Circuit refused to enforce an arbitration clause buried in a license linked from below the download button, where users were never required to see or assent to the terms before downloading. The opinion is now the leading authority for striking browse-wrap when the user is not on actual or inquiry notice.
Drafter's Red Flags, the Five Clauses That Get Struck
Browse-wrap with no notice. A licensing link in the footer with no affirmative click moment fails Specht and most Specht-adopting circuits.
Hidden mandatory arbitration. Where the arbitration clause is buried in dense terms with no conspicuous heading, courts apply Restatement § 211 and refuse to enforce it as outside the user's reasonable expectation.
Excessive class-action waiver. Class waivers that operate as a de facto immunity (because individual damages are too small to justify pursuit) are more vulnerable under state unconscionability doctrines than they were pre-Concepcion.
Liability caps below the license fee. Caps that purport to limit publisher liability to less than the price paid for the license are unconscionable in many jurisdictions and are routinely reformed upward.
Unilateral amendment with no notice. Provisions that let the publisher amend the EULA at any time with continued use treated as assent fail in most courts where the change is material and the user is not given an opportunity to opt out.
The pattern across the case law is not anti-publisher. It is anti-surprise. EULAs survive when the formation is conspicuous, the terms are reasonable, and the user has a real opportunity to assent or to walk away. EULAs fail when any of those conditions slip, and the failure mode is consistent across click-wrap, browse-wrap, and shrink-wrap variations alike. For business agreements that ship alongside software (like operating agreements for the licensee entity, partnership agreements, or service contracts that depend on the licensed product), the types of agreements in business overview and the LLC operating agreements template cover the entity-side documents the licensee usually pairs with an enterprise EULA.
End-user License Agreements, Frequently Asked Questions
Can end user license agreements put you at risk?
Should I accept or decline the end user license agreement?
What does an end user license agreement represent?
What are the three types of licensing agreements?
Drafting or Reviewing an Enterprise EULA?
The shipped click-wrap is the floor for consumer use. Enterprise deployments routinely move to a negotiated agreement above the floor, with custom terms on data, liability, indemnification, and termination. Submit the deal facts and an IP and software licensing attorney will return a drafted or reviewed end-user license agreement, calibrated to the licensee's deployment footprint and risk profile.
Get a Custom Software Licensing QuoteOr browse the contract templates Word library and the free agreement contract template catalog for the underlying drafting frames.