Clause explained · free
Limitation of Liability Clause: What It Means & Why It Matters
Buried near the end of most contracts is a clause that quietly decides how much money changes hands if something goes badly wrong. It rarely gets read closely — which is exactly the problem.
The limitation of liability clause sets a ceiling (or a floor of protection) on how much one party has to pay the other if they mess up. Understanding it matters because it can turn a costly mistake into a minor inconvenience — or the other way around, depending on which side of the cap you're on.
This is one clause — your contract has dozens.
A limitation of liability clause rarely sits alone. Upload the whole contract and PlainClause reviews every clause in plain English — what you’re signing, the red flags, and what to negotiate. Your first preview is free.
Get your free review →What is a Limitation of Liability Clause?
A limitation of liability clause caps the amount of money one party can be forced to pay the other if something goes wrong — a breach, an error, a missed deadline, a security failure, whatever the contract covers. Instead of leaving damages open-ended (which is the default under general legal principles), the parties agree in advance on a ceiling, and often on which types of losses are excluded entirely. It shows up in almost every commercial contract — freelance agreements, software licenses, service contracts, vendor deals — because without it, either side could theoretically be on the hook for damages far larger than the value of the deal itself.
How it typically reads
A standard version says something like: 'In no event shall either party's total liability exceed the total fees paid under this agreement in the preceding twelve months.' It usually pairs with a second sentence excluding 'indirect, incidental, consequential, or punitive damages' — things like lost profits, lost business opportunities, or reputational harm.
Some clauses cap liability at a fixed dollar amount instead of tying it to fees paid. Others carve out exceptions — certain types of claims (like confidentiality breaches or gross negligence) that aren't subject to the cap at all.
Who it tends to favour
In theory, a mutual cap protects both sides equally. In practice, it usually favours whoever drafted the contract and whoever is providing the service or product — because they're the one most likely to make a mistake that causes the other party financial harm.
If you're the client paying for a service, a low liability cap can leave you badly exposed: if a vendor's failure costs you far more than what you paid them, you may only be able to recover a fraction of your actual loss. If you're the service provider, the same clause protects you from being wiped out by one bad contract.
How it plays out in practice
Say a freelance developer is paid $5,000 to build a feature, and a bug in their code causes $200,000 in losses for the client. If the contract caps liability at fees paid, the developer's exposure is $5,000 — not $200,000. For the developer, that's the whole point of the clause. For the client, it means eating the other $195,000 themselves, or trying to recover it another way (which is often difficult or impossible).
This is why the size of the cap matters more than whether a cap exists. A cap set at total fees paid is very different from a cap set at ten times the fees, or one with no cap at all for certain kinds of harm.
How it's sometimes negotiated
Common negotiation moves include raising the cap (e.g., to a multiple of fees paid, or a fixed higher amount), carving out specific exceptions where the cap doesn't apply (confidentiality breaches, IP infringement, gross negligence, willful misconduct), or making the cap mutual if it currently only protects one side.
Some parties also negotiate insurance requirements alongside the cap — requiring the other party to carry a minimum level of liability insurance, so there's a real source of funds behind the number on the page.
When this clause works against you
No cap at all, or liability described as 'unlimited'
You could be on the hook for the full financial impact of any mistake, however large, with no ceiling in sight. This is rare but appears in poorly drafted or one-sided contracts, and it deserves serious scrutiny.
The cap only protects one party, not both
If the clause caps what you can recover from the other side but doesn't cap what they can recover from you, the risk allocation is lopsided — you carry more downside than they do.
Cap is set very low relative to the potential damage
A cap tied to a small fee amount can leave the injured party recovering a tiny fraction of their actual loss, especially in contracts where the service touches sensitive data, critical systems, or large sums of money.
Broad carve-outs that swallow the cap
If the exceptions to the cap are written broadly (e.g., 'any breach of this agreement' rather than a specific serious event), the cap may not actually protect anyone — the exceptions could cover almost every scenario.
Cap excludes 'indirect and consequential damages' without defining them
These terms sound technical but have real consequences — lost profits and lost business opportunities are often the biggest real-world losses from a failure, and excluding them can gut what's actually recoverable.
Liability cap paired with an uncapped indemnification clause
A liability cap can be quietly undone if a separate indemnification clause requires you to cover the other party's losses without any limit — check whether the two clauses actually work together.
Cap tied to a stale or unclear number
A cap set at 'fees paid in the prior 12 months' means something very different in month one of a contract versus year three — and vague phrasing about which period counts can create disputes later.
What to check when you see this clause
- Is there a liability cap at all, and if so, what's the dollar figure or formula?
- Does the cap apply equally to both parties, or only to one side?
- Is the cap tied to fees paid — and if so, over what time period?
- What types of damages are explicitly excluded (lost profits, consequential damages, etc.)?
- Are there carve-outs where the cap doesn't apply — and are they narrow or broad?
- Does a separate indemnification or confidentiality clause create liability that bypasses this cap entirely?
- Is the cap size reasonable relative to the actual risk and value of the contract?
- Is there an insurance requirement that backs up the numbers in this clause?
Seeing a limitation of liability clause in a contract you’re about to sign? PlainClause reviews the whole document in about a minute.
Review your contract free →Frequently asked questions
What is a limitation of liability clause?
It's a contract clause that sets a maximum amount one party has to pay the other if something goes wrong, like a breach or a mistake that causes financial harm. It often also excludes certain categories of damages, like lost profits, from being recoverable at all.
Why do contracts include a limitation of liability clause?
Without one, a party's financial exposure for a breach could be unpredictable and potentially far larger than the value of the deal. The clause lets both sides know in advance roughly how much is at stake if things go wrong.
Is a limitation of liability clause enforceable?
Generally yes, but enforceability can depend on where you are and the specific type of harm involved — some jurisdictions won't enforce caps for things like gross negligence, willful misconduct, or certain safety violations. This varies, so it's worth checking your specific situation rather than assuming the clause is airtight.
What's a reasonable liability cap?
There's no universal number — it depends on the size of the contract, the risk involved, and industry norms. A common starting point is fees paid over a set period, though higher-risk contracts (like those involving sensitive data) often justify a higher cap or carve-outs.
Can a limitation of liability clause be negotiated?
Yes, this is one of the more commonly negotiated clauses in commercial contracts. Common changes include raising the cap, making it mutual, or adding carve-outs for serious issues like data breaches or IP infringement.
Key takeaways
- A limitation of liability clause caps how much one party can be forced to pay the other if something goes wrong — instead of leaving damages open-ended.
- The existence of a cap matters less than its size, whether it's mutual, and what's carved out from it.
- Watch for one-sided caps, broad exclusion of consequential damages, and carve-outs that quietly undo the protection the cap is supposed to offer.
- Check how this clause interacts with any indemnification clause — an uncapped indemnity can bypass the liability cap entirely.
- Enforceability can vary depending on where you are and the type of harm involved, so don't assume the number on the page is the final word.
More guides
This guide is general information to help you understand a common type of contract — it is not legal adviceand doesn’t cover your specific situation or local laws. For a high-stakes contract, consult a lawyer.