Royalty and Revenue Share Models

Royalty and revenue share models represent the financial frameworks that game engine providers employ to monetize their platforms while enabling developers to create and distribute games ¹². In the context of Unity and Unreal Engine—the two dominant game development platforms—these models fundamentally shape the economic relationship between engine creators and game developers, directly impacting project budgets, profit margins, and long-term financial planning ¹². Unity historically operated on a subscription-based model with tiered pricing, while Unreal Engine pioneered a revenue-sharing approach charging royalties on gross revenue after specific thresholds ¹². Understanding these models is critical for game developers, studios, and publishers as they ultimately influence which engine developers choose for their projects and how they structure their business operations.

Overview

The emergence of distinct royalty and revenue share models in Unity and Unreal Engine reflects the evolution of game development economics over the past two decades. Unity's subscription-based model traditionally centered on tiered subscriptions (Personal, Plus, Pro, and Enterprise) with annual or monthly payments, where developers pay regardless of revenue generation ¹⁴. Conversely, Unreal Engine's model exemplifies a royalty-based approach, historically charging 5% of gross revenue after the first $1 million per product per calendar quarter ²³.

The fundamental challenge these models address is balancing accessibility for developers with sustainable revenue for engine providers. Subscription models transfer financial risk to developers who pay upfront regardless of success, while royalty models align engine provider success with developer success, creating shared risk ¹². This distinction has profound implications for studios of different sizes and financial capabilities.

The practice has evolved significantly, particularly in recent years. Unity's 2023 announcement of a "runtime fee" model drew substantial criticism from the development community and was subsequently revised ⁵⁸. Epic Games introduced strategic exemptions, waiving Unreal royalties for games published exclusively on Epic Games Store, which takes its own 12% cut instead of the industry-standard 30% ⁹. These changes demonstrate how revenue models continue to adapt to market pressures, developer feedback, and competitive dynamics between the two platforms.

Key Concepts

Revenue Thresholds

Revenue thresholds represent the earnings level that triggers royalty obligations or tier changes in engine licensing models ²³. These thresholds determine when developers must begin paying fees or upgrade their subscription levels. Unreal Engine's $1 million quarterly threshold per product means many indie developers never pay royalties, while Unity's Personal tier remains free only up to $100,000 annual revenue ¹².

For example, consider an independent studio developing a narrative-driven adventure game. If they use Unreal Engine and their game generates $800,000 in its first quarter, they owe no royalties to Epic Games. However, if the same game generates $1.3 million in the second quarter, they would owe 5% of the $300,000 exceeding the threshold—$15,000 in royalties. Under Unity's model, if their annual revenue exceeds $100,000, they must upgrade from the free Personal tier to Plus at $399 annually, regardless of whether they earn $101,000 or $1 million.

Gross Revenue Calculation

Gross revenue represents total income before deductions, forming the basis for royalty calculations in Unreal Engine's model ²¹⁰. This includes all monetization streams: direct sales, in-app purchases, advertisements, downloadable content, and any other revenue generated by the product. Understanding what constitutes gross revenue is critical for accurate royalty reporting and financial planning.

Consider a free-to-play mobile game built with Unreal Engine that generates revenue through multiple streams: $600,000 from in-app purchases, $300,000 from advertising, and $200,000 from a premium battle pass system in a single quarter. The gross revenue totals $1.1 million, exceeding the threshold by $100,000. The developer owes 5% of that excess—$5,000—even though platform fees (typically 30% on mobile) and payment processing fees significantly reduce their net income. This calculation method can create substantial royalty obligations for high-revenue, low-margin games.

Seat Licensing

Seat licensing refers to per-user subscription costs where each developer using the engine requires a separate license ¹⁴. This model, employed by Unity for its Pro and Enterprise tiers, scales costs with team size rather than revenue. The approach creates predictable expenses but can become costly as teams grow.

A mid-sized studio with 15 developers using Unity Pro faces annual costs of $30,600 ($2,040 per seat × 15 developers) ¹. If the studio expands to 25 developers during a successful project, their annual Unity costs increase to $51,000. In contrast, the same studio using Unreal Engine pays no upfront costs regardless of team size, though they would owe royalties on successful products. This distinction makes Unreal particularly attractive for studios with large teams but uncertain revenue prospects, while Unity's model benefits smaller teams with predictable revenue.

Platform-Specific Exemptions

Platform-specific exemptions are special provisions that waive or modify standard royalty obligations based on distribution channels ⁹. Epic Games waives Unreal Engine royalties for games published exclusively on Epic Games Store, creating strategic incentives for platform adoption. These exemptions fundamentally alter the economic equation for developers.

An indie studio developing a multiplayer shooter faces a critical decision: publish on Steam with its 30% platform fee while paying 5% Unreal royalties on gross revenue, or publish exclusively on Epic Games Store with its 12% platform fee and zero Unreal royalties. For a game generating $2 million in revenue, the Steam route yields $1,330,000 after platform fees (30%) and royalties (5% of gross), while Epic Games Store exclusivity yields $1,760,000 after only the 12% platform fee—a difference of $430,000. This 32% increase in net revenue creates powerful incentives for Epic Games Store exclusivity, though developers must weigh this against Steam's larger user base.

Custom Licensing Agreements

Custom licensing agreements allow large studios to negotiate alternative arrangements with reduced rates or different payment structures ¹². AAA studios often secure custom deals that fundamentally change the economic relationship, though specific terms typically remain confidential. These negotiations recognize that major studios bring significant value to engine providers through high-profile titles and technical feedback.

A AAA studio planning a major franchise entry with projected revenue exceeding $100 million might negotiate a flat-fee license with Epic Games rather than paying the standard 5% royalty. Instead of owing $5 million in royalties (5% of $100 million), they might negotiate a $2 million flat fee, saving $3 million while providing Epic with guaranteed revenue regardless of the game's ultimate performance. Similarly, studios might negotiate reduced royalty rates (perhaps 2-3% instead of 5%) in exchange for multi-year commitments or technical collaboration on engine development.

Quarterly Reporting Requirements

Quarterly reporting requirements mandate that developers track and report earnings accurately to engine providers when thresholds are exceeded ²¹⁰. For Unreal Engine, developers must submit royalty reports and payments each calendar quarter when their product generates revenue exceeding $1 million. This creates ongoing compliance obligations throughout a product's commercial life.

A studio with a successful live-service game built on Unreal Engine must implement comprehensive tracking systems capturing revenue from PlayStation Network, Xbox Live, Steam, Epic Games Store, and direct sales. Each quarter, they compile sales reports from all platforms, calculate total gross revenue including microtransactions and season pass sales, determine the amount exceeding the $1 million threshold, compute the 5% royalty, and submit payment with detailed documentation to Epic Games. This process continues for years as long as the game remains commercially active, requiring dedicated accounting resources and robust financial systems.

Break-Even Analysis

Break-even analysis helps developers determine the revenue point where Unity subscription costs equal Unreal royalties, informing engine selection decisions ¹². This methodology provides a quantitative framework for comparing the two models, though it requires careful consideration of multiple variables including team size, revenue projections, and development timeline.

For a solo developer comparing Unity Pro ($2,040 annually) against Unreal's 5% royalty, break-even occurs at approximately $40,800 annual revenue (where 5% equals $2,040) ¹². Below this threshold, Unity Pro costs more than Unreal royalties would; above it, Unity becomes more economical. However, this calculation becomes more complex with Unreal's quarterly $1 million threshold—a game earning $900,000 quarterly ($3.6 million annually) pays zero Unreal royalties, making Unreal dramatically more economical than Unity Pro's fixed cost. Only when quarterly revenue consistently exceeds $1 million does the royalty model begin accumulating costs that might eventually exceed Unity's subscription fees.

Applications in Game Development Contexts

Indie Development with Uncertain Revenue

Small independent studios developing their first commercial title typically face significant financial uncertainty and limited capital ¹². In this context, Unreal Engine's zero-upfront-cost model with deferred royalties provides crucial accessibility. An indie team of three developers creating a narrative adventure game over two years can access Unreal's full feature set without any engine costs during development ². If the game launches but generates only $400,000 in total revenue, they pay zero royalties while benefiting from AAA-quality rendering and tools. This risk-sharing model has enabled numerous indie success stories, including games like "Hellblade: Senua's Sacrifice," which benefited from deferred costs during uncertain development periods.

Mid-Sized Studios with Predictable Revenue

Established studios with proven track records and predictable revenue streams often prefer Unity's subscription model for its cost certainty and budgeting simplicity ¹¹². A studio with 20 developers working on multiple mobile games generating consistent annual revenue of $5 million can budget exactly $40,800 annually for Unity Pro licenses ($2,040 × 20 seats). This fixed cost remains constant regardless of whether revenue reaches $4 million or $6 million, simplifying financial planning and investor reporting. The subscription model also serves multiple projects simultaneously—the same 20 licenses support development across several titles, whereas Unreal's per-product royalty calculation means each successful game incurs separate obligations.

AAA Development with High Revenue Potential

Major studios developing blockbuster titles with revenue projections exceeding $50 million face different economic considerations ¹². At this scale, Unreal's standard 5% royalty would amount to millions of dollars, making custom licensing negotiations essential. A AAA studio might negotiate a reduced royalty rate or flat-fee arrangement, fundamentally changing the economic equation. Additionally, these studios often maintain relationships with both Unity and Unreal, selecting engines on a per-project basis. They might use Unreal for graphically intensive single-player experiences where its rendering capabilities provide competitive advantages, while using Unity for live-service games where its robust multiplayer networking and cross-platform tools offer benefits.

Free-to-Play and Live-Service Games

Games employing free-to-play models with microtransaction revenue face unique considerations under these licensing frameworks ¹⁰. Unreal's gross revenue calculation includes all monetization streams—in-app purchases, advertising, battle passes, and cosmetic sales. A mobile game generating $10 million quarterly from microtransactions would owe $450,000 in Unreal royalties (5% of $9 million exceeding the threshold), even though platform fees and payment processing reduce net revenue significantly. For such games, Unity's fixed subscription cost might prove more economical, as a team of 30 developers would pay only $61,200 annually regardless of microtransaction revenue. This dynamic has influenced engine selection for many mobile and free-to-play developers, particularly those expecting high gross revenue but operating on thin margins after platform fees.

Best Practices

Implement Comprehensive Revenue Tracking Systems

Developers using Unreal Engine must establish robust analytics and financial tracking infrastructure that captures all revenue streams across platforms ²¹⁰. The rationale is straightforward: accurate royalty reporting depends on complete revenue data, and underreporting can trigger audits and penalties. Implementation requires integrating analytics systems with all distribution platforms—Steam, Epic Games Store, PlayStation Network, Xbox Live, mobile app stores, and any direct sales channels. Tools like custom dashboards that aggregate platform sales reports, in-app purchase data, advertising revenue, and DLC sales provide real-time visibility into gross revenue. For example, a studio should implement automated monthly reconciliation processes that compare platform payment statements against internal tracking, identifying discrepancies before quarterly reporting deadlines. This infrastructure also supports strategic decision-making by providing clear visibility into which revenue streams contribute most significantly to royalty obligations.

Conduct Break-Even Analysis Before Engine Selection

Developers should perform detailed financial modeling comparing total cost of ownership across both engines before committing to a platform ¹². The rationale extends beyond simple subscription versus royalty comparison to include asset store costs, plugin expenses, training investments, and development time differences. Implementation involves creating financial models with multiple revenue scenarios (pessimistic, realistic, optimistic) and calculating total costs over the expected product lifecycle. For instance, a studio projecting three years of development followed by five years of commercial operation should model Unity subscription costs for eight years across their team size, compare this against Unreal royalties under different revenue scenarios, and factor in platform-specific exemptions like Epic Games Store exclusivity. This analysis should account for platform fees (typically 30%), payment processing fees (2-3%), and refunds (industry average 2-5%) to calculate net revenue accurately.

Set Revenue Monitoring Alerts for Tier Transitions

Unity developers should implement proactive monitoring systems that alert them when approaching tier revenue limits ¹⁴. The rationale is avoiding compliance violations and unexpected cost increases by upgrading tiers before exceeding limits. Implementation involves setting alerts at 80% of tier thresholds—for example, at $80,000 annual revenue for the Personal tier's $100,000 limit. This provides sufficient time to budget for tier upgrades and adjust financial projections. A practical example: a studio using Unity Personal should configure their accounting system to send alerts when trailing twelve-month revenue reaches $80,000, triggering a review of whether to upgrade to Plus ($399 annually) or restructure their approach. This proactive monitoring prevents situations where unexpected success forces rushed tier upgrades or temporary compliance issues.

Maintain Detailed Financial Records for Audit Readiness

Both Unity and Unreal developers should retain comprehensive financial documentation for at least five years, supporting potential audits and model changes ³. The rationale recognizes that engine providers retain auditing rights and licensing terms can change, requiring historical documentation. Implementation involves establishing document retention policies that preserve platform sales reports, payment statements, revenue breakdowns by source, and correspondence with engine providers. For example, a studio should maintain quarterly archives containing Steam sales reports, mobile app store payment summaries, advertising revenue statements, and internal calculations showing royalty computations or tier compliance. This documentation proves invaluable if Epic Games exercises audit rights or if Unity modifies its terms and developers need to demonstrate which license version governed their development period.

Implementation Considerations

Financial Infrastructure and Accounting Tools

Implementing these revenue models requires appropriate financial infrastructure scaled to organizational size and complexity ¹⁰. Small indie studios might use spreadsheet-based tracking integrated with platform payment notifications, while larger studios need enterprise accounting systems with automated platform integrations. For example, a solo developer using Unreal Engine might maintain a quarterly spreadsheet tracking Steam revenue, itch.io sales, and Epic Games Store income, manually calculating royalties. In contrast, a 50-person studio needs accounting software that automatically imports sales data from multiple platforms, categorizes revenue by product, calculates royalties in real-time, and generates quarterly reports. Tool selection should consider integration capabilities with major platforms, support for multi-currency transactions, and reporting features that align with royalty calculation requirements.

Team Size and Organizational Structure

Unity's seat-based licensing creates different cost dynamics based on team composition and structure ¹. Studios must decide whether all team members require Pro licenses or if some can use Personal tier for non-commercial work. For example, a 30-person studio might determine that only 20 developers directly working on commercial projects need Pro licenses ($40,800 annually), while 10 team members in administrative, marketing, or support roles don't require licenses. This requires clear organizational policies defining who needs licenses and processes for adding licenses as teams grow. Conversely, Unreal's team-size-agnostic model simplifies this consideration but requires different organizational discipline around revenue tracking and reporting rather than license management.

Multi-Project Portfolio Management

Studios developing multiple simultaneous projects face distinct considerations under each model ¹². Unity's seat licenses serve all projects a developer works on, making the per-seat cost amortize across the portfolio. A studio with 25 developers working on five different games pays $51,000 annually regardless of how many projects succeed commercially. Unreal's per-product royalty calculation means each successful game incurs separate obligations—five games each generating $2 million quarterly would collectively owe $250,000 in quarterly royalties (5% of $5 million total exceeding thresholds). This dynamic influences portfolio strategy: studios might use Unreal for experimental titles with uncertain returns (paying nothing if they fail) while using Unity for established franchises with predictable revenue (benefiting from fixed costs regardless of success magnitude).

Platform Strategy and Distribution Channels

Distribution platform selection interacts significantly with revenue models, particularly given Epic Games Store exemptions ⁹. Developers must evaluate whether Epic Games Store exclusivity's royalty waiver outweighs Steam's larger user base and higher platform fees. Implementation requires modeling revenue under different scenarios: a game projected to sell 100,000 copies at $30 might generate $2.1 million on Steam (after 30% platform fee) minus $55,000 in Unreal royalties (5% of $1.1 million exceeding threshold), netting $2.045 million. The same game on Epic Games Store might sell only 60,000 copies due to smaller user base but generate $1.584 million (after 12% platform fee) with zero royalties, netting $1.584 million. This $461,000 difference requires careful market analysis of platform reach versus fee structures.

Common Challenges and Solutions

Challenge: Accurate Revenue Tracking Across Multiple Platforms

Developers using Unreal Engine face significant complexity tracking gross revenue across diverse platforms with different reporting formats, payment schedules, and currency conversions ¹⁰. A game distributed on Steam, Epic Games Store, PlayStation Network, Xbox Live, Nintendo eShop, iOS App Store, and Google Play receives sales reports in different formats, with varying payment cycles (monthly, bi-monthly, quarterly), and multiple currencies. Missing revenue from any source creates underreporting risks, while manual aggregation is error-prone and time-consuming. The challenge intensifies for games with multiple revenue streams—base sales, DLC, in-app purchases, advertising, and physical distribution—each requiring separate tracking.

Solution:

Implement automated revenue aggregation systems that integrate with platform APIs and standardize reporting ¹⁰. Many platforms offer API access to sales data—Steam's partner API, Apple's App Store Connect API, and Google Play Console API enable automated data extraction. Developers should invest in middleware solutions or custom integrations that pull data from these sources, convert currencies to a standard denomination, and aggregate totals by product and quarter. For example, a studio might implement a monthly automated process that queries all platform APIs, downloads sales reports, applies current exchange rates for currency conversion, categorizes revenue by type (base sales, DLC, microtransactions), and updates a central dashboard showing quarterly gross revenue trending toward or exceeding the $1 million threshold. This automation reduces manual effort, minimizes errors, and provides real-time visibility into royalty obligations.

Challenge: Forecasting Revenue for Engine Selection Decisions

Developers beginning new projects face significant uncertainty predicting revenue, making it difficult to determine which licensing model offers better long-term value ¹². A new indie studio developing their first commercial game has no historical data to inform projections, while even established studios face uncertainty with new genres or platforms. Overestimating revenue might lead to choosing Unity's subscription model when Unreal's royalties would have been cheaper, while underestimating might result in choosing Unreal when Unity's fixed costs would have proven more economical. The challenge compounds with multi-year development cycles where market conditions, platform popularity, and competitive landscapes shift substantially.

Solution:

Develop comprehensive financial models incorporating multiple scenarios with sensitivity analysis ¹². Rather than single-point revenue forecasts, developers should create pessimistic, realistic, and optimistic scenarios, calculating total cost of ownership under each. For example, a studio might model: pessimistic scenario ($200,000 lifetime revenue), realistic scenario ($1.5 million lifetime revenue), and optimistic scenario ($5 million lifetime revenue). For each scenario, calculate Unity costs (subscription × years × team size) and Unreal costs (5% of revenue exceeding quarterly thresholds). This reveals that Unreal offers better economics in pessimistic and realistic scenarios (minimal or zero royalties) while Unity might prove cheaper in the optimistic scenario (fixed subscription versus substantial royalties). Additionally, developers should research comparable titles—games in similar genres, on similar platforms, from similarly-sized studios—to ground projections in market reality rather than aspirational thinking.

Challenge: Managing Subscription Costs During Team Scaling

Unity developers face escalating costs as teams grow, creating budget pressure during expansion phases ¹. A studio growing from 10 to 30 developers sees annual Unity Pro costs increase from $20,400 to $61,200—a $40,800 increase that might not align with revenue growth timing. This challenge particularly affects studios raising investment capital or experiencing rapid growth, where headcount increases precede revenue increases. The per-seat model can create perverse incentives against hiring or force difficult decisions about which team members receive licenses, potentially limiting productivity.

Solution:

Implement strategic license management with role-based allocation and consider Enterprise tier negotiations for larger teams ¹. Studios should audit which roles genuinely require Pro licenses versus those that could use Personal tier for non-commercial work or no license at all. For example, a 30-person studio might determine that 18 engineers and designers need Pro licenses for commercial development, 7 artists can use Personal tier for asset creation (upgrading only when directly integrating commercial work), and 5 administrative staff need no licenses. This reduces costs from $61,200 to $36,720 annually. For larger teams, negotiate Enterprise agreements that might offer volume discounts or alternative pricing structures. Additionally, studios should budget for license costs as a percentage of headcount in their financial planning, ensuring capital raises or revenue projections account for scaling engine costs rather than treating them as unexpected expenses.

Challenge: Navigating License Term Changes and Retroactive Modifications

Both Unity and Unreal periodically modify their licensing terms, creating uncertainty and potential retroactive cost changes ⁵⁸. Unity's 2023 Runtime Fee announcement proposed charging per-installation fees retroactively, causing significant developer backlash before being revised. Such changes can fundamentally alter project economics mid-development, potentially making previously viable projects financially unworkable. Developers face the challenge of protecting themselves against unfavorable term changes while maintaining access to engine updates and support.

Solution:

Carefully review license agreements to understand which terms apply and whether retroactive changes are permitted, and maintain flexibility to switch engines if necessary ⁵⁸. When beginning projects, developers should document which specific license version governs their development, as many agreements specify that terms in effect when development begins continue to apply. For example, developers who began Unity projects under pre-Runtime Fee terms might be protected from those changes depending on their specific agreement language. Studios should also participate in developer communities and industry organizations that can collectively respond to unfavorable changes—the widespread criticism of Unity's Runtime Fee led to its revision, demonstrating community power. For critical projects, consider maintaining parallel expertise in both engines, enabling migration if one provider implements unacceptable terms. While switching engines mid-development is costly, having the capability provides negotiating leverage and genuine alternatives if licensing becomes untenable.

Challenge: Optimizing Platform Strategy with Revenue Model Implications

Developers must balance platform reach against fee structures and royalty implications, particularly regarding Epic Games Store exclusivity ⁹. Choosing Epic Games Store exclusivity eliminates Unreal royalties but potentially reduces sales volume due to smaller user base compared to Steam. Conversely, launching on Steam maximizes potential reach but incurs both 30% platform fees and 5% Unreal royalties on gross revenue. This creates complex optimization problems where the financially optimal choice depends on price elasticity, platform conversion rates, and marketing effectiveness across platforms.

Solution:

Conduct platform-specific revenue modeling incorporating user base size, conversion rates, and total fee structures ⁹. Developers should research comparable titles' performance across platforms, estimating potential sales volume on each. For example, if market research suggests a game might sell 150,000 copies on Steam but only 80,000 on Epic Games Store (due to smaller user base), model total net revenue: Steam generates $3.15 million gross (150,000 × $30), minus $945,000 platform fee (30%), minus $157,500 Unreal royalties (5% of gross), netting $2.047 million. Epic Games Store generates $2.4 million gross (80,000 × $30), minus $288,000 platform fee (12%), with zero royalties, netting $2.112 million. Despite 47% fewer sales, Epic Games Store yields higher net revenue due to lower combined fees. However, developers should also consider long-term factors: Steam's larger user base might generate more DLC sales, community engagement, and franchise building. Some developers adopt hybrid strategies—launching with Epic Games Store exclusivity for 6-12 months to maximize initial revenue, then expanding to Steam to capture additional market segments.

References

1. Unity Technologies. (2025). Unity Pricing. https://unity.com/pricing
2. Epic Games. (2025). Unreal Engine FAQ. https://www.unrealengine.com/en-US/faq
3. Epic Games. (2020). Unreal Engine End User License Agreement. https://docs.unrealengine.com/5.0/en-US/unreal-engine-eula/
4. Unity Technologies. (2025). Unity Personal. https://docs.unity3d.com/Manual/UnityPersonal.html
5. Game Developer. (2023). Unity Reveals Plans to Charge Per Game Install, Drawing Criticism. https://www.gamedeveloper.com/business/unity-reveals-plans-to-charge-per-game-install-drawing-criticism
6. Reddit. (2023). Unity vs Unreal Pricing Models Comparison. https://www.reddit.com/r/gamedev/comments/16i5gqv/unity_vs_unreal_pricing_models_comparison/
7. Epic Games. (2025). Unreal Engine Release. https://www.unrealengine.com/en-US/release
8. Unity Technologies. (2023). Plan Pricing and Packaging Updates. https://blog.unity.com/news/plan-pricing-and-packaging-updates
9. Game Developer. (2023). Epic Waives Unreal Engine Royalty Fees for Games on Its Store. https://www.gamedeveloper.com/business/epic-waives-unreal-engine-royalty-fees-for-games-on-its-store
10. Reddit. (2021). Understanding the 5% Royalty Fee. https://www.reddit.com/r/unrealengine/comments/pqr8x7/understanding_the_5_royalty_fee/
11. Itch.io. (2025). Creators FAQ. https://itch.io/docs/creators/faq
12. CG Spectrum. (2025). Unity vs Unreal Engine. https://www.cgspectrum.com/blog/unity-vs-unreal-engine