Unity's Pricing, Two Years After the Runtime Fee

PGP Studio Team · April 28, 2026 · 6 min read

The runtime fee is gone, prices are up 5%, and trust is still the real line item. Where Unity's business model actually stands in 2026.

Two years is enough distance to evaluate a business model decision on its actual track record rather than the panic of the announcement itself, and Unity's pricing history since the 2023 Runtime Fee controversy is worth revisiting with exactly that kind of distance. Unity canceled the per-install Runtime Fee in September 2024, roughly a year after the original announcement triggered what remains one of the most consequential trust crises in recent engine history. Under new CEO Matt Bromberg, the company committed publicly to a different operating model going forward: a predictable, traditional cycle of price reviews, annual only, with no surprise mid-cycle changes sprung on studios already deep into a production cycle.

The Commitment Actually Held, Which Is Itself Notable

That commitment has, so far, held through 2026 in a way that is worth stating plainly rather than treating as unremarkable. Unity raised Pro and Enterprise subscription prices by 5 percent in January, the first increase since the Runtime Fee was scrapped entirely, and framed it explicitly as exactly the kind of predictable, once-a-year adjustment the company had promised rather than a surprise mid-cycle change. A 5 percent annual increase, announced on a predictable schedule and consistent with a stated policy, is a genuinely different category of event than an unannounced per-install fee retroactively applied to already-shipped games, and treating the two as equivalent risks would be both inaccurate and unfair to a company that has, on this specific metric, done what it said it would do.

That said, 'did what it said it would do for two years' and 'trust fully restored' are not the same claim, and it is worth being precise about which one the evidence actually supports. A predictable price increase is table stakes for any software vendor, not a special achievement; it is the baseline behavior a customer should expect by default, and Unity is currently being credited for meeting a baseline it violated once already. That is a real, earned improvement, and also a lower bar than 'trustworthy' implies in the abstract.

The HDRP Decision Is the More Consequential 2026 Signal

The pricing predictability is the headline that gets covered, but the more consequential 2026 decision for studios building high-end 3D content is a quieter one: Unity put the High Definition Render Pipeline into maintenance mode, effectively stepping back from flagship, top-tier 3D rendering ambitions to redirect resources elsewhere. For a studio our size, working primarily in mobile-scale 2D and lightweight 3D, that decision has close to zero direct impact. For a studio building AAA-adjacent or visually ambitious 3D console and PC titles specifically on Unity's high-end pipeline, it is a considerably bigger deal than a 5 percent subscription price adjustment, and it is worth flagging as the more important signal in this year's Unity news for exactly that category of studio.

Reading the two decisions together tells a coherent story about where Unity is currently allocating its resources and, by extension, where its own confidence in future investment lies. A company doubling down on predictable subscription pricing while simultaneously stepping back from its most resource-intensive rendering pipeline is a company optimizing for stability and cost discipline over chasing the highest end of the visual fidelity market, which Unreal Engine has arguably already claimed more convincingly. That is not necessarily the wrong strategic bet for Unity to make, but it is a different bet than 'compete directly with Unreal at the top end,' and studios building for that top end should read the HDRP decision as a real signal about where Unity's own roadmap confidence currently sits, not as an isolated technical footnote.

Why We Still Architect for Portability

Our own position, both for our published catalog and for client engagements, has not fundamentally changed despite two years of Unity behaving predictably on pricing. We still architect projects to keep porting options reasonably open rather than betting everything irreversibly on one engine's roadmap, and that is not a statement of ongoing distrust of Unity specifically so much as a general engineering discipline that would apply to any single-vendor dependency this central to a studio's entire output.

Concretely, that means favoring engine-agnostic asset pipelines where the cost of doing so is low, documenting platform-specific integration points clearly rather than letting them become tangled, undocumented dependencies buried in a project, and periodically sanity-checking that a hypothetical migration, however unlikely to actually happen, would not be catastrophically harder than it needs to be. None of that slows down current Unity development meaningfully; it is closer to an insurance policy with a low ongoing premium than a hedge that trades off real production speed today.

What a 'Traditional Cycle' Actually Buys a Studio

The practical value of Unity's predictable annual review cycle, if it continues to hold as it has for two years now, is that it lets a studio budget for engine costs the way it budgets for any other recurring vendor expense: with a known, bounded annual variance rather than an open-ended risk of an unannounced structural change to the pricing model itself. That is a genuinely useful planning input for any studio sizing out a multi-year roadmap against a licensing cost line item, and it is worth acknowledging as real progress rather than dismissing the entire post-Runtime-Fee period as unearned goodwill.

Where we remain cautious is in extrapolating two years of good behavior into an assumption of permanent stability. Two years is a meaningful track record, but it is also exactly the kind of track record a company under new leadership, trying visibly to rebuild trust after a self-inflicted crisis, has the strongest possible incentive to maintain. The real test is what happens further out, once the immediate memory of the Runtime Fee backlash has faded from industry conversation and the pressure to visibly behave well eases. We will keep watching the annual review cycle specifically for whether it stays this disciplined once that pressure naturally diminishes.

Our Bottom Line for Studios Evaluating Unity Today

For a studio evaluating whether to build a new project on Unity today, the honest 2026 assessment is that the business model risk that dominated the conversation in 2023 has meaningfully receded without fully disappearing. Two years of predictable, announced pricing is real evidence of changed behavior, not just changed messaging, and the HDRP maintenance-mode decision is a more useful signal about Unity's actual strategic priorities than the pricing news gets credit for being. We continue to recommend Unity for the mobile, casual, and cross-platform work that describes most of our own catalog and client base, while keeping enough architectural discipline in place that a future pricing surprise, however less likely than it was in 2023, would not be an existential event for a project built on it.

How This Plays Out in an Actual Client Contract Conversation

When we scope a new client engagement that will run on Unity, the pricing history covered here comes up explicitly during the initial planning conversation, not as background trivia but as a genuine input into how we structure licensing cost line items in a project budget. We now present Unity's licensing cost as a known, budgetable annual line item with a documented track record of predictable adjustment, rather than the open-ended risk conversation this same discussion would have required in late 2023 or early 2024, when no client conversation about Unity could avoid addressing the Runtime Fee directly and at length.

That shift in how the conversation itself has changed is, in its own way, real evidence of restored functional trust, independent of whether every studio has fully forgiven the original 2023 decision. A pricing conversation that used to require defending the platform's basic predictability now takes a few minutes and moves on to the actual project scope, and that compression is a meaningful, if understated, signal about where things genuinely stand two years on.

What We Would Flag as a Warning Sign Going Forward

If we were watching for an early signal that Unity's pricing discipline was starting to slip again, the specific thing we would flag is any deviation from the stated annual-only review cadence, even a small one, more than the size of any individual price increase itself. A company that occasionally announces an off-cycle adjustment 'just this once, for a specific reason' is exhibiting exactly the pattern that preceded the original 2023 crisis, regardless of how reasonable any single off-cycle justification sounds in isolation. Consistency of process matters more here than the magnitude of any individual increase, and it is the specific thing worth watching for rather than assuming two clean years guarantees a third.

A Final Word on Why This Still Gets Coverage

It might seem like litigating a 2023 decision two full years later is dwelling on old news rather than covering something current, but the reason this topic still warrants annual revisiting is that engine choice is one of the most consequential, hardest-to-reverse decisions a studio makes, and the trust dynamics around a platform holder's pricing behavior compound slowly over years, not in a single news cycle. A studio evaluating Unity today deserves an honest, current answer grounded in two years of actual behavior, not a frozen snapshot of sentiment from the worst week of the 2023 crisis, and providing that updated, dispassionate read is exactly the service a piece like this is meant to provide.

We will keep revisiting this specific topic on the same annual cadence Unity itself has committed to for its own price reviews, since a yearly check-in matches the actual pace at which anything meaningful is likely to change here. Anything shorter would be reacting to noise; anything longer risks missing an early warning sign before it compounds into a repeat of 2023.

How Client Contracts Have Actually Changed Since 2023

One concrete, practical change we made to our own client contract templates in the aftermath of the Runtime Fee episode was adding an explicit clause addressing how a mid-project engine licensing change would be handled, including who bears the cost and what the renegotiation process looks like if it ever happens again. That clause has never actually been invoked in the two years since, and we hope it never needs to be, but having it in writing before a crisis rather than negotiating it during one is exactly the kind of preparation that a studio only thinks to do after living through the alternative. We recommend the same to any other studio drafting client agreements around Unity-based work, regardless of how much goodwill the platform has rebuilt since. We hold every long-term vendor relationship, not just Unity, to this same standard now: a track record measured in years, not a single good quarter, before we treat a past trust issue as fully resolved rather than merely improving. Whatever happens next in Unity's pricing history, our own architectural discipline around portability stays in place regardless, since it costs little to maintain and protects against exactly the kind of surprise this whole saga was originally about.

Weighing this pricing history against a genuine alternative is a real question for some teams, and our Godot vs Unity in 2026 piece takes that comparison head-on. Platform risk like this factors directly into how we scope every Unity and XR engagement we take on.