What Is a Limitation of Liability Clause?

If you want to understand what a contract actually protects you from — and what it doesn't — the limitation of liability clause is the place to look. It determines, in advance, how much you can recover from the other party if something goes wrong. The cap is often far lower than your actual loss could be.

The Plain-English Definition

A limitation of liability clause sets a ceiling on the total amount one party can recover from the other if things go wrong — regardless of how bad the failure is or how large your actual loss. Even if their mistake causes you $500,000 in damages, if the contract limits their liability to $10,000, that's likely all you can collect.

These clauses are standard in commercial contracts. They're not inherently predatory. The idea is that vendors and service providers shouldn't face catastrophic, unlimited exposure for providing a relatively small, low-margin service. A company charging $50/month for software shouldn't theoretically be on the hook for hundreds of millions of dollars if a bug causes downstream business losses. The clause is the contractual mechanism for managing that exposure.

The problem is when the cap is unreasonably low, when it's written so it only protects one party, or when it's combined with exclusions so broad that practically nothing is recoverable at all.

How Caps Work in Practice

The most common benchmark for a liability cap is the total fees paid under the contract. If you paid a vendor $50,000 over the contract term and something goes catastrophically wrong, they're on the hook for up to $50,000. That's proportional and arguably fair — their revenue from you is the natural limit of their exposure to you.

Here's a spectrum of how to read the common formulations:

What "Consequential Damages Excluded" Actually Means

The dollar cap is only half of what you need to read. The other half is the damages exclusion clause, which almost always appears right alongside it. Look for this language:

Here is what that clause actually does in a real scenario: you depend on a vendor's software to run a core part of your business. Their system goes down for three days due to a bug they introduced. During those three days, you're unable to fulfill orders. You lose $50,000 in revenue, several clients cancel their contracts, and you incur $15,000 in emergency costs to build a workaround.

Under a standard limitation of liability clause with a consequential damages exclusion, almost none of that is recoverable. Your lost revenue is "lost profits" — excluded. The lost client relationships are "loss of business" — excluded. The emergency workaround costs might be recoverable as "direct damages," but the vendor will argue for the cap. You might end up with $300, representing three months of subscription fees.

This is the clause that makes SLA promises meaningless when the stakes are high. The vendor promises 99.9% uptime, delivers 98%, and your remedy under the consequential damages exclusion is a service credit you can apply to next month's bill.

One-Sided vs. Mutual Limitation of Liability

When the limitation of liability clause applies to both parties equally, it's reasonable — you're both giving up the same thing. Many vendor contracts, however, are written so the cap and exclusions apply to the vendor's liability to you, but your liability to the vendor — for unpaid fees, unauthorized use, IP infringement — is unlimited.

The tell is in the grammar. "Our liability to you shall not exceed the fees paid in the prior three months" limits only their liability. "Each party's liability shall not exceed..." is mutual. Always check which party or parties the clause applies to.

What Reasonable and Extreme Language Looks Like

Reasonable:

Extreme:

Can You Negotiate a Limitation of Liability Clause?

Yes — more than most people realize. For enterprise and B2B contracts, the liability cap is one of the most commonly negotiated terms. A few approaches:

• Push for total contract value as the cap, not a rolling three-month window. If you're signing a three-year contract, the cap should reflect that.
• Carve out specific exceptionsfrom the consequential damages exclusion — particularly for data breaches, confidentiality violations, and gross negligence. Even if the vendor won't remove the exclusion entirely, they may agree to carve these out.
• Request mutual application.If the cap applies to both parties, you're on equal footing. If it only caps their liability to you, ask for it to apply symmetrically.
• For mission-critical vendors, consider requiring cyber liability or professional liability insurance at a specified level. A vendor who is insured is more willing to negotiate caps because their insurer is bearing the risk.

When a Limitation of Liability Clause Is Actually Fine

Not every limitation of liability clause is a problem. For high-volume, commodity services — email marketing platforms, document storage, analytics tools — a limitation capped at contract value is entirely reasonable. These vendors serve thousands of customers at low margins and can't be infinitely exposed based on how each customer uses the service.

The clause becomes a problem when the risk it transfers to you is disproportionate to the value of the service, when it's one-sided, or when the cap is so low that it's functionally a waiver of any meaningful remedy. The right question isn't "is there a cap" — it's "is this cap proportional to the actual risk I'm taking on by depending on this vendor?"

For a broader look at where limitation of liability fits alongside other contract patterns, see our 9 contract red flags guide.

The Fine Clause provides document information only — not legal advice. For important decisions, consult a licensed attorney.