The right to dispute
You have the right to dispute the claim and to defend your use. An allegation does not become a debt because it arrived with a reference number and a countdown.
Independent educational resource
Received an image copyright claim?
Preserve first. Identify how the image was selected and delivered. Ask for the evidence before admitting liability or treating a demand amount as established.
Immediate response steps
- 1
Preserve
Keep the notice, page, source, tags, network route, logs, cache records, and terms before they change.
- 2
Verify the sender
Confirm the claimant, representative, and payment recipient are genuine before paying or replying with facts.
- 3
Classify
Distinguish an ordinary demand from a DMCA notice, subpoena, Copyright Claims Board claim, or lawsuit.
- 4
Demand proof
Request ownership, authority, registration, capture, delivery-route, damages, and release evidence.
- 5
Respond without admitting
Send a dispute + evidence-request letter: the claim is disputed and unsubstantiated, nothing is admitted, full substantiation is requested. Then evaluate defenses with counsel.
Know this before anything else
A demand letter is not a court order. You have rights.
A payment deadline in a letter is the sender’s wish, not a legal ruling. Until a claim is proven in a proper forum or you agree to settle, nothing is established — and exercising the rights below is standard, legitimate practice, not aggression.
The right to see the evidence
You have the right to see the evidence and to request every detail before paying: proof of ownership and chain of title, the registration, the sender’s written authority to settle, the exact URLs and captures, the technical theory, the alleged display period, and the basis for the amount. A claimant seeking money can be asked to substantiate — and payment can wait until they do.
The right to admit nothing
You have the right to say nothing that admits liability, ownership, copying, or damages while you investigate. A professional no-admission response protects you; silence and panic-payment do not.
The right to counsel
You have the right to be represented — you may hire a lawyer at any point, and for a lawsuit, subpoena, or Copyright Claims Board matter you genuinely need one. Consulting counsel is not an admission of anything.
The right to verify
You have the right to verify the sender, the claimed owner, any named lawyer, and the payment recipient through independent channels before engaging — and to refuse payment to anyone who fails verification.
The right to settle on real terms
If you choose to resolve the matter, you have the right to a complete written release naming every released party, domain, work, and claim — and to negotiate the amount against real comparable licenses, not a number on a portal.
A demand is an allegation—not a judgment
Some claims are valid. Others may be incomplete or based on a mistaken understanding of how a preview was selected, stored, or transmitted. An ordinary pre-suit demand does not always have to include litigation-level proof, and missing documents do not automatically invalidate a claim.
Do not ignore it
Calendar every stated date, preserve evidence, and determine whether formal process has begun.
Do not admit prematurely
Do not assume ownership, copying, display, willfulness, damages, or the absence of authorization or fair use.
Do not accuse publicly
Describe allegations and evidence neutrally. This site is not affiliated with any claimant, rights holder, enforcement representative, platform, publisher, or law firm and does not accuse any of misconduct.
Why do platforms and Google News seem free to show the same previews?
When someone shares a link on a social platform, the platform renders a small preview image, a headline, and a link — the same shape a news aggregator renders. The platforms are not relying on a special copyright exemption unavailable to everyone else; they rely on a mix of legal and practical positions that any recipient of a demand should understand.
Publisher-supplied metadata
Publishers add og:image, X Card, and JSON-LD tags precisely so that link previews are generated. Sharing on a platform is an invitation the publisher extends through its own markup. An aggregator reading the same tags has a similar factual account — but metadata is not an automatic license, for platforms or for anyone else.
Terms and the server test
Official platform embeds run under the provider’s published terms, and in the Ninth Circuit the “server test” (Perfect 10 v. Amazon, applied to embeds in Hunley v. Instagram) can defeat a direct display theory when the image bytes come from the platform’s own servers. That doctrine is jurisdictionally limited and does not resolve reproduction or every secondary theory.
Scale, licenses, and risk choices
Google News historically showed headlines, snippets, and links, and Google has since signed licensing deals with many publishers. Large platforms also carry legal teams, safe-harbor procedures, and negotiated agreements. Their apparent freedom reflects those positions — not a rule that aggregation by others is unlawful.
The aggregation defense, explained
A small preview with a headline and a link is a discovery card, not a poster
The strongest version of the aggregation position describes a specific format: a reduced-size image the publisher itself designated for sharing, shown beside the headline, attribution, and a direct link to the original article — the format every social feed renders. That format matters under each fair-use factor, including the “news reporting” purpose expressly listed in the preamble of 17 U.S.C. § 107. It is supporting material for a defense — not an automatic pass.
1. Purpose
News discovery, indexing, and navigation point readers to the source rather than substituting for it. Automated selection from the publisher’s own sharing metadata supports a discovery purpose, and “news reporting” is an enumerated § 107 purpose — though courts have not treated aggregation as news reporting in itself (see the Meltwater row below); the inquiry looks at what your specific use did.
2. Nature
Published news photographs still receive protection, but published, factual-context works weigh differently than unpublished, highly creative ones.
3. Amount — size matters
A reduced-resolution thumbnail uses less of the expressive value than the full image. Thumbnail size was central to the outcomes in Kelly v. Arriba Soft and Perfect 10 v. Amazon.
4. Market effect
A preview that drives clicks to the original is the opposite of a substitute. A full-size copy readers can consume in place — or download — replaces the market and weighs against fair use.
Build the defense from facts: the defense-builder
| Fact to establish | Evidence to preserve | Why it matters |
|---|---|---|
| The displayed image was a small preview | Screenshot with visible context, rendered pixel dimensions, CSS size, and the served file’s resolution. | Factor 3 (amount) — the thumbnail cases turn on reduced size and resolution. |
| The image was auto-selected from the publisher’s own tags | Source HTML, raw og:image/X Card/JSON-LD/oEmbed responses, crawler logs, and the code path that consumed them. | Factor 1 (purpose) and the factual account: the publisher supplied this image for exactly this preview use. |
| Headline, attribution, and a direct link were shown | Full-page capture showing the headline, source name, and working link to the original article. | Factors 1 and 4 — a discovery card sends readers to the source instead of replacing it. |
| No standalone or full-resolution download was offered | Page capture and code showing no click-through to a full-size copy hosted by you. | Factor 4 (market) — no substitute for the original or for a license. |
| The image has since been disabled, with headline and link kept | Dated removal record, deploy log, and an archived copy of the page before and after. | Mitigation and willfulness — risk reduction without admitting anything, though it does not by itself resolve a monetary demand. |
| Which server transmitted the bytes | HAR/network trace, request initiator, redirect chain, and the delivery host. | Determines whether the original-source-URL analysis (server test, where it applies) or the cached-copy analysis governs. |
| The display period was brief (a rotating feed slot, a short cache TTL) | Feed-rotation schedule, cache TTL and purge records, deploy logs, and dated captures bracketing the window. | Factor 4 and damages — a transient preview is far less likely to substitute for the original, and exposure scales with duration. Duration is supporting material, not a standalone defense: even brief displays can raise copyright questions, and where statutory damages are available, exposure does not scale simply with duration. Evidentially, a claimant’s screenshot proves a moment, not a period — request their evidence of the alleged display period rather than asserting a number your logs cannot support. |
What the cases actually held
| Case | Holding on its facts | What it does not prove |
|---|---|---|
| Kelly v. Arriba Soft (9th Cir. 2003) | A search engine’s reduced-size thumbnails of photographs were fair use: transformative indexing purpose, small size, no market substitution. | Not a rule that every thumbnail is fair use; the court analyzed a search-and-index purpose, not decoration or republication. |
| Perfect 10 v. Amazon (9th Cir. 2007) | Search thumbnails again favored fair use, and the “server test” defeated a direct display claim for full-size images served from third-party servers. | The server test is Ninth Circuit doctrine, does not decide reproduction claims, and other circuits have not all adopted it. |
| Hunley v. Instagram (9th Cir. 2023) | Reaffirmed the server test for embedded content: embedding an image served by the platform was not direct display infringement. | Limited to the Ninth Circuit and to the display right; contract, authorization, and secondary-liability questions remain. |
| Authors Guild v. Google (2d Cir. 2015) | Mass digitization to power search and snippets was transformative fair use — indexing that points users to works rather than substituting for them. | Books and snippets, not news photographs; snippet limits and access controls were central to the outcome. |
| AP v. Meltwater (S.D.N.Y. 2013) | A paid clipping service that delivered article excerpts to subscribers lost fair use: commercial substitution for the originals, not discovery. | The boundary case: “aggregation” framing fails when the product replaces visiting or licensing the source. |
| Brammer v. Violent Hues (4th Cir. 2019) | A website’s unlicensed use of a found photograph for the same illustrative purpose was not fair use; “I found it online” carried no weight. | Shows what the aggregation defense is not: manual selection, same purpose as the original, no transformation. |
| Warhol v. Goldsmith (U.S. 2023) | Factor 1 now turns on whether the specific use shares the same purpose as the original and is commercial — narrowing loose “transformativeness” claims. | It did not overturn the thumbnail cases, but same-purpose commercial image use now needs a clearly distinct justification. |
Fair use for news discovery and aggregation
Fair use is a fact-specific defense under 17 U.S.C. § 107. The party asserting fair use generally bears the burden of proving it. No fixed thumbnail size, word count, attribution practice, or “aggregator” label decides the result.
| Fair-use factor | Questions to investigate | Evidence to preserve |
|---|---|---|
| 1. Purpose and character | Was the use search, indexing, reporting, commentary, navigation, or a substitute for the original? What did the page add? | Headline, excerpt, attribution, source link, editorial context, rendered size, automation, and business model. |
| 2. Nature of the work | Was the photograph published and informational, or highly creative and unpublished? | Publication history, caption, subject, photographer information, and claimed licensing terms. |
| 3. Amount used | Was a reduced preview reasonably necessary? Was the complete expressive image still visible or separately downloadable? | Pixels, crop, compression, CSS size, screenshots, source files, and download routes. |
| 4. Market effect | Did the preview direct readers to the source or substitute for a normal image license, article subscription, clipping service, or full-resolution market? | Clicks, impressions, access to full-size media, comparable licenses, lost sales, and product positioning. |
Facts that may strengthen the argument
- Reduced, low-resolution small preview used for news discovery or navigation.
- Automated selection from source-supplied metadata or an official embed.
- Headline, source attribution, and direct link to the original publication.
- No standalone high-resolution download and no market substitution.
- Context explains, indexes, comments on, or points readers to the underlying news.
Facts that may weaken the argument
- Full-size or high-resolution use serving the same purpose as the original.
- Permanent local copy, manual selection, decorative use, or removed attribution.
- Substantial copied article text or an experience that replaces visiting the source.
- Paid clipping, image-library, or syndication competition.
- Ignoring provider limits, removal requests, or obvious rights information.
Preserve before systems change
Preserve first, then consider disabling or removing the challenged display. One common mitigation: disable the preview image while keeping the headline, attribution, and link to the original article. Done after preservation and described neutrally, that reduces ongoing exposure without admitting the allegation — though it does not by itself resolve an existing monetary demand.
Before paying anything
Verify the sender and the demand are genuine
Image demands are often mass-generated, and impersonation scams copy their format. Verify the sender independently before paying, replying with facts, or clicking portal links. Verification helps separate the two — treat a sender that fails it as unsafe to pay, and remember that passing a basic check is not proof of legitimacy either.
1. Preserve the original message
Save the email with complete headers, attachments, envelope, portal URL, invoice, reference number, payment instructions, and every follow-up.
2. Verify the sender independently
Do not rely on the phone number, link, or address inside the demand. Find the purported organization through an independent source and confirm it sent the communication.
3. Inspect the domain and email
Check for misspellings, look-alike characters, recently created domains, unexpected reply-to addresses, odd redirects, and mismatches between the claimed organization and the payment recipient. None of these alone proves fraud.
4. Verify the claimant and representative
Request the owner’s legal identity, the claimed work, chain of title, registration information, and written authority allowing the representative to investigate, negotiate, settle, release, and — if asserted — litigate.
5. Verify any lawyer independently
If the message claims to come from an attorney, check the firm’s official contact information and the applicable bar directory, and contact the verified office — not the contact details supplied in a suspicious message.
6. Verify the work and registration
Search the Copyright Office public records and ask for enough information to identify the asserted image within any individual or group registration. An absent search result does not by itself disprove ownership.
7. Verify payment instructions
Do not send money because a portal shows a countdown. Independently confirm the legal recipient, amount, currency, account details, and authority to settle. Treat demands for payment by cryptocurrency, gift card, personal money-transfer account, or an unrelated recipient as significant warning signs.
8. Protect sensitive information
Do not send passwords, access tokens, identity documents, banking credentials, customer data, or privileged communications to an unverified sender.
9. Require a written release
Before settling, require a written agreement identifying the correct owner and authorized representative, the specific work, the alleged use, the amount, every released person, domain, URL, claim, and remedy — and, if negotiated, no admission of liability.
10. Fraud vs. incomplete claim
A legitimate sender may initially provide incomplete evidence. Missing evidence does not automatically make the communication fraudulent — request substantiation and evaluate the response.
11. Report actual fraud safely
If reliable evidence indicates impersonation, fraudulent payment instructions, or phishing, preserve the evidence and consider reporting via the FTC (reportfraud.ftc.gov) or the FBI IC3 (ic3.gov), plus your bank, email provider, host, local authorities, or counsel as circumstances warrant.
12. Do not miss formal deadlines
Suspected fraud does not justify ignoring formally served court papers, a subpoena, or a Copyright Claims Board matter. Verify formal process independently and obtain qualified counsel promptly.
Claim substantiation gate
Request the evidence before building the defense
Do not admit liability, pay, or treat the stated amount as established merely because a letter provides a deadline. At the same time, an ordinary pre-suit demand may not be required to attach every item needed in litigation, and missing material does not automatically invalidate the allegation.
Burden boundary: A claimant generally must prove ownership and actionable infringement. A defendant generally bears the burden of proving fair use. Other defenses and procedural burdens vary.
- Work, owner, and authority: the exact work, photographer/author, owner, chain of title, exclusive rights asserted, registration, group-registration identification, and the representative’s authority to investigate, negotiate, settle, release, and—if claimed—litigate.
- Every relevant URL: alleged page URL, source article or social-post URL, original image asset URL, oEmbed/Open Graph/X/JSON-LD/API/feed image URL, browser request and final redirect URL, and any cache, proxy, CDN, or storage URL.
- Delivery and capture: the server said to have transmitted the bytes; timestamps and time zone; complete screenshots; source HTML/HTTP archive; oEmbed/API response; headers; crawler logs; file dimensions, hash, and chain of custody.
- Alleged display period: evidence establishing when the display began and ended. A single capture establishes a moment, not a period — repeated dated captures or equivalent records are needed to allege a duration.
- Technical theory: whether the claimant alleges upload, reproduction, cache, proxy, hotlink, embed, display, transmission, or distribution, and which person or system allegedly caused each act.
- Authorization and fair-use position: the basis for rejecting authorization or fair use in light of source-supplied metadata or embeds, reduced size, attribution, headline, excerpt, source link, news-discovery purpose, and any absence of standalone download or market substitution.
- Notice history: all prior notices, recipients, delivery methods, attachments, and delivery records.
- Damages and resolution: the calculation, ordinary rate, materially comparable arm’s-length licenses, alleged lost sales, attributable profits, multipliers or fees, and a proposed release identifying every released party, domain, work, act, and claim.
“The materials presently provided are insufficient to establish ownership, authority, actionable copying or display, the alleged delivery method, damages, or the absence of authorization or fair use. The claim remains unsubstantiated pending production of the requested information.”
Slow down — follow the process
You do not need to rush to pay. Follow the process.
A payment date stated in an ordinary letter or portal is not a court-imposed deadline, though it can carry practical consequences — an offer can expire and a matter can escalate. Formal court, DMCA counter-notice, or Copyright Claims Board dates are different: verify those independently and meet them. For an ordinary demand, the safe path is a process, and negotiation at the end of it is a normal, expected part of how these matters resolve.
1. Verify, preserve, classify
Run the sender-verification checklist, preserve your evidence, and confirm what you actually received before any substantive reply. If you or your business carries general, media, or cyber liability insurance, check the policy’s claim-notice requirement now — late notice can forfeit coverage.
2. Demand the details
Send the no-admission letter requesting full substantiation — ownership, registration, authority, captures, delivery route, display period, and the basis for the amount. Their response (or silence) tells you what the claim is really made of.
3. Then decide — with leverage
Only after seeing their evidence: seek withdrawal, negotiate in writing toward a documented settlement with a complete release, or defend with counsel. Negotiation is normal — amounts are often negotiable, and an offer to compromise is generally protected; while negotiating, avoid statements of fact you have not verified, since factual admissions may not be.
Research the public record
Check the registration — it decides what the claim can be worth
Under 17 U.S.C. § 412, statutory damages and attorney's fees are available only if the work was registered with the U.S. Copyright Office before the infringement began, or within three months of the work's first publication. Registration records are public and free to search. Whether that timing test is met is often the single largest factor in what an ordinary demand is realistically worth — and you can research it yourself before paying or replying with facts.
- Collect the identifiers. From the demand: the image or catalog ID, any file name, the photographer, the named owner, and the date the source article or image was first published. From your own records: when the display on your site began (your first notice from the claimant is a useful latest-possible date).
- Search the Copyright Office public records at publicrecords.copyright.gov — with two different IDs. First, the claimed ID: the image or catalog number printed in your demand letter; keyword-search it exactly as written (and any plausible misreadings — 1/I, 6/G, 0/O — if it came from a scanned letter). Second, a control ID: open one of the owner's older registration records (find them with a name search for the claimed owner) and pick any photo ID listed inside a group registration. Search that control ID too. If the control comes back — proving the index really does find individual photo IDs inside group deposits — a zero result for the claimed ID means something. Without the control, a zero result might just mean the index doesn't work that way.
- Read the owner's registration pattern. Group records show the publication window each one covers. Note the most recent covered date — bulk registration programs can stop years before the image you are accused over was published, and a gap covering your image's publication year is a significant finding.
- Apply the § 412 timing test. Was any registration covering the image effective before the alleged infringement commenced, or within three months of the image's first publication? Both dates matter; write them down with sources.
- Draw the conclusion carefully. If no timely registration appears, the law's two heaviest remedies — statutory damages and attorney's fees — are off the table, and recovery is limited to actual damages: in practice, a reasonable license for the actual use, which for a small preview image is usually modest. If a timely registration does appear, statutory damages become available in an amount a court decides within the limits of § 504(c) — and the same facts you gathered (automated selection, reduced size, attribution, a link to the source, brief display) argue for the bottom of that range; where the infringement was innocent, the law lets a court reduce the award to a nominal sum.
- Compare the entities. The claimant of record on the registration may be a different legal entity than the one named in the letter. If the names differ, add a chain-of-title question to your evidence request: which entity owns the work, and where is the assignment?
Foreign-origin works
U.S. law fully protects foreign works — do not assume a foreign photograph is unprotected. The nuance is procedural: § 412's bar on statutory damages and fees applies to works of foreign and domestic origin alike, while § 411(a)'s register-before-suing requirement applies only to "United States works." A work first published abroad may support a suit without registration — but still without statutory damages or fee-shifting if registration was not timely. Whether simultaneous online publication makes a work a "United States work" is unsettled; raise it with counsel.
What the economics mean
Federal copyright litigation is expensive for both sides, and a claimant without statutory damages or fee-shifting carries its own legal costs to pursue a recovery about the size of a license fee. The small-claims alternative — the Copyright Claims Board — is voluntary for a respondent (there is an opt-out window) and its awards are capped by statute at small-claims scale. None of this makes a claim invalid; it frames what a proportionate resolution looks like.
Limits of a records search
The index is built from applicant-supplied data, pending applications are not visible, and a group's full deposit list may be only partly indexed — so a zero result puts the claimant to its proof; it is not proof of non-registration. Ask the claimant in writing for the registration number, its effective date, and identification of the image within any group deposit. If the matter escalates, a formal Search Report from the Copyright Office's Records Research and Certification Division is the citable version.
Classify the notice before responding
Different documents create different risks and procedures.
Ordinary demand
A private allegation and settlement request. Preserve, investigate, request substantiation, and evaluate the practical response date.
DMCA notice
Compare it with 17 U.S.C. § 512(c)(3), your service-provider procedure, and any counter-notice risks. Lenz v. Universal holds that a sender must consider fair use before issuing a DMCA takedown notice.
CCB claim
A Copyright Claims Board matter has official service and procedural deadlines. Do not confuse it with an informal demand or miss an opt-out or response decision.
Lawsuit or subpoena
Formal process can trigger short, non-negotiable deadlines and preservation duties. Contact qualified counsel promptly.
Ready to respond? Use the wizard
Ten short questions about what you received and how the image appeared. You get a tailored no-admission draft letter, notes on your situation, and the evidence list to gather — in about two minutes, entirely in your browser.
Response wizard
Answer 10 questions. Get your letter.
- 1 · AnswerPick what matches your records — “Not sure yet” is always an option and asserts nothing.
- 2 · ReviewRead your tailored draft, situation notes, and evidence list.
- 3 · CopyCopy or download, verify every fact, then get legal review.
Runs entirely in your browser — answers are not transmitted or stored. Not legal advice.
Choose the next step from the record
01
Confirm facts
Selection, storage, transmission, size, context, duration, reach, and terms.
02
Test rights
Ownership, authority, registration coverage, work match, and remedies.
03
Analyze law
Authorization, fair use, server-test jurisdiction, safe-harbor conditions, procedure, and damages.
04
Respond proportionately
Seek withdrawal, request more evidence, negotiate, settle with a complete release, or defend—with counsel where warranted.
Primary and authoritative sources
Read the statute, controlling decisions, specifications, and provider terms. Summaries do not replace them.
- U.S. Copyright Office — More Information on Fair UseFour-factor framework
- 17 U.S.C. § 107Fair use
- 17 U.S.C. § 512System caching, takedown notices, and safe-harbor conditions
- 17 U.S.C. § 504Damages and profits — actual damages, statutory ranges, innocent infringement
- Copyright Office — Section 512Official overview and resources
- Perfect 10 v. AmazonNinth Circuit server test and search-thumbnail fair-use analysis
- Hunley v. InstagramNinth Circuit application of the server test to embeds
- Lenz v. UniversalFair-use consideration before a DMCA takedown notice
- Kelly v. Arriba SoftCopyright Office case summary — search-engine thumbnails held fair use
- Authors Guild v. GoogleSecond Circuit — mass indexing and snippets as transformative fair use
- Associated Press v. MeltwaterCopyright Office case summary concerning a clipping service
- Brammer v. Violent HuesFourth Circuit photograph fair-use analysis
- Andy Warhol Foundation v. GoldsmithSupreme Court — purpose-focused first-factor analysis
- oEmbed specificationResponse types, fields, discovery, and cache_age
- Open Graph protocol
og:image, title, URL, and object metadata - X — How to embed a postOfficial embed information
- X oEmbed APIProvider response and embed workflow
- Schema.org NewsArticleStructured article and image data
- Google Article structured dataJSON-LD article-image examples
- Copyright Office public recordsSearch registrations and recorded documents
- FTC — ReportFraudReport suspected fraud or impersonation
- FBI Internet Crime Complaint CenterReport internet-enabled crime
General information—not legal advice
This toolkit provides general educational information about copyright notices, technical evidence, oEmbed, social previews, caching, news aggregation, and potential defenses. It does not provide legal advice, determine whether any particular use is lawful, create an attorney-client relationship, or guarantee any result.
Copyright, contract, evidence, fair-use, safe-harbor, and procedural rules vary by jurisdiction and facts. Do not miss a court, Copyright Claims Board, subpoena, or response deadline. Consult a qualified intellectual-property lawyer before sending a response, making admissions, paying a demand, filing a counter-notice, or relying on a defense.
A demand is an allegation, not a judgment. Missing support does not automatically defeat a claim. Metadata and oEmbed do not automatically grant a license. Caching does not automatically qualify for fair use or a safe harbor. Customize and fact-check every template.