Indie Game Studio Formation and IP Basics: What Every Dev Needs to Know

The Legal Gap Most Indie Studios Fall Into

I've seen it more than once: a studio ships a game, gets traction, and then receives a message from a contractor asking for a cut of every sale. Not a bug report. A licensing demand. Under U.S. copyright law, paying a contractor for work does not automatically transfer ownership of that work to you — and without a written IP assignment agreement, the contractor may legally retain rights to the art, code, or audio they created. That means they can demand additional licensing fees beyond what you already paid, or claim a portion of sales revenue retroactively. By the time the game is live and generating revenue, the leverage has shifted entirely to them.

The studio name problem hits at a different stage but with equal force. Iron Maiden held a registered trademark in Class 9 — the class that covers computer and video games — and used it to file a $2 million lawsuit against 3D Realms over the name Ion Maiden. The studio resolved the dispute by renaming the game to Ion Fury. That rebrand happened after the game was already in early access, meaning marketing spend, community goodwill, and search visibility all had to be rebuilt around a new name. A trademark clearance search before launch would have surfaced the conflict in an afternoon. These two failure modes — contractor IP disputes and name conflicts — are almost entirely preventable, and they almost always happen to studios that were focused on shipping rather than structure.

Choosing Your Entity: LLC vs. C-Corp

The single most useful frame for this decision is your funding trajectory. If you are bootstrapping — selling games on Steam, itch.io, or through a publisher deal, with no plans to raise venture capital — a Texas LLC is the right starting point. LLCs have fewer formal requirements than corporations: no shareholder meetings, no board minutes, no governance overhead that pulls founders away from making games. You get liability protection and pass-through taxation, where profits flow directly to your personal return without a corporate-level tax hit first.

If raising venture capital is the plan, form a Delaware C-Corp from day one. Venture capital and institutional investors almost always require a Delaware-domiciled C-Corp — not a Texas LLC, not an S-Corp. The structure enables clean equity incentive plans (ISOs, stock options, ESOP pools) and C-Corp shareholders may qualify for QSBS (Qualified Small Business Stock) benefits, which can allow significant capital gains exclusions after a required holding period. Trying to raise a seed round through an LLC typically means converting anyway, often under deal pressure and on an investor’s timeline rather than your own.

For studios that are not yet sure which path they will take, an LLC is a reasonable default — conversion to a C-Corp is possible later, and it is cleaner to start simple and restructure on your own terms than to build unnecessary complexity into an early-stage studio. In Texas, forming an LLC costs $300 to file a Certificate of Formation with the Texas Secretary of State. You will also need a registered agent and an operating agreement that specifies ownership percentages, decision-making authority, and what happens if a founder leaves. On the tax side, Texas does not impose its franchise tax until annual revenue exceeds $2.65 million — so for most indie studios, the LLC maintenance cost is effectively just the formation fee and registered agent service until the studio reaches meaningful scale.

Who Owns Your Game? IP Ownership and Contractor Clauses

Here is the default rule most studios do not know until it costs them: copyright vests automatically in the person who created the work — not the person who paid for it. A contractor who writes your game’s pathfinding code, draws your character sprites, or composes your soundtrack owns that work the moment it is created. Payment alone transfers nothing. Without a written agreement, the studio has a license at best and nothing enforceable at worst.

Studios often assume the work-for-hire doctrine closes this gap automatically. It does not. Under 17 U.S.C. § 101, work-for-hire applies to independent contractors only when three conditions are all satisfied: the work is specially ordered or commissioned, both parties sign a written work-for-hire agreement, and the work falls into one of nine enumerated statutory categories. Video games do not appear as a named category under § 101 — assets would need to qualify under “audiovisual work” or “contribution to a collective work,” both contested characterizations. This makes the work-for-hire route unreliable for game studios as a standalone ownership mechanism. A handshake, an invoice, or a wire transfer does not substitute for a signed writing, and studios should not rely on work-for-hire alone to establish ownership over contractor-created assets.

The practical structure for every contractor engagement is a two-step check. First, does the deliverable fall into a work-for-hire category? If yes, get a signed work-for-hire agreement before work begins. If you are unsure — and for game assets the answer is often unclear — use an explicit IP assignment clause instead. An assignment transfers ownership directly from the contractor to the studio by written agreement, and it works regardless of whether the work-for-hire doctrine would have applied. As a default, I recommend the assignment route for every contractor relationship. It is simpler, it is unambiguous, and it eliminates the statutory category question entirely.

The same ownership problem appears among co-founders. If you wrote code, built levels, or designed systems before the studio entity existed, that work is owned by you personally — not the LLC or C-corp you later formed. Without a written IP assignment from each founder to the entity, the studio is building on assets it does not legally own. That gap becomes serious the moment you raise outside capital, negotiate a publishing deal, or face any transaction requiring clean title to your IP.

Copyright Registration for Game Assets

You own copyright in your game the moment you create it — but you cannot sue anyone for infringement until you register with the U.S. Copyright Office. More importantly, registration is what unlocks the damages that make litigation worthwhile for a small studio: 17 U.S.C. § 504 sets statutory damages at $750 to $30,000 per infringed work, rising to $150,000 if the infringement is found willful. Without registration, you’re limited to actual damages — which are nearly impossible to prove when a copycat undercuts your game on Steam.

Registration also shifts attorney fees. Under 17 U.S.C. § 505, a court may award a prevailing party’s reasonable attorney fees — which means a registered studio can credibly threaten litigation that an unregistered one cannot. For a two-person shop, that threat alone often resolves infringement without going to court.

The good news for game developers is that a single application covers more than you might expect. The Copyright Office’s Circular 61 confirms you can register your source code (classified as a literary work) and your audiovisual elements — art, animation, UI — together in one application, as long as the same claimant owns both and they were published together as a unit. One game, one filing.

Before launch, the Group Registration of Unpublished Works (GRUW) option lets you bundle up to 10 unpublished works — concept art, music tracks, a code build — into a single $85 application. A standard single application runs $65, and the single-author, single-work option is $45. At those prices, skipping registration is one of the more expensive decisions a studio can make.

Trademark: Protecting Your Studio Name and Game Title

Before you announce your game title publicly, run a clearance search. The consequences of skipping it are concrete: when 3D Realms released Ion Maiden, Iron Maiden’s registered Class 9 trademark triggered a $2 million lawsuit that forced the studio to rename the game Ion Fury. A clearance search isn’t just checking the USPTO database for identical names — it means examining registered marks, designations used in commerce, and company names across adjacent industries, because a trademark held by a band or film studio in Class 041 can still block your game title.

Trademark protects your studio’s commercial identity in the marketplace — the name, logo, or title consumers use to identify your work. That’s a different layer of protection from copyright, which covers the creative content inside the game. A studio that skips trademark registration is leaving its brand exposed even if its code, art, and story are fully protected. For a downloadable game, the relevant filing classes are International Class 009 (computer-based video game software) and International Class 041 (entertainment services such as streaming, esports events, and online community features). Without registering both classes that apply to your actual business, your trademark won’t protect what you’re actually selling.

Common-law trademark rights arise automatically from use in commerce, but they are geographically limited and carry no presumption of validity in a dispute. For a game distributed digitally — meaning you’re effectively operating nationally from day one — common-law rights are a thin shield. USPTO registration gives you an exclusive, renewable right to use the mark commercially, a public record of priority, and the kind of enforceable protection that matters when a larger studio or brand comes calling. First use matters for establishing priority, but it doesn’t substitute for registration when your title is available in every app store and regional boundaries are irrelevant.

Launch Checklist: Entity, Contracts, and IP

The ownership disputes, lost IP, and forced rebrands described above share a common thread: founders who moved fast and skipped the legal foundations. These three checklists address each failure point in sequence.

Entity Formation

1. Choose LLC or C-Corp based on your funding trajectory — bootstrapped studios default to LLC; investor-backed studios form a Delaware C-Corp from day one
2. File your Certificate of Formation with the Texas Secretary of State ($300 filing fee)
3. Designate a registered agent for service of process
4. Draft and execute an operating agreement that governs equity splits, voting rights, and profit distributions

Contractor Agreements

1. Include an explicit work-for-hire designation in every contractor agreement
2. Add an IP assignment clause as a fallback — work-for-hire doctrine has gaps for independent contractors, especially for game assets
3. Require delivery of source files, not just compiled outputs
4. Get a representation that the contractor’s work does not infringe any third-party IP

IP Protection — In Order of Priority

1. Execute co-founder IP assignments to the studio entity on day one, before any code is written
2. Have every contractor sign an agreement before work begins — not after
3. Run a trademark clearance search before locking in your studio name or game title
4. Register copyrights at or before launch (use GRUW for pre-launch assets)
5. File trademark applications in International Class 009 (software/games) and Class 041 (entertainment services)