Shotcraft
How generation works

Training data and copyright: what is not settled

Where the training material came from, and why the law has not settled what that means.

Commonly believed, and wrong: a court has already ruled that training on copyrighted work is fair use.

Imagine a chef who learned to cook by photographing every page of every rival's recipe book and keeping the photographs in a warehouse. Nobody claims the finished dish is a copy of any single recipe. The argument is about the warehouse: the copying that had to happen for the education to happen at all. That is the shape of the copyright fight over generative models, and it is why the debate so often talks past itself. There are two separate questions. First, was the reproduction of works to assemble and train on a dataset infringement, or was it fair use in the United States and fair dealing elsewhere. Second, and independently, does a particular output infringe, either by resembling a specific work or by depicting a protected character or trade mark. A model can be clean on one question and exposed on the other. The honest answer today is that neither question is resolved. The US Copyright Office published Part 3 of its Copyright and Artificial Intelligence report, on generative AI training, in May 2025, and it remains a pre-publication version. The litigation is live and pulling in different directions on different facts: Andersen v. Stability AI is in discovery with Runway added as a defendant, Getty's US case moved districts, Kadrey v. Meta continues, the New York Times matter is consolidated in a multidistrict proceeding, Bartz v. Anthropic ended in a settlement given final approval in July 2026 so its fair-use reasoning was never tested on appeal, and Thomson Reuters v. Ross was argued in the Third Circuit in June 2026 and is undecided. In the UK, the Getty v. Stability judgment turned on territoriality and abandoned claims rather than on whether training is lawful. Anyone who tells you the question is settled is selling something.

Why it matters on a production

This lands on your paperwork, not your timeline. Broadcasters, streamers and brand clients increasingly ask what generated material is in a delivery, and errors and omissions cover depends on the answer. Practical consequences: keep a provenance record for every generated shot, naming model, version, prompt, seed and every reference image plus the rights you hold in it; avoid prompting by living artist name or protected character; read what a vendor's indemnity actually covers and what it caps; and remember that a platform's stated training data claim may cover only its own models, not partner models hosted in the same product.

What people get wrong

Each of these is a belief worth dropping, followed by what is actually happening.

Terms this introduces

Fair use
A US statutory defence that can excuse otherwise infringing copying based on a multi-factor analysis, applied case by case rather than as a blanket rule.
Fair dealing
The narrower UK and Commonwealth equivalent, available only for specified purposes rather than as an open-ended balancing test.
Provenance record
The log of model, model version, prompt, seed, parameters and input references behind a generated shot, kept so a delivery can be explained later.
Indemnification
A vendor's contractual promise to cover defined legal costs arising from use of its outputs, usually subject to caps, conditions and correct use of the product.
Multidistrict litigation
A US procedure that consolidates related federal cases before one judge for pretrial purposes, which is why several separate complaints can appear under a single docket.

Where this shows up in the directory

Models whose own documentation names this. It is evidence the vendor considers it relevant, not a judgement that the model is good or bad at it.

16 more not listed.

Whose job this changes

Craft roles whose page discusses this directly. Follow one to see what the person actually decides.

Further reading

Next

Sources