Zarlent

Can a game studio sell or license its data to AI companies, and what is it worth?

Yes. Game studios with 10 to 500 staff can license game code, gameplay footage and company records, with a published price band of $750K to $1M as of November 2026. Work you do not own, such as publisher-owned assets and licensed middleware, usually cannot be included.

No buyer pays to be mentioned

What could your company's records earn? Get a range in 30 seconds. Free, no obligation.

Can a game studio license its code and footage to AI companies?

Yes. Buyers publish a program for game studios and list game code, gameplay footage and company records as what they want (published buyer listing, read 20 Nov 2026). They state 10 to 500 staff and a ceiling in the $750K to $1M band. See the price table by industry.

A game is an unusual pile of records. It holds code, art, sound and motion in one place, plus years of playtest footage showing a person making choices on screen. Footage with matching game state is hard to find anywhere else.

What are game studio records worth?

ItemFigureSource
Published price band per studio$750K to $1MPublished buyer listing, read 20 Nov 2026
Staff band buyers list10 to 500Same listing
Records namedGame code, gameplay footage, company recordsSame listing
Work made for hire testEmployee work within regular duties, or a signed written agreement for certain commissioned worksUS Copyright Office, Circular 30, read 21 Nov 2026

A studio with shipped titles, long version history and footage tied to build numbers sits higher in the band. A studio with one prototype sits lower. Run the calculator.

Which game records do buyers want?

  • Code: engine and gameplay code, tools, build scripts and the commit history behind a shipped game.
  • Gameplay footage: recorded playtests and internal captures. Footage paired with inputs or logs can be worth more than video alone, because it shows what the player did.
  • Company records: design documents, bug trackers, sprint notes, post-mortems and live-operations logs.

The bug tracker and design documents show why choices changed. That reasoning is what code alone cannot teach.

Which systems hold the records?

Code is in version control, often with large binary files stored separately. Art and audio sit in an asset pipeline or shared drive. Playtest video sits on cloud storage or a recording tool. Design documents and tickets sit in a wiki and an issue tracker. Chat history holds a lot of the reasoning. See preparing company data.

What can a game studio not share?

  1. Work you do not own. Under US copyright law, a work is made for hire when an employee creates it within regular duties, or when certain types of commissioned work are covered by a signed written agreement that states the work is made for hire (US Copyright Office, Circular 30, read 21 Nov 2026). Art or code from a freelancer without such an agreement may belong to the freelancer, not the studio. Check your contractor agreements.
  2. Publisher-owned work. If a publisher funded the game, the publishing contract may give the publisher the rights to code, art and footage. Read it before offering anything.
  3. Licensed middleware and assets. Engine source, audio libraries and purchased asset packs carry their own license terms.
  4. Player information. Telemetry, chat logs and support tickets can hold names, voices and messages. Children may be among them. See de-identification.
  5. Footage with voices of people outside the studio. Playtesters and streamers need consent.

This page is general information, not legal advice.

How should a studio prepare?

Pick one shipped title you fully own. Confirm each contributor was an employee or signed a work-for-hire or assignment agreement. Remove player data. Export the repository with history, the playtest footage and the design documents. Then read the contract clauses to check.

What does a sample record look like?

Three linked game records a studio could license: code with history, gameplay footage, and design and bug records.

Code with commit history
Repository
Gameplay code and tools, 3 shipped titles
History
4,200 commits over 26 months
Build link
Release build 1.4.2
Outcome
Shipped; 3 tuning changes reverted after tests
Ownership check
All contributors employees or signed work-for-hire
Personal details
Player data and contributor emails removed
Playtest footage with logs
Session
38 minutes, level 3 of 12
Paired input log
Yes, button presses and game state
Build number
1.3.9
Outcome
Player stuck at puzzle, design change filed
Linked ticket
Bug tracker item for the same build
Personal details
Playtester consent on file; voices removed or consented
Design doc and bug tracker
Design doc
Level 3 pacing, 4 revisions
Bug item
Puzzle unsolvable on 2 platforms
Time to fix
6 days, patched in 1.3.10
Linked records
Commit and playtest footage by build number
Decision
Hint system added after review
Personal details
Player names and chat removed

Illustrative samples: invented values, real record types.

What has company data sold for?

We record 40 public data sales, each with its price, date and source. Search all 40 recorded data sales.

Questions

Do I need to own the engine?

No. Many studios build on a commercial engine. You can license your own game code and assets but not the engine's own source unless its terms allow it.

Can I license footage of playtesters?

Only with their consent. Write it down before you record, and keep it.

Are mobile studios included?

The listing says game studios of 10 to 500 staff and names no platform. Ask the buyer which kinds of game it takes.

Does a failed game count?

Yes. A cancelled project still has code, tickets and playtests. Confirm ownership first.

Sources