Legal Foundations for Indie Game Studios — The Complete Guide
Building a game is hard. Keeping everything you built is harder — and most indie studios don't realize how much is at risk until a contractor dispute, a platform delisting, or an FTC enforcement action arrives. The legal structure you build around your studio determines not just whether you survive those moments, but whether you ever get to keep the value you create. This guide covers the seven legal foundations every indie studio needs, from your first entity filing through the IP documentation that makes acquisition conversations possible.
What This Guide Covers
- Entity Formation — Why Your Studio Needs a Legal Entity Before Your First Dollar
- IP Ownership — Who Owns What Your Team Builds
- Contractor and Team Agreements — Protecting Your Studio When You're Not All Co-Founders
- Age Ratings, COPPA, and Kids' Game Compliance
- Platform Distribution — What Steam, Epic, and Itch.io Agreements Actually Say
- Loot Boxes, Gambling Regulations, and In-App Purchase Compliance
- Building an Acquisition-Ready IP Stack — What Investors and Acquirers Check
Entity Formation — Why Your Studio Needs a Legal Entity Before Your First Dollar
For $300 and ten business days, you can separate your personal bank account from every lawsuit, chargeback, and contractor dispute your studio will ever face. That's the cost of filing a Certificate of Formation for a Texas LLC online through SOSDirect. It is also, in practical terms, the single most protective legal step an indie studio can take before it earns its first dollar — and most studios skip it entirely until something goes wrong.
Operating as an unincorporated sole proprietor or an informal partnership means there is no legal wall between the studio's liabilities and your personal estate. A copyright infringement claim from a third-party IP holder, a breach of contract suit by an unpaid contractor, or a payment processor freeze on a storefront payout can all reach your personal bank accounts, home equity, and savings. A properly formed and maintained LLC or corporation interposes a liability shield between those claims and your personal assets — not because the entity is magic, but because it is a legally recognized boundary that courts respect when the entity is treated as a separate person (separate bank account, separate contracts, no commingling of funds).
Texas is a particularly favorable jurisdiction for US-based indie studios. There is no state income tax, the one-time LLC filing fee is $300 (expedited next-day service runs $500; same-day is $750), and online filings typically process within 10 to 12 business days. Texas does not charge a separate annual report fee, though studios must file a Franchise Tax Report and Public Information Report each year — both straightforward for most small studios.
LLC vs. C-Corporation: The Investor-Track Decision
For studios that plan to remain self-funded or bootstrap to profitability, a Texas LLC is usually the right structure — it offers the liability shield, pass-through taxation (no corporate-level tax on profits), and flexibility in how you divide economics among founders without the administrative overhead of a corporation. But if your studio is building toward a VC or angel round, the calculus shifts.
C-corporations can issue Qualified Small Business Stock (QSBS) under IRC §1202, which allows founders and early investors to exclude capital gains from a future sale. The One Big Beautiful Bill Act, enacted July 4, 2025, raised the per-taxpayer, per-issuer QSBS exclusion cap from $10 million to $15 million (indexed for inflation beginning in 2027) and the gross asset ceiling from $50 million to $75 million. For stock issued or acquired after July 4, 2025, the tiered exclusion structure is: 50% for stock held 3–4 years, 75% for 4–5 years, and 100% for 5+ years. Investors know this structure and increasingly expect it — which means studios that form as LLCs and later attempt conversion face transaction costs and timing risk that an early C-corp formation avoids entirely.
The Operating Agreement Gap That Creates IP Disputes
Whichever entity you choose, if you have more than one founder, you need a written operating agreement — and that agreement needs to address IP ownership explicitly. Texas law does not require a written operating agreement, but without one, the default rules under the Texas Business Organizations Code allocate economic rights by capital contribution percentage, not by labor or creative contribution. That means the co-founder who contributed more cash at formation has a proportionate claim to the studio's assets — regardless of who wrote the engine, designed the characters, or composed the soundtrack.
More critically: if a founder contributed IP assets before the entity was formed — a game prototype, an art library, a working build — and the operating agreement does not specify that those assets were assigned to the entity at formation, those assets remain legally owned by the individual founder. The moment the studio generates revenue or faces acquisition interest, that ambiguity becomes a live dispute. A well-drafted operating agreement resolves this on day one by specifying exactly what each founder contributed, what those contributions are worth, and that all pre-formation IP is assigned to the entity as a condition of membership.
The Promise Legal founder agreements guide covers the full range of operating agreement provisions that game studio founders need — from IP contribution schedules to buyout mechanics for departing members. That documentation layer is where entity formation converts from a filing to an actual legal foundation.
IP Ownership — Who Owns What Your Team Builds
Most indie developers believe that paying a contractor for work means the studio owns it. Under US copyright law, that assumption is wrong — and it is wrong in a way that routinely surfaces years later, when the game is generating revenue or the studio is in acquisition discussions. The actual rule is narrower than most people expect, and the fix is simple: a written assignment clause in every contractor agreement, executed before a single line of code is written or a single asset is delivered.
The Work-for-Hire Problem
Copyright law creates two paths to work-for-hire status. The first — employee work product created within the scope of employment — applies only to actual employees, not contractors. The second path, under 17 U.S.C. §101, covers nine specific categories of commissioned works: contributions to collective works, parts of motion pictures or other audiovisual works, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases. Video games are not on this list. Character art, engine code, soundtrack compositions, and level design assets do not fit any of the nine categories. That means a contractor who builds your game's core visual library or proprietary engine code retains copyright ownership by default, regardless of what you paid them, unless you have a written agreement that transfers those rights to the studio.
The writing requirement is not a technicality — it is a separate statutory rule under 17 U.S.C. §204(a), which provides that a transfer of copyright ownership, including an exclusive license, is not valid unless it is in writing and signed by the owner. An email chain where a contractor says "all good, it's yours" does not satisfy this requirement. An invoice marked "work for hire" does not satisfy this requirement. The assignment must be a signed instrument — which can be a paragraph embedded in a properly executed contractor services agreement, but it must exist.
The Mojang Trademark Lesson
Copyright is not the only IP risk. Game title trademarks are equally important — and equally misunderstood. In September 2011, ZeniMax Media (Bethesda's parent) filed suit against Mojang after Mojang applied to register "Scrolls" as the title for a new card game. ZeniMax argued the mark infringed its "The Elder Scrolls" trademark. The parties settled in March 2012: Mojang ceded the trademark, and ZeniMax licensed it back to Mojang for limited use with that specific game only. Mojang ultimately renamed the game "Caller's Bane" in 2016. A forced rename four years after launch — after marketing investment, community-building, and brand equity accumulation — is a costly outcome that a trademark clearance search and earlier registration could have avoided.
As of January 18, 2025, the USPTO restructured its trademark fee schedule, eliminating the TEAS Plus and TEAS Standard tiers and setting a single electronic base application fee of $350 per class. A studio registering both its studio name and a game title across Class 9 (computer software and games) and Class 41 (entertainment services) pays a minimum of $1,400 in government filing fees. That cost does not include attorney time for the clearance search, response to office actions, or prosecution — but the government fee alone is the floor. Registering early, before launch marketing creates brand equity, is significantly less expensive than clearing a challenged mark or rebranding after release.
AI-Generated Assets: An Emerging Ownership Gap
Studios using generative AI tools to produce visual assets, music, or in-game dialogue should understand a specific limitation in the current copyright framework. The Copyright Office's January 2025 report on AI and copyrightability concluded that a party who simply enters a prompt into a generative AI tool cannot claim authorship over the resulting output. Human creative contributions — selecting, arranging, modifying, and curating AI outputs — can constitute protectable authorship, but this is evaluated case-by-case. Studios that rely heavily on AI-generated assets without sufficient human creative involvement may hold an IP library they cannot register, which in turn affects licensing, enforcement, and acquisition valuation. The practical response is to document human creative decisions made throughout the AI-assisted production process, not just the final prompt.
Contractor and Team Agreements — Protecting Your Studio When You're Not All Co-Founders
Game studios are built on informal relationships. A developer you met at a jam. A composer you found through a Discord community. A 3D artist who will "help out" on a revenue share basis. These arrangements feel like partnerships, but the law categorizes them differently depending on how they are structured — and the gap between how you treat a worker and how the law classifies them creates two distinct exposure tracks: one in state labor law, one in federal tax.
The California AB5 Problem (That Isn't Just California's Problem)
California's Assembly Bill 5 applies a three-part ABC test to determine whether a worker is an employee or an independent contractor. The critical provision for game studios is Prong B: the worker must perform work that is outside the usual course of the hiring entity's business. Under this standard, a game studio whose core business is making games cannot classify California-based game artists, programmers, or designers as independent contractors — because the work they perform is precisely the work the studio exists to do. Those workers must be classified as employees under California law, with the full obligations that entails: payroll taxes, workers' compensation, unemployment insurance, and California's wage and hour protections.
The cross-jurisdictional dimension makes this more than a California issue. A Texas studio that engages a California-based freelance animator for a six-month project is operating inside California's labor law framework for that worker, regardless of where the studio is incorporated. Remote work has made state-of-worker-domicile the operative jurisdiction for many labor law questions. Studios that engage contractors across multiple states should audit worker classification state by state, not just under their home state's rules.
The IRS Misclassification Tax Exposure
Federal exposure operates separately and can compound state liability. Under IRC §3509, an employer that misclassifies employees as independent contractors without reasonable cause owes 40% of the worker's share of unpaid FICA taxes (Social Security and Medicare), plus the employer's full FICA share, plus civil penalties of $50 per unfiled W-2 and 1.5% of wages. The reasonable-cause rate is reduced to 20% of the employee's portion for employers who can demonstrate good-faith reliance on classification guidance — but good faith requires documentation. A studio that cannot show its classification analysis will pay the higher rate.
The practical exposure for a small studio that ran three or four "contractor" artists for two years — paying them on invoices, filing 1099s, but treating them operationally as team members — is not abstract. Retroactive reclassification means back taxes, penalties, and interest on every dollar paid during the misclassification period. This does not require an audit initiated by the IRS; a single worker filing for unemployment benefits can trigger a state agency determination that cascades into a federal review.
Co-Founder Equity: Vesting Is Not Optional
For studios with multiple founders, the equity structure is as much a legal protection as it is a compensation mechanism. The industry standard — and investor expectation — is a 4-year vesting schedule with a 1-year cliff. At the 12-month anniversary, one quarter of each founder's equity vests. From that point, 1/48th vests each month until the 48-month mark. A co-founder who leaves before the cliff receives zero equity.
The protective function of this structure is specific: without vesting, a co-founder who exits after six months — taking their creative contributions, their industry relationships, and their institutional knowledge with them — retains their full equity stake in perpetuity. That stake dilutes all future fundraising rounds, complicates any acquisition conversation, and creates a financial incentive for the departing founder that is not tied to any ongoing value creation. Vesting schedules resolve this by tying equity ownership to continued participation. Investors typically impose this structure as a condition of a priced round if it is not already in place — which means negotiating it after the fact, from a weaker position.
Non-Compete Provisions Under Texas Law
Texas takes a different approach to non-compete enforcement than most jurisdictions. Under Texas Business & Commerce Code §15.50, a covenant not to compete is enforceable if it is ancillary to an otherwise enforceable agreement and contains reasonable limitations on time, geography, and scope of activity. Critically, Texas courts do not simply void overly broad non-compete clauses — they judicially reform them, reducing time periods, narrowing geographic scope, or limiting the restricted activities to match what is necessary to protect legitimate business interests. This "blue-pencil" approach gives Texas studios more protection from imperfectly drafted clauses than studios in states where courts void non-competes outright. A non-compete that is drafted too broadly in Texas becomes narrower; in some other states, it becomes unenforceable.
Every contractor agreement for a studio should address four elements: (1) IP assignment — all work product created under the agreement is assigned to the studio; (2) confidentiality — the contractor cannot disclose the studio's unreleased projects, technical implementations, or business plans; (3) classification acknowledgment — the agreement documents the basis for contractor status under the applicable state's test; and (4) compensation and IP ownership — the agreement makes explicit that payment is in exchange for both services and IP rights, not just services.
Age Ratings, COPPA, and Kids' Game Compliance
There are two separate compliance questions any indie studio needs to answer about minors and their game: what rating does the game carry, and whether COPPA applies regardless of that rating. They are not the same question, and studios that conflate them — assuming an E10+ ESRB rating is an adequate COPPA compliance posture — have materially misunderstood the regulatory landscape. The FTC's enforcement record over the last three years makes this misunderstanding expensive.
ESRB Ratings: Free for Digital, $3,000 for Physical
Digital-only games can obtain ESRB ratings at no cost through the IARC self-rating process, which is available on participating storefronts including the Nintendo eShop, Microsoft Store, Google Play, Oculus Store, and PlayStation Store. Developers complete a self-assessment questionnaire about their game's content, and the system generates region-appropriate age ratings automatically. According to VentureBeat/GamesBeat reporting, this free IARC path remains available following ESRB's phase-out of the Short Form process.
Physical retail releases follow a different path. They require the Long Form review process — and ESRB introduced a "value tier" for games with development budgets under $1 million at a cost of $3,000. For a studio weighing digital-only versus boxed retail distribution, this cost differential is one of several factors worth modeling before committing to a physical release. It is also a regulatory prerequisite, not optional, for retail shelf placement at major US retailers.
COPPA: Who Actually Plays Your Game, Not Who You Targeted
COPPA's applicability is determined by a totality-of-circumstances analysis under 16 CFR §312.2 — not by the developer's stated intent or the game's ESRB rating. The eight-factor test asks: (1) subject matter; (2) visual content; (3) use of animated characters or child-oriented activities and incentives; (4) music or other audio content; (5) age of models; (6) presence of child celebrities or celebrities who appeal to children; (7) language or other characteristics of the service; and (8) whether advertising is directed to children. Satisfaction of a subset of these factors may be sufficient — no single factor is determinative.
In practical terms: a game with anime-style animated characters, collectible mechanics with bright visual rewards, and popular voice actors who have roles in children's media may trigger COPPA's protections even if the developer built it for adult players. This has direct implications for data collection (parental consent is required before collecting personal information from children under 13), in-game purchasing (consent requirements), and social features (chat, voice communication, friend-finding systems).
The HoYoverse and Epic Enforcement Benchmarks
In January 2025, the FTC settled with HoYoverse (developer of Genshin Impact) for $20 million, establishing the most current US enforcement benchmark for combined COPPA and monetization deception violations. According to Frankfurt Kurnit's analysis, the FTC charged HoYoverse with: (1) collecting personal data from children under 13 without verifiable parental consent; and (2) deceiving players about loot box odds — featured characters had a 0.3% drop rate, with potential costs of $360–$540 to obtain them, obscured by a multi-layer virtual currency system. The settlement required HoYoverse to pay $20 million, delete personal data of children collected without consent, prohibit loot box sales to users under 16 without parental consent, and disclose actual drop odds and virtual currency exchange rates.
For scale context: in December 2022, Epic Games settled FTC charges arising from Fortnite's COPPA violations for $275 million — the largest-ever FTC rule violation penalty at that time — as part of a combined $520 million settlement. The Orrick analysis of the settlement noted that default on-by-default voice and text communications connecting children with strangers were independently cited as actionable — separate from monetization practices. A studio that enables social features without age-gating those features for children faces exposure on that basis alone, regardless of its monetization model.
Platform Distribution — What Steam, Epic, and Itch.io Agreements Actually Say
Most indie developers treat Steam's 70/30 split as a known cost and sign without reading further. That is understandable — the Steamworks Distribution Agreement is long, and the revenue share is the number everyone discusses. But the revenue split is not the most consequential term in the agreement. The price parity clause and the delisting provisions carry more practical risk for most studios, and both are worth understanding before signing.
Steam's Revenue Share: What the Tiers Actually Mean
Valve uses a tiered revenue share structure: 30% on the first $10 million in lifetime game revenue, 25% on revenue between $10 million and $50 million, and 20% on revenue above $50 million. These tiers are calculated per game, not per developer. For the overwhelming majority of indie developers, every dollar of revenue falls in the first tier. The vast majority of Steam games never reach the $10 million revenue threshold — which means virtually all indie studios pay the maximum 30% platform fee, regardless of how long the game has been on the market.
Epic Games Store offers an 88/12 developer-favorable split as its headline differentiation from Steam. On a straightforward revenue calculation, Epic's terms are more favorable for developers at every revenue level. But the headline split comparison understates what Valve's platform most-favored-nation clause does to that advantage.
The Price Parity Clause That Neutralizes the Epic Advantage
Valve's Steam Distribution Agreement includes a platform most-favored-nation (PMFN) clause that prohibits developers who list on Steam from offering their game at a lower price on competing storefronts, or from providing additional content on a competing storefront that is not also available on Steam. In practical terms: a studio cannot price its game at $19.99 on Epic and $24.99 on Steam to pass on the cost savings from Epic's lower cut to consumers. Both storefronts must carry the same price.
This clause is the subject of a class action filed in August 2024 alleging antitrust violations — the argument being that the PMFN prevents developers from passing on the savings from Epic's 88/12 split to consumers, artificially maintaining Steam-level pricing across all storefronts. According to ABA Business Law Today, no US court has yet found that an MFN provision of this type violates antitrust law — but the litigation is active. For studios planning a multi-platform strategy, the operational implication is clear regardless of how the antitrust question resolves: you cannot use Epic's better economics to offer a lower consumer price as long as your game is also listed on Steam.
Delisting Risk: The Exit Condition Most Developers Miss
Valve retains unilateral authority under the Steamworks documentation to delist titles. Developers can initiate their own product removal, but there is no contractual recourse mechanism if Valve initiates the delisting. This is not a theoretical risk. Beginning in late 2024, Valve delisted over 5,000 games from Steam — primarily games without required age-rating information under Germany's mandatory age-rating regulations. The Nerd Stash reported that approximately 23,000 titles were flagged as potentially affected, and that the Steamworks documentation confirms Valve will not republish a product it retires.
For a studio whose game generates ongoing revenue from a back catalog, delisting is an existential revenue event. Compliance with age-rating requirements — the IARC process for digital titles described in the previous section — is not just a legal formality. It is the minimum threshold for maintaining platform availability on the world's largest PC gaming storefront.
Itch.io: The Open Marketplace Alternative
Itch.io operates as an open marketplace with developer-controlled pricing and a default revenue split of 90% to the developer and 10% to the platform — though developers can choose to give itch.io a higher percentage, or zero. Critically, itch.io imposes no price parity clause. A studio can price a game lower on itch.io than on Steam without violating its Steam distribution agreement, provided the itch.io page does not trigger Steam's content parity concerns. For studios releasing free-to-play titles, experimental projects, or games with existing communities, itch.io's terms represent a genuinely different economic structure — one where the platform economics favor the developer at every revenue level, without the MFN-clause friction that characterizes Steam-plus-Epic multi-distribution strategies.
Publisher Deals: The Terms That Matter Beyond Revenue Share
For studios approaching direct publisher deals beyond Steam and Epic, the revenue split headline number is again not the most consequential term. Based on Southwind's analysis of indie publishing agreement structures, the three provisions most likely to determine the economic outcome for a studio are:
- Recoupment structure: Whether recoupment comes from total game revenues (more publisher-favorable) or only from the developer's revenue share (developer-favorable). Some agreements apply 80–100% of total revenue toward recoupment; others use an 80/20 split where 20% flows to the developer even during the recoupment period. A studio can have a 60/40 developer-favorable headline split and still see no revenue for years under a total-revenue recoupment structure.
- Sequel and DLC rights: Sequel rights appear in approximately 63% of publishing agreements that include an advance. Of those, 56% grant the publisher exclusive sequel development rights — meaning the publisher controls whether a franchise continues, not the developer. A studio that builds a successful IP under this structure may not control what happens to that IP next.
- IP ownership and reversion: Most direct publishing agreements leave IP ownership with the developer, but some — particularly agreements involving significant publisher investment in development — include IP transfer provisions or options. Reversion clauses that return publishing rights in territories where the publisher fails to distribute are worth negotiating for regardless of the IP ownership structure.
Signing a publisher agreement without understanding recoupment mechanics is one of the most common structural mistakes in indie game development. The headline revenue share tells you what percentage of revenue you receive; the recoupment structure tells you when you start receiving it.
Loot Boxes, Gambling Regulations, and In-App Purchase Compliance
Loot boxes sit at the intersection of three regulatory frameworks that operate independently of each other: gambling law, consumer protection law, and children's privacy law. A studio can be compliant under one framework while facing enforcement exposure under another. The design-level decisions that determine a studio's regulatory posture — whether items are transferable, whether odds are disclosed, whether age gates are enforced — need to be made before the monetization system is built, not after it launches.
Belgium: Criminal Penalties for Transferable Loot Boxes
Belgium is the most aggressive jurisdiction globally on loot box classification. The Belgian Gaming Commission determined in 2018 that paid loot boxes whose contents are determined by chance and are transferable to other players constitute gambling under the Belgian Gaming Act. Offering such loot boxes without a gambling license is a criminal offense under Belgian law, carrying imprisonment of 6 months to 5 years and a fine of up to €800,000. The enforcement deadline for compliance was June 20, 2018.
The Belgian Gaming Commission has acknowledged that enforcement has been difficult in practice — an academic study found that 82 of the 100 highest-grossing iPhone games continued selling loot boxes in Belgium after the deadline. But the legal exposure is real regardless of enforcement frequency. A studio with transferable in-game items available for real-money purchase is operating a potentially unlicensed gambling service in Belgium, with criminal liability attaching to its officers and directors.
The Netherlands: How EA Won on Transferability
The Dutch Kansspelautoriteit (KSA) — the Netherlands' gambling regulator — applies a three-element test to determine whether loot boxes constitute gambling: (1) prizes can be won, (2) participants cannot influence the outcome, and (3) contents have economic value through transferability within the game or through third-party platforms. EA was initially fined €5 million for FIFA Ultimate Team (FUT) packs in the Netherlands on this basis.
EA appealed, and the Dutch Council of State ruled on March 9, 2022 that FIFA 22's FUT loot boxes did not constitute gambling and revoked the penalty. The key fact: EA had made FUT cards non-tradeable in the Netherlands by 2018. Without transferability, the third element of the KSA's test failed, and the loot boxes fell outside the statutory definition of gambling. This outcome establishes a concrete design mechanism for avoiding gambling classification in the Netherlands: if in-game items obtained through randomized purchase cannot be transferred between players or sold on third-party platforms, they are unlikely to meet the Dutch standard.
The January 2025 Antwerp Court Referral
The European regulatory picture became more complex in January 2025 when the Enterprise Court of Antwerp referred several questions to the Court of Justice of the European Union (CJEU) regarding Apple's potential liability for distributing a game containing loot boxes in its App Store. According to Taylor Wessing's analysis, the claimant spent €67,813 on loot boxes in 10 months in a Belgian-classified gambling game (Top War: Battle Game) and sought those sums as damages from Apple. The CJEU referral asks whether the EU's e-Commerce Directive safe harbors apply to platform providers that offer and promote gambling-classified activities. If the CJEU answers no, app stores could face direct liability for distributing loot box games without age verification or gambling license requirements — a structural shift that would affect how platforms handle indie game submissions globally.
US Loot Box Standards: Odds Disclosure and Age-Gating
The United States does not classify loot boxes as gambling at the federal level, but the FTC's January 2025 HoYoverse settlement established two minimum compliance standards that now define the US enforcement baseline. First, odds must be disclosed — the actual probability of receiving each outcome from a loot box or randomized purchase mechanism must be communicated to players before purchase. Second, users under 16 cannot purchase loot boxes without parental consent.
As detailed in the Frankfurt Kurnit analysis, HoYoverse's exposure arose specifically from the combination of hidden odds (0.3% for featured characters, requiring $360–$540 in expected spending to obtain them) and a confusing virtual currency system that obscured the real-money cost. A studio that sells loot boxes with multi-layer currency conversion — where players buy Crystals, which convert to Genesis Crystals, which convert to Primogems, which are used to pull characters — is creating the same obfuscation that triggered FTC scrutiny. The FTC's settlement now requires direct real-currency purchase options and clear odds disclosure. Studios planning any randomized in-app purchase mechanism should implement both before launch.
Building an Acquisition-Ready IP Stack — What Investors and Acquirers Check
Acquisition due diligence for a game studio is, at its core, an IP audit. An acquirer buying a studio is buying the right to own and exploit the games that studio built — which means every asset, mark, and line of code in the commercial product line needs clean title. Studios that treat IP documentation as a future problem discover at the worst possible moment — during a live deal process — that clean title cannot be manufactured retroactively without the cooperation of contractors who have long since moved on and may have no incentive to help.
The GPL Contamination Problem
Open source software is pervasive in game development. Game engines, physics libraries, audio frameworks, networking middleware, and toolchains all draw from open source ecosystems. The license terms attached to those components determine what obligations attach when the studio's commercial code is distributed — and GPL and AGPL licenses create obligations that can destroy the proprietary value of a codebase if they are not identified and managed before an acquisition.
GPL and AGPL are copyleft licenses that condition use on passing the same terms downstream. An acquirer that closes without understanding the scope of copyleft components in a target's codebase may inherit undisclosed source code disclosure obligations, or find that portions of the proprietary engine must be licensed openly — effectively making those components freely available to competitors. According to Nixon Peabody's 2025 M&A analysis, OSS usage in acquisition targets is "usually understated," and acquirers now routinely require third-party automated composition analysis using tools such as Black Duck, FOSSA, Snyk, or Mend as a condition of closing. A studio that cannot produce a clean SBOM — a Software Bill of Materials inventorying all components, dependencies, and their licenses — is signaling a diligence problem before the conversation about valuation begins.
The same Nixon Peabody analysis notes that "having a current, accurate SBOM is no longer a bonus. It's a requirement in many M&A conversations." For a game studio, this means running composition analysis on the commercial build quarterly — not just as a pre-sale exercise — so that GPL contamination is identified and remediated before it becomes a deal condition that requires emergency engineering work during a live acquisition process.
Contractor Assignment Gaps: The Most Common Diligence Failure
Standard IP diligence in a game studio acquisition requires production of signed copyright assignment agreements from every contractor who contributed to any asset in the studio's commercial product line. As discussed in Section 2 of this guide, 17 U.S.C. §204(a) requires that copyright transfers be in writing and signed by the rights holder. A missing assignment — particularly from a contractor who built the game engine, designed core mechanics, or created foundational visual assets — creates a cloud on title that cannot be resolved without that contractor's cooperation.
Acquirers respond to missing assignments in one of three ways: they require holdback escrow (a portion of the purchase price held back until assignments are obtained or the limitations period expires), they require a price reduction to account for the IP uncertainty, or they decline to close. None of these outcomes is recoverable by the time due diligence surfaces the gap. The assignment must be in the contract before the contractor delivers the work.
Trademark Chain of Title
The Mojang/Scrolls trademark dispute — described in Section 2 — illustrates a specific acquisition risk beyond the litigation cost itself. When a studio's game title trademark is challenged, unregistered, or the subject of a contested settlement, acquirers face a brand equity question: how much of the purchase price represents value attached to a mark that may need to be renamed or that is subject to third-party license-back conditions? A forced rename during or after an acquisition process can destroy community goodwill, invalidate marketing investment, and complicate the financial model used to justify the purchase price.
Registered trademarks with clean chain of title — no assignments of record from third parties, no active opposition proceedings, no settlement-based license-back arrangements — present a straightforward asset. Acquirers also check Class coverage: a studio name registered only in Class 9 (software) but not Class 41 (entertainment services, including online gaming) has incomplete coverage for the core business, which may require a post-close filing campaign that the acquirer factors into the price.
Publishing Agreement IP Provisions
Studios that have entered publisher agreements before an acquisition need to review those agreements for IP ownership and sequel rights provisions before a deal process begins. Based on Voyer Law's 2025 analysis of indie publishing agreements, IP ownership remains with the developer in 96.4% of agreements — but sequel rights appear in 63.49% of agreements that include an advance. Of those, 56.41% grant exclusive sequel development rights to the publisher.
An acquirer buying a studio that has granted a publisher exclusive sequel rights to its most successful franchise is buying a constrained asset. The studio owns the current game; the publisher controls the next one. That constraint does not necessarily kill a deal, but it reprices it — and it is materially harder to negotiate publisher consent to terminate or limit sequel rights during a live acquisition process than it would have been during the original publishing agreement negotiation.
Studios planning for an eventual acquisition — or simply building toward investment — should treat this checklist not as a pre-sale exercise but as a quarterly governance practice. The IP stack that makes a studio acquisition-ready is built over years of documentation discipline, not assembled in the six weeks before a letter of intent is signed.
Ready to get your studio's legal foundation right? Schedule a consultation with Promise Legal.