An end to the input-output dichotomy in AI copyright? Like Company v Google takes an unexpected turn

AI copyright arguments in C-250/25 Like Company v Google are shifting away from a strict input-output divide. The hearing raised a focused question on whether the legal analysis should stop treating training data and generated outputs as separate copyright events. That point matters because it may alter how copyright liability is assessed in AI disputes.

The conventional distinction is easy to state: input concerns the material used to train a model, while output concerns the material the model produces. If that distinction is weakened, the legal consequences are not confined to one stage of development or use. A court may instead need to consider the relationship between the material absorbed by the system and the content it later generates as part of a single copyright assessment.

For copyright analysis, that approach is significant because it narrows the value of arguing that only one side of the AI process should matter. It also raises the possibility that liability questions may turn less on when copying occurs and more on how the system operates overall. That does not resolve the underlying issue, but it does show that the traditional framework may be too rigid for the dispute being examined.

For rights holders, the practical effect is uncertainty. If the input-output distinction no longer controls the analysis, the legal boundaries around AI use of copyrighted material become less predictable. That increases the importance of precise factual analysis in any copyright claim involving AI systems, because the relevant conduct may no longer be capable of being divided neatly into separate stages.

The immediate legal point is therefore not that copyright protection has been expanded or reduced, but that the analytical structure itself may be changing. If that trend continues, the risk for AI-related copyright disputes will be a less certain liability framework and a correspondingly harder compliance assessment.

Disclaimer: This post is for general information only and does not constitute legal advice. Specific advice should be sought for your particular circumstances.
Source: