Clickwrap is usually enforceable. For terms of service, SaaS signup and app EULAs, a well-built “I accept” checkbox is the right tool and a signature flow would be overkill.
But the question is framed wrongly, and the framing causes the confusion. Clickwrap is an electronic signature. Under ESIGN, an electronic signature is any electronic sound, symbol or process adopted with intent to sign a record — and a checkbox clicked with intent to accept terms fits that definition squarely.
So the real question isn’t clickwrap or e-signature. It’s how much evidence of assent your document needs, and clickwrap sits near one end of that range.
Key takeaways
Clickwrap is a form of electronic signature, not an alternative to one.
Courts apply a two-part test: reasonably conspicuous notice, plus an action that unambiguously manifests assent.
A click only counts if the user was explicitly told that clicking means agreeing.
Browsewrap — terms behind a link with no affirmative action — usually fails.
The practical weakness of clickwrap is version evidence, not enforceability in the abstract.
Negotiated terms, identity-sensitive documents and Statute of Frauds matters need a signature flow.
The spectrum of online assent
Pattern | What the user does | Typical enforceability |
|---|---|---|
Browsewrap | Nothing. Terms linked in a footer. | Usually unenforceable |
Sign-in wrap | Clicks a button; notice says continuing means agreeing | Depends entirely on design |
Clickwrap | Checks a box or clicks “I agree” with terms presented | Routinely enforced |
Scrollwrap | Must scroll through terms before accepting | Strongest |
E-signature flow | Signs a specific document, identity verified, audit trail | Strongest evidence; highest friction |
Each step adds friction and adds proof. The design question is matching the level to the document.
The test courts actually apply
The leading modern statement is Berman v. Freedom Financial Network, LLC, 30 F.4th 849 (9th Cir., 5 April 2022). Where a company can’t show the user had actual knowledge of the terms, it can establish assent through inquiry notice — but only by demonstrating two things:
The website provided reasonably conspicuous notice of the terms to which the consumer would be bound consumerfinancemonitor
The consumer took some action, such as clicking a button or checking a box, that unambiguously manifested assent to those terms consumerfinancemonitor
Clickwrap, where a contract is displayed and must be agreed to with a click, is routinely found enforceable. Browsewrap, where assent is supposedly manifested by continuing in the presence of a hyperlink, is enforced far less often. Sign-in wrap sits in a gray zone where enforceability requires conspicuous textual notice that completing the transaction signifies consent. calawyersjustia
The sharpest point in the case: a click constitutes unambiguous assent only when the consumer is explicitly advised that clicking will signify agreement to the terms. In Berman, the page carried the sentence “I understand and agree to the Terms & Conditions which includes mandatory arbitration” near a large green Continue button — and the court still held that clicking it didn’t manifest unambiguous assent, because nothing indicated the legal significance of the click. consumerfinancemonitormaddinhauser
That’s a high bar, and it’s still being applied. In November 2026 the Ninth Circuit again relied on Berman to refuse to compel arbitration in a case involving an online retailer, reiterating that businesses should not rely on the mere availability of a hyperlink or on language buried in terms declaring that site use constitutes acceptance. [LEGAL REVIEW] consumerfinancemonitor
What this means for design
Conspicuousness turns on the transactional context, the notice’s size relative to other text on the page, its proximity to the button or box the user must click, and whether hyperlinks are readily identifiable. Read closely, the opinion is a usability critique written by judges. ericgoldmankoji
Practical requirements that follow:
Tie the action to the consequence explicitly. “By checking this box, I agree to the Terms of Service” — not a notice sitting near a button labelled “Continue.”
Make the link look like a link. Contrasting colour, underlined. Grey text at the same weight as body copy has been held insufficient.
Put the notice adjacent to the control, not elsewhere on the page.
Size it legibly relative to surrounding text. Fine print is the thing courts single out.
Prefer a checkbox over a button. A dedicated affirmative act is cleaner evidence than a dual-purpose Continue button.
Don’t bury it. Buried terms are the specific pattern the November decision warned against.
The recommended approach is a clearly designed clickwrap process giving reasonably conspicuous notice and expressly informing the user that a specified action constitutes acceptance. consumerfinancemonitor
The problem nobody plans for: version evidence
Enforceability in the abstract isn’t where clickwrap actually fails. Proving what was accepted is.
A dispute arrives three years later. You need to show: this specific user, on this specific date, saw this specific version of the terms, presented in this specific interface, and took this specific action. If your terms have changed eleven times since, can you produce the version that was live that day — and a screenshot or record of the page as it rendered?
Most companies cannot. They have a current terms page and a database row saying accepted_tos: true.
What to capture at acceptance:
Terms version identifier, immutably linked to the record
The exact terms text as served, archived
Timestamp, user identifier, IP
A record of the interface presented — the notice, placement and wording
The affirmative action taken
And for changes: a mechanism for re-acceptance. Unilateral amendment clauses, where you reserve the right to change terms by posting them, receive sceptical treatment. Material changes generally warrant fresh affirmative assent rather than a posted update.
This is the same evidential job an audit trail does in a signature flow, and it’s why retention matters here too: how long to keep signed documents. [LEGAL REVIEW]
When clickwrap is the right call
Terms of service and privacy policy acceptance at signup
Self-serve SaaS subscriptions on standard terms
App EULAs
Marketplace seller and buyer terms
Standardised, non-negotiated, high-volume agreements
Common thread: the terms are identical for everyone, nothing is negotiated, volume makes signature friction untenable, and the counterparty’s precise identity matters less than the fact of acceptance.
When you need a signature flow
Negotiated terms. If anything was discussed and changed, you need a record of the final agreed version, signed. An MSA or SOW with custom terms isn’t a clickwrap candidate.
Statute of Frauds documents. Real property, contracts not performable within a year, suretyship, sale of goods at $500 or more. These need a signed writing, and you want strong evidence of who signed.
Where identity actually matters. Clickwrap proves an account holder clicked. It doesn’t prove which human was at the keyboard. Where you need to tie assent to a verified individual — regulated transactions, high value, or anything where identity may be contested — you need verification. Types of electronic signatures covers assurance levels, which matter more under eIDAS than in the US.
Employment agreements. Arbitration and restrictive covenants in employment receive heightened scrutiny in many jurisdictions. A click at onboarding is weaker ground than you’d want.
Consumer contracts under ESIGN’s consent rules. Where law requires information to be provided to a consumer in writing, ESIGN requires affirmative consent to electronic delivery plus specific disclosures before you can satisfy that requirement electronically.
Anything you’d want to hand to a court as a complete document. A signed PDF with a completion certificate is a self-contained artefact. A database row is an argument.
Hybrid: use both
Most mature products run both, and this is usually the right answer:
Clickwrap for platform terms, privacy policy, acceptable use — the standardised layer
E-signature for enterprise agreements, custom terms, order forms, DPAs — the negotiated layer
If you’re building signing into your own product, embedded signing for SaaS products covers the implementation pattern, and signing API vs SDK covers the integration choice. How an e-signature API improves customer experience covers keeping the friction proportionate.
The design goal is matching evidence to stakes — not maximising friction everywhere, and not minimising it everywhere either.
Related confusions worth clearing up
Three terms get tangled with this one:
Email acceptance. Replying “I agree” to an email can form a contract. Different mechanism, similar questions about intent and authority — see is replying “I agree” legally binding.
Email signature. The footer block. Not related, except that courts have occasionally found it to be a signature — see email signature vs electronic signature.
Digital signature. The cryptographic technique. A method of implementing higher-assurance e-signatures, not a synonym for either.
Common mistakes
Browsewrap. A footer link and hope. The pattern courts have rejected repeatedly.
A Continue button with notice nearby, rather than an explicit statement that clicking means agreeing.
Hyperlinks that don’t look like links.
No version evidence. The failure that surfaces in litigation.
Unilateral amendment by posting, without re-acceptance on material change.
Clickwrap for negotiated terms.
Assuming clickwrap identifies a person. It identifies an account.
Signature flows for standard ToS, adding friction that buys nothing.
FAQ
Is clickwrap legally binding?
Generally yes, where the interface gives reasonably conspicuous notice and the user takes an action that unambiguously manifests assent. Clickwrap is routinely enforced; browsewrap usually isn’t.
Is clickwrap an electronic signature?
Yes. Under ESIGN, an electronic signature is any electronic process adopted with intent to sign. A checkbox clicked to accept terms qualifies. The distinction between clickwrap and a signature flow is evidential strength, not legal category.
What’s the difference between clickwrap and browsewrap?
Clickwrap requires an affirmative act — checking a box or clicking “I agree” — with terms presented. Browsewrap relies on a link and the claim that using the site implies agreement. Courts enforce the first and rarely the second.
Does clicking a button count as agreeing?
Only if the user was explicitly told that clicking constitutes agreement. Courts have held that clicking a “Continue” button, even with terms language nearby, didn’t manifest unambiguous assent where nothing indicated the click’s legal significance.
When do I need a real signature instead?
Negotiated terms, Statute of Frauds documents, anything where identity may be contested, employment agreements, and regulated consumer contracts.
Does clickwrap prove who agreed?
It proves an account took an action. It doesn’t establish which individual was at the device. Where that matters, you need identity verification.
Can I change my terms and rely on the original acceptance?
Risky. Unilateral amendment by posting is treated sceptically. Material changes generally warrant fresh affirmative acceptance.
What should I log at acceptance?
Terms version, archived text as served, timestamp, user identifier, IP, a record of the interface presented, and the specific action taken.
