The R&D tax credit for gaming studios
The short answer
Engine, tools, and gameplay systems programming at gaming studios usually qualifies for the R&D credit. Art, audio, and content production without genuine technical uncertainty usually does not.
What qualifies, and what fights you
Gaming studios split their work into two buckets: engine, tools, and systems programming, and content production like art, audio, and level design. The first bucket generally meets the bar for the credit. The second usually does not, unless the studio is solving a genuine technical problem in how content gets made.
The sticking point is separating custom pipeline tooling built to solve a technical problem, which can qualify, from artists using existing tools to make assets, which does not. A tool that automates LOD generation to solve a real rendering constraint is different from an artist modeling a character in Blender using a known workflow.
For most studios, the largest bucket of qualifying spend is gameplay systems programming, especially multiplayer networking. Netcode, procedural generation, and engine modification work tend to involve exactly the kind of uncertainty and iteration the credit is built around.
The four-part test, applied to gaming studios
Qualified purpose for a gaming studio means building or improving the engine, tools, or gameplay systems. Technological in nature means the work relies on computer science, like networking and rendering algorithms, not on art direction or narrative writing. Elimination of uncertainty shows up when a team does not know whether a rollback netcode implementation will keep sessions in sync under real-world packet loss, or whether a procedural generation algorithm will reliably produce playable levels.
Process of experimentation is visible in how a studio gets there: iterating on prediction and reconciliation logic in netcode, tuning generation algorithms against playability constraints, and testing anti-cheat detection against real player data. Failed attempts, like a netcode approach that does not hold up under high latency, still count as evidence of the uncertainty the test requires.
New to the test itself? Read what software work qualifies as R&D first.
Work that usually qualifies
Netcode and rollback systems
Building deterministic lockstep or rollback networking to keep multiplayer sessions synchronized under latency and packet loss.
Procedural generation systems
Building algorithms that generate levels, terrain, or content programmatically within constraints that keep the result playable.
Custom engine or renderer work
Building or substantially modifying rendering pipelines, physics systems, or other engine subsystems, rather than using Unity or Unreal defaults.
Anti-cheat and matchmaking systems
Building detection algorithms and skill-based matchmaking logic where accuracy is genuinely uncertain and has to be validated against real player behavior.
Custom asset pipeline tooling
Building tooling that solves a real technical problem in the content pipeline, like automated level-of-detail generation for large environments.
Work that usually does not
Art and asset production with existing tools
Modeling, texturing, and animating using established tools and workflows involves creative skill, not technological uncertainty.
Level design and dialogue writing
Using the studio's already-built tools to design levels or write narrative content does not involve resolving technical uncertainty.
Which expenses count
W-2 wages for engine, gameplay, and network programmers count as QRE, along with the time technical leads spend supervising that work. Wages for artists and designers generally do not count unless they are directly doing or supervising qualifying technical work.
US-based contractors doing qualifying systems programming count at 65 percent of what you pay them, which matters for studios that bring in specialists for netcode or engine work on a contract basis.
Build farm and playtest infrastructure compute counts as a supply expense. Studios spend real money on continuous integration build farms and playtest server capacity, and that spend supports the testing that the process of experimentation requires.
A worked example
Hypothetical example. A mid-size studio has 12 staff, 6 engineers and 6 artists, plus one contractor on netcode work. Only the engineering wages and the contractor spend count toward QRE.
At roughly 6 to 10 percent of total QRE, the federal credit lands around $37,000 to $61,000. Studios under $5 million in revenue can apply up to $500,000 of that credit against payroll taxes each year.