Warranty vs indemnity: which one you need

Warranty vs indemnity at a glance

Dimension	Warranty	Indemnity
What it is	An assurance that a stated fact is true (for example, the software does not infringe third-party IP)	A promise to make good a defined loss or liability triggered by a specified event
Primary remedy	Damages for breach of contract	Reimbursement, often a debt-style claim for the covered amount
Measure of recovery	Loss of the bargain, subject to foreseeability limits	The loss defined by the clause, potentially dollar-for-dollar
Causation	Claimant must prove the breach caused the loss	Loss follows from the triggering event named in the clause
Mitigation	Claimant generally must mitigate	May not apply, depending on drafting and state law
Remoteness / foreseeability	Applies (the Hadley v. Baxendale line of cases)	Can be reduced or avoided by clear wording
Third-party claims	Not directly; the promise runs between the parties	Commonly covers third-party claims, settlements, and defense costs
Interaction with the cap	Usually subject to the general liability cap	Frequently carved out or given a separate cap
When it accrues	On breach	When the covered loss or liability is incurred

The key differences

Nature of the promise. A warranty is a statement about the present or the past: the accounts are accurate, the goods meet the specification, the seller owns the asset. If the statement turns out to be false, the warranty is breached. An indemnity does not assert anything. It is a forward-looking allocation of risk that says, in effect, “if this happens, I will pay for it.” That difference in character drives almost everything else.

Remedy and how loss is measured. Breach of warranty produces an ordinary damages claim. The innocent party is put, so far as money can, in the position it would have occupied if the warranty had been true, and recovery is bounded by the usual contract limits: the loss must be caused by the breach, it must not be too remote, and the claimant must take reasonable steps to mitigate. An indemnity can be drafted to sidestep those limits and pay the actual amount of the defined loss, which is why indemnified recovery is often larger and more predictable than a warranty claim for the same underlying problem.

Causation and trigger. Under a warranty, you prove the statement was untrue and that the untruth caused your loss. Under an indemnity, you show that the trigger described in the clause occurred, then quantify the covered loss. A tightly written trigger (for example, “any third-party claim alleging infringement”) can make recovery far more mechanical than litigating whether a warranty was breached and what damages flowed from it.

Third-party exposure. Indemnities are the standard tool for third-party risk. They can cover the liability itself, the cost of settling, and the legal fees of defending, and they can add a duty to defend so the indemnifying party runs the litigation. A warranty gives no direct protection against a claim brought by someone outside the contract; it only supports a claim between the two contracting parties.

Caps, carve-outs, and survival. Because indemnities can be so broad, they are heavily negotiated. Parties often carve high-stakes indemnities (such as IP infringement, data breach, or breach of confidentiality) out of the general limitation-of-liability cap, or give them their own higher cap, baskets, and survival periods. Warranties are usually swept inside the general cap and may carry shorter survival windows. Anti-indemnity statutes in some states also restrict how far certain indemnities can reach, particularly in construction.

Limitation timing. A breach-of-warranty claim generally accrues when the breach happens, which can be at or near signing or delivery. An indemnity claim may accrue only when the covered loss is actually incurred, which can be much later. That timing gap can decide whether a claim is still alive.

Which one to use, and when

Use a warranty when you want a party to stand behind the truth of specific facts and you are comfortable with the normal contract-damages framework. Warranties are the natural home for statements of condition, quality, ownership, authority, and compliance.

Use an indemnity when you want certainty of recovery, when the risk involves third-party claims or defense costs, or when the potential loss would be hard to recover as ordinary damages because of remoteness or mitigation rules. Indemnities are the right tool for IP infringement, data protection, tax, and specific known liabilities you want the other side to absorb in full.

In practice most well-drafted agreements use both: a warranty establishes the standard, and a matching indemnity guarantees the recovery if that standard fails. When you pair them, spell out how they interact so the counterparty cannot recover twice for the same loss, and align each with the cap. A compliance playbook in a CLM platform such as Pactolane can flag when an indemnity is uncapped or missing a defense obligation, and PactAI exposure analysis and risk scoring can estimate the dollar range at stake, but the human negotiator decides the final position.

Decision rule: if you need someone to promise that something is true, use a warranty; if you need someone to pay for a defined loss in full and without the usual damages limits (especially a third-party claim), use an indemnity, and when the risk is material, use both and cap them deliberately.