Indie Studio Formation and IP: Structuring Your Game Company from Day One

Entity Choice: LLC vs. S-Corp vs. C-Corp for Game Studios

The most expensive legal mistake an indie studio can make is shipping its first game as a sole proprietor. Without an entity, there is no liability shield — a copyright infringement claim, a contractor dispute, or a platform takedown can reach your personal bank accounts, your home, and every other asset you own. Forming an LLC or corporation is the first line of defense, and the choice between entity types determines far more than your tax return.

For most bootstrapped studios — two friends building a side-scrolling platformer with no outside investment planned — a Texas or Delaware LLC is the right starting point. An LLC gives you the liability shield, pass-through taxation (income flows to your personal return, no corporate-level tax), and minimal compliance overhead. Texas LLCs have a franchise tax exemption for entities under $2.47 million in annual revenue; the state filing fee is $300. If institutional money is never part of the plan, this is your default.

The calculus changes the moment venture capital or a serious publisher advance enters the picture. Institutional investors structurally require Delaware C-corporations — VC term sheets, SAFEs, convertible notes, and stock option plans are built around Delaware corporate law. Tax-exempt and foreign investors cannot hold LLC interests without triggering unrelated business taxable income (UBTI) problems, so VC funds will not invest in LLCs regardless of how strong your game is. S-corps face parallel disqualifiers: no foreign shareholders, no more than 100 shareholders, and passive income restrictions that create structural deal-breakers.

The tax exit case for C-corps is equally compelling. Founders who hold Delaware C-corp stock for at least five years may qualify to exclude up to $15 million in capital gains under IRC Section 1202 Qualified Small Business Stock (QSBS) — a benefit the 2025 One Big Beautiful Bill Act enhanced to a full 100% exclusion for five-year holders. LLCs and S-corps are categorically ineligible. If there is any realistic path to a publisher buyout or acquisition, form the C-corp now. Review the full entity decision in Promise Legal's entity formation guide.

IP Ownership: The Assignment Trap Most Founders Walk Into

Most indie studios own less of their game than they think. The assumption is simple: we paid the artist, so we own the art. Federal copyright law does not share that assumption. Under 17 U.S.C. § 101, a work created by an independent contractor is only a "work made for hire" if it falls within one of nine specific statutory categories — and none of those categories include standalone game art, character designs, music compositions, or engine code. Outside those nine categories, copyright belongs to the creator by default, regardless of who paid.

The fix is a signed written assignment. Under 17 U.S.C. § 204, a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights conveyed. An oral agreement, a course of dealing, or payment alone are legally insufficient to transfer copyright. The good news is that the writing requirement is minimal — courts have held that a one-line signed statement is enough. This is not a complex document; it is a signature on a simple clause in your contractor agreement. The only failure mode is not doing it.

The problem surfaces during publisher due diligence. When a publisher or acquirer reviews your studio, their attorneys will ask for signed IP assignment agreements from every contractor who contributed to the game. The IGDA's M&A guidance is explicit: sellers should require all employees and independent contractors to sign agreements assigning all rights to the developed IP to the studio. Missing assignments from a character artist hired two years ago, or a composer hired through a freelance platform, can stall or kill a deal — not because the work is disputed, but because ownership cannot be demonstrated.

The assignment trap is a formation problem, not a litigation problem. Studios that solve it at incorporation — by including a short IP assignment clause in every contractor agreement from day one — never face the audit gap. Studios that discover it during publisher review face a retroactive signature hunt that is time-consuming, legally uncertain, and occasionally impossible when the original contractor has disappeared.

Trademark Registration for Your Game Title and Characters

In 2011, Mojang filed a trademark application for "Scrolls" — the title of a new card game. Bethesda, owner of the Elder Scrolls franchise, immediately contested it. The resulting dispute ran for months before a settlement was reached: Mojang kept the name for the game but gave up the trademark registration, and Bethesda agreed not to challenge the commercial use as long as Scrolls did not directly compete with Elder Scrolls. No damages changed hands, but the legal costs were real and the distraction during active development was significant. The lesson for indie studios is not that you will face Bethesda — it is that a clearance search before you commit to a title costs far less than a dispute after you've shipped.

A video game title requires trademark protection in two classes. Class 9 covers the downloadable software (the game itself), and Class 41 covers entertainment services (online multiplayer, streaming, and the interactive service layer). Filing in only one class leaves material exposure. As of January 18, 2025, the USPTO replaced TEAS Plus and TEAS Standard with a single $350-per-class base application fee — meaning a dual Class 9 + Class 41 filing costs a minimum of $700 in USPTO fees. Additional surcharges apply if you use free-form identification language rather than the USPTO's ID Manual terms ($200 per class extra). A filing with counsel — including the clearance search — typically runs $1,500–$3,000 total.

The clearance search must cover both the USPTO's Trademark Electronic Search System (TESS) and common law uses. Unregistered trademark rights arise from actual commercial use, even without federal registration, and can support a cease-and-desist against a later filer. Common law searches should include domain name registries, app store listings, social media handles, and general internet searches for competing uses of the same or confusingly similar name.

Character names and distinctive visual designs can also be registered as trademarks — a protection that supplements copyright and survives far beyond any individual game's commercial lifespan. Studios planning sequels, merchandise, or licensing revenue should treat character trademark registration as part of the initial IP stack, not a follow-on task.

Copyright in Game Assets: What You Own and What You Don't

Copyright protection in video games has a precise scope that surprises many founders. Under 17 U.S.C. § 102(b), copyright does not extend to any idea, procedure, process, system, or method of operation — regardless of how it is expressed. That means game mechanics are not copyrightable. The concept of matching falling blocks, the loop of a roguelike run, the rules of a battle royale shrinking zone — none of these are owned by anyone. The clone game industry exists because of this rule, and it is operating legally.

What copyright does protect is specific creative expression. In Tetris Holding, LLC v. Xio Interactive (D.N.J. 2012), the court drew exactly this line: while Tetris gameplay mechanics are not protected, the visual expression of the game — the shape proportions of the pieces, the board dimensions, the color scheme, the scoring display — is copyrightable. Xio Interactive copied the mechanics without copying the visual expression and still lost, because the visual similarity was close enough to constitute infringement. The practical takeaway: your game art, your character designs, your UI layout, and your narrative text are protected the moment they are created and fixed in a tangible medium. Mechanics are free; expression is yours.

The AI-generated asset question has become significant. The US Copyright Office confirmed in its January 2025 guidance that prompts alone do not provide sufficient human control to make a user the author of AI-generated output. A studio that built its entire art pipeline on Midjourney or Stable Diffusion may hold no copyright in those assets — meaning it cannot stop others from copying them, cannot license them exclusively to a publisher, and may face due diligence problems at an acquisition. Studios using AI tools need to ensure meaningful human creative selection and arrangement is part of the workflow, and should document that involvement.

Third-party middleware licenses are a separate ownership issue. Unity, Unreal Engine, FMOD, and Wwise each impose terms on commercial use, sublicensing, and platform porting. A publisher deal may require sublicensing the game under terms your engine license does not permit. Review every middleware agreement for transferability clauses before entering any publisher or M&A discussion — acquirers and publishers verify this as part of due diligence.

Contractor Agreements: Protecting the Studio When Working with Freelancers

Every contractor a game studio hires creates two layers of legal exposure: one for the IP they create, and one for whether they are properly classified as a contractor in the first place. The IP layer was covered in section two. The classification layer is where studios incur unexpected payroll tax liability.

The IRS applies a three-category common-law test — behavioral control, financial control, and type of relationship — to determine whether a worker is an employee or an independent contractor. Misclassifying an employee as a contractor exposes the studio to back payroll taxes (both employer and employee shares), penalties under IRC § 3509, and potential benefits liability. The rates under § 3509 run from 1.5% to 3% of wages for income tax withholding and up to 20% for FICA on the employer side, depending on whether the misclassification was intentional. This is not a theoretical risk — the IRS conducts employment tax audits, and game development creates the behavioral control patterns (deadlines, revision cycles, directed work product) that auditors flag.

California adds a harder threshold. Under AB5's ABC test, a worker is presumed to be an employee unless the hiring entity can show (A) the worker is free from direction and control, (B) the worker performs work outside the usual course of the hiring entity's business, and (C) the worker is customarily engaged in an independently established trade. Prong B is the problem: if your studio hires a game programmer or a character artist, their work is squarely within the usual course of your business. Studios with California-based freelancers face serious misclassification exposure that the IRS federal test would not generate.

Every contractor agreement for a game studio should include five provisions: an IP assignment clause, a confidentiality obligation, a non-solicitation clause covering the studio's employees and contractors, defined deliverables and acceptance criteria, and a representation that the contractor has rights to any pre-existing IP they incorporate into the work. That last clause — the pre-existing IP representation — is routinely omitted and routinely causes problems when a contractor's prior work shows up in your codebase during due diligence. The agreement does not need to be long. It needs to be complete and signed before work begins. Use a standard contractor agreement template and customize to the engagement.

Co-Founder Agreements and Equity Splits

Consider the scenario: two founders start building a game in January. They agree verbally to split the studio 50/50. One founder leaves in October, ten months in. The game ships eight months later, becomes profitable, and a publisher offers to acquire the studio. The departing co-founder — who has contributed zero work in the final push — holds 50% of the company with no vesting restriction, because nothing was ever written down. This is not an edge case. It is the default outcome when co-founders skip the agreement.

The industry standard is a four-year vesting schedule with a one-year cliff. Under this structure, 25% of each founder's equity vests at month 12, and the remaining 75% vests monthly over the following 36 months. 87% of venture-backed startups use monthly vesting after the cliff, a structure Y Combinator recommends explicitly. If the October co-founder in the example above had signed a vesting agreement, they would have left with zero equity — none of the one-year cliff had been reached. A co-founder who departs at month 24 would leave with 50% of their stake (two years vested). The schedule creates proportional protection without being punitive.

Pre-company IP is the other critical clause. A co-founder who built a game engine, an asset library, or a custom physics system before incorporation owns that IP personally — unless they signed a written assignment to the company under 17 U.S.C. § 204. A verbal agreement to contribute that IP to the studio is legally unenforceable. The co-founder agreement should include a schedule listing all pre-existing IP being assigned and the consideration (equity or nominal payment) in exchange. Industry practice also permits founders to receive retroactive vesting credit for pre-incorporation work — typically applied toward satisfying the one-year cliff for work begun before the entity was formed.

Texas co-founder non-competes are enforceable when they are ancillary to an otherwise enforceable agreement and contain reasonable limitations on time, geography, and scope of activity. Under Texas Business and Commerce Code § 15.50, courts will reform — not void — an overly broad covenant, meaning the studio keeps some protection even if the original scope was excessive. For a game studio, a 12–18 month restriction on developing directly competing games in the same genre is generally defensible; a lifetime ban on game development generally is not. Include the restriction narrowly and it will survive judicial review.

The Acquisition-Ready IP Stack: Getting Your House in Order Before a Publisher Deal or Exit

Publisher and acquirer due diligence for game studios is a verification exercise, not a discovery exercise. By the time a publisher wires an advance or an acquirer signs an LOI, their attorneys have already checked five things: the entity owns all game IP outright, every contractor and employee signed an IP assignment, there are no pending trademark oppositions, third-party asset licenses are transferable to the acquirer, and all middleware and engine contracts permit the transaction. The IGDA's M&A guidance confirms this framework explicitly — legal due diligence spans technical, creative, management, finance, and legal domains, and the IP chain-of-title review is the most common deal-stopper.

The two most frequently missed technical items are GPL-contaminated code and missing software bills of materials. GPL is a copyleft license: if your codebase incorporates GPL-licensed components, the entire combined work must be released as open source. This is not a theoretical compliance issue — the Free Software Foundation has enforced it successfully, and acquirers who discover GPL contamination post-LOI either require a costly remediation or reprice the deal. The Cisco-Linksys acquisition is the canonical example: after failing to detect GPL-licensed software in acquired products, Cisco was forced to release source code publicly rather than reengineer it, forfeiting licensing revenue. For a game studio, GPL contamination in your engine layer or networking stack is a deal-ending finding. An SBOM (Software Bill of Materials) that catalogs every open-source component and its license is now a standard pre-diligence requirement — buyers will ask for it, and not having one introduces delay.

Publisher deal economics underscore why IP clarity matters before you sign anything. The average indie game publishing advance is $318,000, though the median for most indie developers is well under $50,000. Post-recoupment splits average 60% to the developer and 40% to the publisher. Critically, 38% of publishing contracts run in perpetuity — not for a fixed 10-year term, but forever. Signing a perpetual publishing deal with unresolved IP chain-of-title means you are locking in revenue participation on IP whose ownership you cannot fully guarantee. Clean the stack before you negotiate.

The tax exit payoff for founders who built correctly from day one: a Delaware C-corp that qualifies as QSBS under IRC § 1202 allows founders to exclude up to $15 million in capital gains from an acquisition — 100% exclusion for stock held five or more years, as enhanced by the 2025 legislation. That exclusion is unavailable to LLC members and S-corp shareholders. Everything in sections 1 through 6 feeds directly into whether you capture that benefit: entity choice, clean IP assignment, no unresolved ownership disputes, transferable license stack, documented SBOM. The acquisition-ready IP stack is not a separate project. It is the cumulative result of doing sections 1 through 6 on day one.