Agency image copyright liability: who pays, you or the client?

If an unlicensed image ends up on a client website, the site owner is generally the primary target of a copyright claim, but the agency or freelancer who placed the image can be named too, especially when the contract lacks a clear indemnification clause. In practice, rights holders and enforcement firms often send demand letters to whoever is easiest to identify and whoever appears to have deeper pockets, which sometimes means the agency. Your protection comes down to two things: the license paperwork behind every image and the indemnification language in your client agreement.

Below we break down who is actually liable, why "the client bought the stock license" is not the safe answer agencies think it is, and how to run a quick copyright QA pass before you ship deliverables.

Who is legally liable for an infringing image?

US copyright law does not hand out a single "guilty party." Direct infringement can attach to anyone who reproduces, distributes, or publicly displays a protected work without permission. On a live website, that usually means the entity that owns and operates the site, because they are publishing the image to the public.

But agencies are not shielded just because they are one step removed. Two doctrines matter here:

• Contributory infringement: knowingly causing or materially contributing to someone else's infringement. Selecting and installing an unlicensed image on a client's site can fit this description.
• Vicarious infringement: having the right and ability to control the infringing activity and a direct financial interest in it. An agency being paid to build and manage the site can check both boxes.

The practical takeaway: when a demand letter goes out, the rights holder does not have to pick just one defendant. Agencies get named alongside their clients more often than most operators expect. And even if you are eventually dismissed, the cost of getting there is real.

What the financial exposure looks like

Copyright is not a "pay the license fee you skipped" situation. Under 17 U.S.C. 504, statutory damages for registered works run from $750 to $30,000 per work, and up to $150,000 per work for willful infringement. "Per work" matters: five unlicensed photos on a portfolio page is five separate claims, not one.

Most matters never reach a courtroom. They arrive as a demand letter from an enforcement firm like Higbee & Associates or PicRights, or as a claim filed with the Copyright Claims Board (CCB), the US small-claims tribunal for copyright disputes. Getty and similar agencies find infringing use with perceptual-hash crawlers such as PicScout, which fingerprint an image and then scan the open web for visual matches, even cropped or lightly edited ones.

If you want the full anatomy of one of these letters, our Getty Images demand letter guide walks through what a typical letter demands and how recipients usually respond.

Why "the client has a stock license" is not enough

This is the single most common misunderstanding in agency work. A stock license is almost always tied to the purchasing account, not to the finished asset or the person who will host it.

Say your freelancer buys a Shutterstock or Adobe Stock image under the agency's account and drops it into a client's homepage. Unless that license permits sublicensing or you execute a proper assignment or extended license, the client is not actually licensed. The image is licensed to you, and you handed it to a third party. That is a gap the rights holder can exploit.

A few license traps that trigger claims:

• Editorial-only licenses used commercially. Editorial stock cannot be used to sell or promote a product. Putting an editorial image on a product page is a violation even though the download was "legitimate."
• Watermarked comps in deliverables. Dropping a watermarked preview image into a mockup, a pitch deck, or worse, a shipped page, is a license violation. Because it is unlicensed use by definition, it is the kind of conduct that can support the enhanced, willful-infringement damages tier.
• Expired or seat-limited subscriptions. A subscription that lapsed, or one licensed for a single user or single project, does not stretch to cover every client site you have ever built.
• AI-generated images assumed to be "free." AI output raises its own copyright questions and can still reproduce protected elements. See our note on AI-generated images and copyright before treating them as risk-free.

Because stock accounts rarely transfer cleanly, the safest posture is to license per project under the client's own account, or to buy an extended license that explicitly covers the end use and end user, and to keep the receipt.

Indemnification clauses: the line that decides who pays

When a demand letter lands, the contract, not copyright law, usually decides who absorbs the cost. That decision lives in the indemnification clause.

Two directions this clause can point:

• Agency indemnifies client. You promise the deliverables do not infringe and you will cover the client's costs if they do. Clean for the client, heavy exposure for you.
• Client indemnifies agency. The client takes responsibility for assets and approvals, and covers your costs. Better for you, harder to get signed.

Most real agreements land somewhere in between, and the details do the work. Here is how the common structures compare:

Contract structure	Who absorbs a demand letter	Best for	Watch out for
Agency indemnifies client (broad)	Agency	Winning risk-averse enterprise clients	Unlimited exposure if you have no liability cap
Mutual indemnification	Whoever caused the issue	Balanced agency/client relationships	Ambiguity over who "caused" a mixed-asset page
Client indemnifies agency for client-supplied assets	Client (for their images), agency (for yours)	Agencies that only place licensed or client-provided media	Requires clear tracking of asset origin
No indemnification clause	Undefined, decided by law and leverage	Nobody	Rights holder targets whoever is easiest to reach

Two protections belong in almost every agency contract regardless of direction: a liability cap (often tied to fees paid) and a carve-out that excludes client-supplied assets from your warranty. If the client hands you the images, you should not be warranting that images you never sourced are clean.

None of this is legal advice, and clause wording should be reviewed by a lawyer licensed in your state. The point is simpler: know which way your indemnification points before you sign, because that is the sentence that decides who writes the check.

How to run a copyright QA pass before handoff

The cheapest demand letter is the one you prevent. A short QA routine before delivery catches the images most likely to generate a claim. Build it into your handoff checklist:

1. Inventory every image and its origin

List each image on the deliverable and where it came from: client-supplied, purchased stock (with license type and account), original photography, or AI-generated. If you cannot name the source, treat it as high risk until you can.

2. Match licenses to actual use

Confirm the license permits the specific use. Commercial vs editorial. Web display vs print. Single project vs multi-client. Note whether the license is under the client's account or yours, and whether it transfers.

3. Scan for the risk signals a human eye misses

Some of the highest-risk images look completely clean at a glance. A comp watermark can be faint, a stock fingerprint is invisible, and metadata clues are buried. A per-image risk scan surfaces these fast. PixGuard crawls the images on a page (or a single upload) and flags copyright-risk signals: visible and invisible watermarks, stock-agency fingerprint matches, AI-generation markers, EXIF and metadata clues, and reverse-image source lookup, then returns a per-image risk score. On paid plans it adds likely source attribution so you can trace where an image probably originated.

Important framing for your own peace of mind and your client's: a scan flags images for review and estimates risk. It does not confirm infringement and it is not a legal opinion. It tells you which images deserve a closer look before you ship, which is exactly what a QA pass is for.

4. Document the sign-off

Keep the scan output and license receipts with the project file. If a claim ever arrives, being able to show that you ran a copyright QA pass and sourced licensed assets is far better than reconstructing it under pressure.

For a deeper walkthrough of auditing a full site rather than a single deliverable, see how to audit a website for copyrighted images. And if you are weighing whether a free checker is enough for agency workloads, free vs paid copyright tools compares what each tier actually catches.

A quick agency risk-reduction checklist

• License images under the client's account, or get an extended license and assignment that names the end use.
• Never ship a watermarked comp, even in a mockup that "will get replaced later."
• Put a liability cap and a client-supplied-asset carve-out in every contract.
• Read which way your indemnification clause points before signing.
• Run a per-image risk scan on the final deliverable and keep the receipts.

Frequently Asked Questions

Can an agency be sued if the client's site infringes?

Yes. While the site owner is usually the primary target, agencies are frequently named too under contributory or vicarious infringement theories, especially when the agency selected, installed, or manages the images. Your contract's indemnification clause, not just copyright law, often determines who ultimately pays.

Does a stock license transfer from the agency to the client?

Usually not automatically. Stock licenses are typically tied to the purchasing account. To cover the client you generally need sublicensing rights, an extended license that names the end user, or a written assignment. Buying under the client's own account is the cleanest option.

Is using a watermarked comp image really infringement?

Yes. A watermarked comp is a preview, not a license to publish. Using it in a shipped deliverable is unlicensed use, and because it is clearly outside any granted right, it is the type of conduct that can support enhanced, willful-infringement damages under 17 U.S.C. 504.

Who pays a Getty or PicRights demand letter, the agency or the client?

Copyright law can attach to both, but the contract usually decides who absorbs the cost. An indemnification clause pointing at the client shifts it to them, one pointing at the agency shifts it to you, and no clause at all leaves it to law and leverage, which often favors the rights holder.

Can a scan tool tell me an image is definitely infringing?

No, and you should be wary of any tool that claims it can. A risk scanner flags images for review and estimates copyright risk from signals like watermarks, stock fingerprints, AI markers, and metadata. Confirming infringement is a legal determination. The value of a scan is catching risky images before delivery so a human can review them.

Ship deliverables you can stand behind

Agency liability is mostly about paperwork and process: licensed assets, a contract that points indemnification the right way, and a QA pass that catches the images most likely to draw a letter. The scan is the fastest of those to add.

Run a free scan on your next deliverable or a client's live site at PixGuard. The free tier covers about 30 image scans with no credit card, enough to pressure-test a page before you hand it off.