Skip to content
induwara.lk
Premium
Opinionaicopyrightfreelancing

Google's $40M-per-character AI deal is a price list

Google is reportedly offering Hollywood studios ~$40 million per character to train on their IP. What that price tag means if you build with these models.

Induwara Ashinsana5 min read
A Disney-supplied promotional image marked with an AI label, used as the article's hero
Image: The Verge

Google's AI licensing deals with Hollywood have a number attached now, and it is the most useful piece of information to come out of the AI industry this year. According to The Verge's report by Charles Pulliam-Moore, citing The Los Angeles Times, Google could pay a studio like Disney/Pixar around $40 million for the right to generate outputs featuring a single copyrighted character.

Not a library. Not a franchise. One character.


πŸ’° The number is the story, not the deal

Everything else in this story is familiar. Google wants training rights, studios want money, nobody has signed anything. Google reportedly has no agreement yet with Disney, Warner Bros. Discovery, or Universal. What is new is that a rights-holder and a model company have put a public-ish price on a single unit of copyrighted material.

Here is what the licensing map looks like from the reporting:

Deal Parties Status
Studio training licences Google ↔ Disney / WBD / Universal Pitched, nothing signed
Per-character generation rights Google ↔ Disney/Pixar ~$40M per character, reported figure
Studio investment Google DeepMind β†’ A24 $75M, struck earlier this summer
Model training licence Lionsgate ↔ Runway Signed 2024, nothing shipped yet
UGC generation partnership Disney ↔ OpenAI (Sora) Collapsed

Key takeaway: if one cartoon character is worth $40 million as training input, then training data has stopped being a free externality and become a line item on a balance sheet. Everything downstream of that changes.


πŸ” The moat moved from compute to rights

For the last few years the honest answer to "why can't a small team compete with Google" was compute and talent. Both of those have been getting cheaper and more accessible. Open-weight models keep closing the gap, and you can fine-tune something decent on rented GPUs for the cost of a used motorbike.

Rights don't work that way. There is no cheaper tier of Darth Vader.

  • Compute is a commodity with falling prices and a spot market.
  • Talent is global and increasingly remote-friendly.
  • Licensed IP is a monopoly good, sold by a party with no incentive to discount.

That asymmetry is the point of the original piece: the studios can walk away and lose nothing, while Google needs the deal badly enough to pay billions in aggregate. Google's real purchase here isn't pixels, it's legitimacy. Public sentiment on AI has been sliding, especially among young people, and "official Disney output" is a much easier sell than another round of disruption talk.


βš–οΈ Where this lands on a freelancer in Colombo

If you deliver AI-assisted creative work to overseas clients, this news is not abstract. When licensing becomes a market with prices, unlicensed output becomes a quantified liability rather than a grey area. Your client's legal team can now put a number on it.

The reporting also gives a preview of audience reaction risk. AI-generated images turned up in the official artbook for Spider-Man: Brand New Day and fans were unhappy about it, on a film that went on to make $2 billion. The film survived. A three-person studio's reputation would not.

Practical sorting for client work:

What you're doing Risk level Why
Generating recognisable characters or brands High This is exactly the right Google is trying to buy
Style-matching a named living artist High Attribution and passing-off exposure
Generic stock-type imagery from a licensed model Low Provider indemnity usually covers this
Generating from the client's own assets Lowest They own the input
Cleanup, upscaling, background work on supplied files Lowest You're editing, not synthesising IP

Warning: many international contracts now carry an IP-indemnity clause that pushes infringement liability onto you, the supplier. Read that clause before you accept a rate. If a job requires character-adjacent generation, price the risk in or decline it. I'm not a lawyer and this isn't legal advice, but "I didn't read the indemnity clause" has never been a defence anywhere.

If you're recalculating what a job is actually worth once you factor that in, the freelancer hourly rate calculator and the USD-LKR earnings calculator will do the arithmetic faster than a spreadsheet.


πŸ› οΈ What I'd build instead

You cannot outbid Disney. So don't compete on the axis where money decides the winner. Three things are still cheap and still defensible:

  1. Data you legitimately own. A client's product catalogue, your own photo library, your company's support tickets. Nobody can outbid you for access to it because you already have it.
  2. Local context nobody has licensed. Sinhala and Tamil text, SL-specific documents, local pricing, local regulations. Frontier labs are not buying this; the market is too small for them and exactly the right size for you.
  3. Openly licensed material, used properly. CC-licensed and public-domain assets, and open-weight models with clear licence terms. Slower to assemble, but it produces work you can ship without checking your inbox for takedown notices.

The pattern is the same one that has always worked for a small team with a learning budget instead of a war chest: pick the ground where capital doesn't decide the outcome.

Keep a provenance note for every asset in a project. Source, licence, date, and the model that produced it. Ten seconds per asset now, versus reconstructing it from memory eighteen months later when someone asks.


πŸ’‘ What this means for you

The $40 million figure is the useful takeaway, not the corporate manoeuvring. It tells you that the free-training-data era is being priced out from the top, and that the companies doing the pricing know exactly how exposed they were.

For anyone building here, three moves:

  • Stop treating "the model generated it" as a defence. It was never one, and now there's a market rate proving the underlying right had value.
  • Audit your dependency chain. Know which models you use, what their licences say about output ownership, and whether the provider offers indemnity. Write it down.
  • Move your work toward data you own or data nobody wants to license. That's where a small team in Sri Lanka can build something that doesn't evaporate when a billion-dollar deal gets signed above your head.

Google is buying its way out of a legitimacy problem. That is a problem you don't have. Don't create one by borrowing theirs.

#ai#copyright#freelancing
IA

Induwara Ashinsana

Information Systems student at UCSC and Executive Director at Ryzera Technologies. Writes about software, AI, and what it means for builders in Sri Lanka.

About the author β†’

Keep reading