What Is a Limitation of Liability Clause?

A limitation of liability clause is a contract provision that caps the maximum amount one party can recover from the other if something goes wrong. Courts generally enforce these provisions in commercial contracts between businesses, though they apply them more carefully in consumer contexts where power imbalances are significant. It's one of the most important clauses in any commercial contract, and it's almost always buried in the fine print.

The basic idea: no matter how badly one party screws up, their maximum financial exposure is capped at a specified amount. For a SaaS contract, that cap is often the amount you paid in the last 12 months. For a freelance contract, it might be the total project fee.

What a Limitation of Liability Clause Looks Like

Here's a typical example:

"In no event shall either party be liable for any indirect, incidental, special, consequential, or punitive damages. Each party's total liability arising out of or related to this agreement shall not exceed the amounts paid by Client to Service Provider in the twelve (12) months preceding the claim."

This clause does two things:

1. Excludes certain types of damages (consequential, indirect, punitive)
2. Caps direct damages at a specified amount (12 months of fees)

Types of Damages the Clause Usually Excludes

Consequential damages are the downstream harm from a breach. If a software vendor's data breach exposes your customer list and you lose $500,000 in business as a result, that's consequential damage. Most limitation of liability clauses exclude these entirely.

Indirect damages are similar to consequential damages: harm that flows from the breach but isn't a direct result. Lost profits, lost business opportunities, reputational harm.

Punitive damages are damages designed to punish bad conduct, not just compensate the victim. These are excluded in virtually every commercial contract.

Incidental damages are expenses incurred as a result of a breach, like the cost of finding a replacement vendor.

Why This Clause Is High-Risk for the Smaller Party

In most B2B contracts, the limitation of liability clause is written to protect the company sending the contract, not you. Cornell Law's overview of limitation of liability clauses confirms that courts generally enforce these clauses as written unless the cap is so low it effectively excuses bad behavior, which means your best defense is negotiating the clause up front rather than hoping a court will rewrite it later.

Here's the problem: if the vendor makes a catastrophic mistake (a data breach, a missed deadline that costs you a client, a defective product), your recovery is capped at whatever you paid them. If you paid $5,000 for a service and their mistake cost you $200,000, you're out $195,000.

Meanwhile, if you breach the contract (by, say, not paying), there's often no cap on what they can recover from you.

Watch for asymmetric clauses. Some limitation of liability clauses apply to both parties equally. Others apply only to the vendor. If the clause says "Service Provider's liability shall not exceed..." and says nothing about the Client's liability, it's one-sided.

What the Cap Is Usually Set To

Common caps in commercial contracts:

• 12 months of fees paid (most common in SaaS and service contracts)
• The amount paid for the specific deliverable that caused harm (common in project-based contracts)
• A fixed dollar amount ($50,000, $100,000, etc.)
• Insurance coverage amounts (rare but exists in construction and professional services)

The cap matters a lot in context. If you're paying $99/month for software and the cap is 12 months of fees, your maximum recovery is $1,188 no matter what happens.

Exceptions Companies Sometimes Accept

Some damages are so fundamental that courts and sophisticated negotiators carve them out of limitation of liability clauses:

Gross negligence and willful misconduct. It's reasonable to argue that a company shouldn't be shielded from a cap if they intentionally harmed you or were reckless. Some contracts exclude gross negligence and willful misconduct from the cap.

IP indemnification. If the vendor's software infringes someone's patent and you get sued, the limitation of liability clause shouldn't cap your recovery for that specific type of harm.

Confidentiality breaches. Data breaches and confidentiality violations are sometimes carved out.

Death and personal injury. In most jurisdictions, you cannot limit liability for personal injury or death caused by negligence.

How to Negotiate This Clause

If you have leverage, push for:

1. Mutual cap. The cap should apply to both parties equally.
2. Higher cap. Negotiate the cap to reflect your actual risk exposure. If a vendor mistake could cost you $500,000, a $10,000 cap isn't adequate.
3. Carve-outs for serious conduct. Exclude gross negligence, willful misconduct, and data breaches from the cap.
4. Consequential damages for IP and confidentiality. Ask for the right to recover consequential damages specifically in cases of IP infringement or data breach.

If You Can't Negotiate

If the limitation of liability clause is non-negotiable, consider:

• How much could this vendor actually harm you if they fail?
• Does the capped amount roughly correspond to your real downside?
• Can you get additional contractual protections (audit rights, SLAs, termination for cause) that reduce the likelihood of a catastrophic failure?

How This Clause Plays Out in Practice

The stakes of a limitation of liability clause become clearest in concrete scenarios.

SaaS provider outage: A software vendor experiences a 72-hour outage during your busiest sales period. You lose $80,000 in revenue. The contract caps liability at 12 months of fees, which totals $6,000. You can recover $6,000 at most, regardless of your actual loss.

Freelance contractor error: A contractor delivers a website with a security flaw that exposes customer payment data. The total contract value was $15,000, and the clause caps liability at the contract amount. Notifying affected customers, managing regulatory requirements, and restoring systems costs $60,000. The cap leaves you absorbing most of that.

Service provider data handling: A vendor stores your client files and mistakenly deletes them. Recovery costs $25,000. The vendor's monthly retainer was $1,500, making the 12-month cap $18,000. Even with a mutual cap, you may not fully recover.

These scenarios share a common pattern: the cap is sized around the revenue the vendor earns from you, not around the risk they create for your business. The bigger that gap, the more important it is to either negotiate a higher cap or carve out your specific categories of risk.

For a practical overview of other contract provisions that interact with this clause, see 7 clauses to check before signing any contract and the indemnification clause guide.

When This Clause Shows Up in Contracts You Sign Every Day

Limitation of liability clauses are not just in enterprise software agreements. They appear across almost every contract type most people encounter.

Freelance and consulting agreements: Service providers typically include a liability cap limiting their exposure to the fees paid for the specific project. This is a standard protection, not an aggressive move, though the symmetry of the cap (whether it applies to both sides) is still worth checking.

SaaS and software subscriptions: Nearly universal. Almost every SaaS agreement caps the provider's liability at 12 months of fees and excludes consequential damages. These terms are rarely negotiable at small-business pricing tiers but are often more flexible in enterprise contracts.

Vendor agreements: Physical goods suppliers, logistics providers, and service vendors all include limitation of liability clauses. The relevant question is whether the cap is proportionate to the risk you face if the vendor fails.

Employment agreements: Less common in personal employment contracts, but non-disclosure and invention assignment agreements sometimes include provisions that limit the company's liability to the employee in ways that interact with this clause.

Understanding where these caps appear and how they are structured before signing any of these agreements is part of evaluating the real risk of the deal. For a practical walkthrough of what to look for across common contract types, see 7 clauses to check before signing any contract.

FAQ

What does limitation of liability mean in a contract?

A limitation of liability clause caps the maximum amount one party can recover if something goes wrong. It typically excludes indirect and consequential damages entirely and limits direct damages to a fixed amount, often the fees paid in the last 12 months. The purpose is to give both parties predictable financial exposure in a dispute.

Do courts enforce liability caps?

Generally yes, in commercial contracts between businesses. Courts treat limitation of liability clauses as valid allocations of commercial risk. They are less likely to enforce caps that are unconscionably low, that cover gross negligence or willful misconduct, or that appear in consumer contracts where there is a meaningful power imbalance.

What happens if a contract has no liability cap?

Without a limitation of liability clause, either party could potentially be liable for the full extent of damages caused by a breach, including consequential damages like lost profits, lost clients, and reputational harm. For lower-risk agreements this may not matter much. For vendor relationships involving critical data, operations, or significant financial exposure, an uncapped liability structure significantly increases risk on both sides.

See It in Your Contract

Inkvex flags limitation of liability clauses and tells you whether the cap is mutual, how it compares to industry norms, and what damages you'd be giving up.

Upload your contract for a free analysis at inkvex.app, no account, results in under a minute.