Unreal Engine Royalties, Unity Seats and In-House Engine Economics

Epic’s standard Unreal Engine royalty is 5% on product revenue above a $1 million lifetime threshold, while Unity Pro’s 2026 prepaid annual price is $2,310 per licensed user. The economic choice is between revenue-linked liability, recurring editor subscriptions and an internally funded engineering organization—not simply three prices for engine access.

A game generating $5 million in gross lifetime revenue produces a simplified $200,000 Unreal Engine royalty calculation: 5% of the $4 million above Epic’s stated allowance, before applicable exclusions or contract-specific adjustments. That is a product-lifetime exposure, not an annual editor bill. Comparing it directly with one year of Unity subscriptions mixes different accounting periods and obscures the studio’s actual engine cost.

The framework below uses Epic’s and Unity’s public licensing and pricing position as of October 2026. It separates the charging basis from the wider production burden: royalties, licensed users, negotiated commitments, platform support and the continuing cost of maintaining an engine. A meaningful comparison applies those costs over the same development, release and support horizon.

The public licensing baseline

The principal difference is the unit that creates liability. Epic’s standard game royalty follows product revenue. Unity subscriptions follow licensed users within an organization’s required tier. An internal engine replaces those commercial-engine charges with a studio-funded technical organization.

Licensing model	Charging basis	Public baseline	Main cost boundary
Unreal Engine, standard royalty	Gross lifetime revenue from each product	5% on revenue above the first $1 million, subject to the applicable end-user license agreement (EULA)	Product-revenue definition, exclusions and signed terms
Unity Pro	Licensed editor users	$2,310 per seat per year, prepaid annually, or $210 per seat per month under the 2026 schedule	Required above $200,000 and below $25 million in organizational total finances over the latest 12 months
Unity Enterprise	Contracted subscriptions and services	Custom pricing; minimum subscription or spending commitments may apply	Required at $25 million or more in organizational total finances over the latest 12 months
In-house engine	Internal staffing, tools and ongoing technical support	No standard Unreal royalty or Unity editor subscription for the proprietary engine itself	Engineering capacity, platform coverage, technical debt and support duration

Epic describes its standard royalty on its Unreal Engine licensing page. Unity publishes its subscription prices and Enterprise structure on its plans and pricing page. These public schedules describe baseline commercial terms, rather than the complete cost of shipping and supporting a game. All prices and illustrations below are in US dollars.

1. Scope: product revenue, organizational finances and editor users

The first analytical distinction emerges when the thresholds are mapped to legal entities and products. Unreal’s $1 million allowance concerns a product’s gross lifetime revenue. It is not a studio-wide annual exemption, and development headcount does not determine the standard royalty.

Unity’s tier thresholds concern the organization’s total finances over the most recent 12-month period, not the receipts of a single game. A project with little revenue can therefore sit inside an organization that requires Pro or Enterprise. Unity’s revised thresholds took effect on January 1, 2025, applying at purchase, renewal or upgrade. Unity Personal may apply below the paid-tier threshold, subject to its eligibility terms.

Seat count is a separate variable from tier eligibility. Unity’s licensing FAQ describes a seat as a user license: ten users require ten subscriptions in its example. Total studio headcount is consequently an imperfect proxy. Programmers, artists, designers, technical artists, producers and contractors contribute to the license count when their work requires licensed editor access. Peak simultaneous usage alone does not establish the required user-license count.

The relevant inputs are therefore a product-level revenue ledger for Unreal, an organizational-finances assessment for Unity eligibility, and an editor-user inventory for Unity subscriptions. Combining these into a single “studio revenue” or “team size” assumption loses the distinctions that drive the bill.

2. Unreal royalty exposure: the allowance, revenue base and contract

Under Epic’s stated standard model, the first $1 million in gross lifetime product revenue sits below the royalty trigger. Crossing that threshold does not make the allowance itself royalty-bearing. Applying the public rate to the amount above the allowance produces the following illustrative calculations:

• $5 million in lifetime gross product revenue: $4 million above the allowance, producing $200,000 at 5%.
• $20 million in lifetime gross product revenue: $19 million above the allowance, producing $950,000 at 5%.

These examples isolate the threshold mechanic. The payable amount depends on the applicable EULA, including its calculation, reporting and exclusion provisions. “Gross lifetime revenue” is not interchangeable with the cash remaining after storefront deductions, development spending or marketing costs. Refunds, taxes, bundles, subscription arrangements and downloadable content require treatment under the relevant agreement rather than an assumed net-revenue formula.

Store mix and release timing can also change the calculation. Epic excludes revenue processed through the Epic Games Store from its royalty calculation. Its Launch Everywhere with Epic program offers a 3.5% rate for qualifying products, subject to the program’s release and parity requirements. The simplified 5% examples are therefore baseline scenarios, not forecasts of every product’s payable royalty.

Limited use of Unreal code is another scope issue. Epic states that using any Unreal Engine code, even a small amount, places the product under the Unreal Engine EULA and its royalty provisions. The percentage of the codebase supplied by Epic is therefore not a proportional royalty discount.

The operational trade-off is revenue sensitivity. A small team with a high-revenue game can incur a substantial royalty, while a larger project below the product threshold may generate no standard royalty liability. Neither outcome establishes the full production cost: engine access and the engineering work required to ship remain different categories.

3. Unity expenditure: seats, eligibility and renewal dates

Unity Pro’s 2026 public price is $2,310 per licensed user for a prepaid annual subscription. The monthly price is $210, totaling $2,520 over twelve monthly payments. These are distinct payment schedules, not interchangeable annual prices.

At the prepaid annual rate, 20 licensed users produce $46,200 in annual editor subscriptions; 100 licensed users produce $231,000. Both illustrations assume Pro eligibility and exclude taxes, regional adjustments and negotiated terms. A 100-user organization in the Enterprise financial band cannot use the Pro illustration as its actual Enterprise quote.

Two independent changes can alter the bill: the number of licensed users and the organization’s required tier. Crossing $25 million in total finances moves the organization into Enterprise eligibility even if editor usage remains unchanged. Enterprise pricing is custom, so extrapolating the public Pro rate does not resolve that transition.

Renewal timing adds another boundary. Unity announced a 5% increase for Pro and Enterprise beginning January 12, 2026, with existing subscriptions receiving the new price at renewal on or after that date. Its pricing update also notes regional differences arising from taxes, currency conversion and rounding. A model mixing an existing contract’s price with a later public schedule can misstate the cash requirement during the transition.

The proposed Runtime Fee is not a current payable charge. Unity states that no Unity game has been or will be subject to it. Unity’s Editor terms permit distribution of the Unity Runtime embedded in projects created with Unity 6 or earlier without royalty, revenue share or runtime fee, provided the applicable subscription and tier requirements are met. Version and contract scope matter when describing those rights.

4. Negotiated agreements: a separate cost case

Public pricing and a studio-specific agreement are different inputs. Where a publisher operates under negotiated Unreal terms, the signed agreement determines whether the standard public calculation applies unchanged. Publisher scale alone does not establish a different royalty rate or charging structure.

Unity Enterprise likewise has no universal public per-seat price. Its commercial structure can include minimum subscription or spending commitments. The meaningful comparison therefore includes the quoted commitment, covered users, support scope, deployment rights and renewal provisions—not a hypothetical Enterprise discount applied to Pro pricing.

Negotiation changes which variables are fixed and which remain sensitive to revenue, staffing or renewal. It does not eliminate the distinction between the license charge and the technical work retained by the studio.

5. In-house engine cost: the engineering organization behind the license

An in-house engine removes standard Unreal royalties and Unity editor subscriptions for that engine, but it does not remove the functions those products support. The internal cost base includes engine programming, rendering, tools, build systems, networking, technical art, quality assurance, release engineering and platform support. Third-party middleware can remain a separate expense.

The production distinction becomes clearest at the tools layer. A renderer capable of running a game is not the same asset as a stable production pipeline. Editors, asset importers, profiling tools, automated builds and usable debugging workflows determine how much engineering assistance content teams require. Engine capability and production throughput can diverge.

Platform expansion adds recurring work in graphics application programming interfaces, memory management, input, software development kit (SDK) integration, storefront services, certification fixes and performance tuning. Commercial engines do not remove all title-specific porting or certification work; proprietary engines place more of the underlying compatibility burden inside the studio. Console SDK permissions and platform-holder requirements remain separate from engine ownership.

Technical debt extends the cost beyond initial development. Aging rendering architecture, unsupported middleware, platform-specific workarounds, unstable builds and knowledge concentrated in a few specialists can create continuing liabilities. An existing engine therefore cannot be treated as cost-free simply because its original development spending has already occurred.

An internal engine has no universal sticker price. A defensible estimate depends on the studio’s staffing, shared-engine use across projects, target platforms, release cadence and support obligations. External porting quotes measure a defined delivery task; they do not establish the cost of maintaining the underlying technology organization.

Cost normalization and operational signals

A like-for-like model covers the same development, release and support period for every engine route. Unreal revenue assumptions extend across the product’s commercial life; Unity subscriptions follow the periods in which licensed access continues; internal-engine staffing follows maintenance obligations across supported projects. Engine migration adds another distinct exposure through asset conversion, tool rewrites, retraining and parallel pipelines.

The comparison can be expressed as three cost cases, with the engineering work retained under each route included rather than assumed away:

• Unreal: applicable product royalties over the commercial lifetime, plus studio-funded tools, integration, porting and maintenance work. Gross revenue, store mix and qualifying license terms drive the royalty scenario.
• Unity: licensed users multiplied by the applicable subscription price for each subscription period, plus retained engineering and support costs. Eligibility, user-count changes and renewals determine whether a Pro calculation remains applicable.
• In-house: engine and tools payroll, infrastructure, middleware, platform integration, certification and continuing maintenance. Initial development and ongoing support are separate budget lines; engineers diverted from game production create an additional opportunity cost.

The 20-user Unity example therefore contributes $46,200 for each year at the stated prepaid Pro rate, not $46,200 for the product’s entire life. The $200,000 Unreal example represents the simplified lifetime royalty on $5 million in gross revenue, not an annual charge. An internal-engine case requires a staffing and support budget over that same horizon before either figure becomes a useful comparator. Shared-engine costs across several games also require an explicit allocation rather than charging the entire technology organization to one title.

The resulting analysis has four operational watch points:

• Revenue concentration: a high-revenue product changes standard Unreal royalty exposure even when team size remains stable. Product-level revenue definitions, store mix and applicable exclusions determine the calculation.
• Eligibility and access: Unity’s rolling organizational-finances assessment and editor-user count can move independently. Tier changes, contractor access and renewals are separate cost events.
• Support expansion: additional platforms and longer-lived products extend SDK, certification, build and compatibility work, particularly where the studio owns the engine.
• Contract dependence: negotiated royalties, Enterprise minimum commitments and version-specific distribution terms can change the result without changing the public headline price.

The useful output is a contract-specific cost range over a common production and support horizon, reconciled against product revenue assumptions, licensed-user records and the engine staffing plan. That exposes which liabilities follow commercial success, which follow editor access, and which persist because the studio owns the technology.

Conclusion

Unreal’s standard model makes engine licensing sensitive to product success; Unity makes editor expenditure sensitive to licensed users and organizational eligibility. An in-house engine replaces those vendor charges with a continuing technical organization, not a one-time development bill. The decisive comparison is the studio’s total obligation over a shared product and support horizon—not the smallest headline license charge.