Does Unity Charge Per Download? How Unity's Runtime Fee Model Actually Works

Unity's pricing model has gone through significant changes in recent years, and the question of per-download charges sits right at the center of one of the most debated policy shifts in game development history. Here's what you need to understand about how Unity charges developers — and what variables determine whether those fees actually affect you.

Unity's Traditional Pricing Structure

For most of its history, Unity operated on a straightforward subscription-based model. Developers paid monthly or annual fees for access to different tiers — Personal (free), Plus, Pro, and Enterprise — and those fees covered the right to use the engine regardless of how many copies of their game sold or were downloaded.

Under this model, Unity made money upfront from developers, not from the downstream success of the games built with the engine. A game downloaded a million times cost the developer the same engine fee as one downloaded a thousand times.

The Runtime Fee: What Unity Announced

In September 2023, Unity announced a significant structural change: the Unity Runtime Fee. This introduced a per-install charge that would apply once a game crossed certain thresholds of revenue and lifetime installs.

The proposed structure worked like this:

  • The fee would only kick in after a game surpassed both a revenue threshold and an install threshold
  • Charges were calculated per new install beyond those thresholds
  • The exact per-install rate varied depending on the developer's subscription tier
Subscription TierRevenue ThresholdInstall ThresholdPer-Install Fee (Proposed)
Personal / Plus$200K annual revenue200K lifetime installs~$0.20 per install
Pro$1M annual revenue1M lifetime installs~$0.15 per install
Enterprise$1M annual revenue1M lifetime installs~$0.125 per install

These figures represent the originally announced structure. Unity subsequently revised the policy after significant developer backlash.

What Changed After the Backlash

The developer community responded strongly against the initial announcement — particularly around concerns like:

  • Retroactive application to games already shipped using older Unity versions
  • Counting reinstalls as new installs (which was later walked back)
  • Free-to-play game economics, where high install counts don't correlate with high revenue

Unity revised the policy in response. Key modifications included:

  • Removing retroactive application to games already in market
  • Clarifying that reinstalls and game pass installs would be handled differently
  • Raising thresholds and reducing rates in some tiers

The specifics of the revised policy continued to evolve, and Unity has since made further structural announcements including leadership changes and re-evaluations of the fee model. Developers building with Unity today should verify the current terms directly from Unity's official pricing documentation, as this has been a moving target.

Which Developers Are Actually Affected 🎮

The per-install fee model is specifically relevant to games built with Unity — not enterprise applications, training simulations, or other software categories. And even within games, the thresholds are designed to exclude most independent developers.

A solo developer releasing a small mobile game is unlikely to cross both the revenue and install thresholds simultaneously. The fee structure targets commercial-scale games with meaningful traction.

Several variables determine whether the Runtime Fee is relevant to a specific developer:

  • Platform — mobile games typically have much higher install counts than PC or console titles for a given revenue level, making the ratio of installs to revenue an important factor
  • Business model — free-to-play games accumulate installs faster than paid games, changing how quickly thresholds are reached
  • Unity subscription tier — higher tiers have higher thresholds before fees apply
  • Game distribution method — games distributed through subscription services like Xbox Game Pass have had specific carve-out considerations in the policy discussions
  • Revenue reporting — the thresholds apply to the developer's overall Unity-built revenue, not just a single title in some interpretations

How This Compares to Other Engines

For context, Unreal Engine uses a royalty model — Epic takes a percentage of gross revenue above a certain threshold rather than charging per install. Godot is MIT-licensed and free with no runtime fees. Each model creates different economic math depending on a game's revenue profile and distribution scale.

The per-install model Unity proposed is structurally unusual in the industry because install counts and revenue don't always move in proportion. A viral free game could theoretically generate significant fees with modest revenue — which was the core concern developers raised.

The Variables That Determine Your Exposure

Whether Unity's per-install fees matter in practice comes down to a handful of factors specific to a developer's situation:

  • The scale of distribution they're targeting
  • The platform mix (mobile vs. PC vs. console)
  • The monetization model (premium, freemium, subscription-distributed)
  • The Unity subscription tier they're on or planning to use
  • The current version of Unity's terms, which have changed and may continue to change

A game targeting a niche PC audience with a paid model sits in a very different position than a mobile title aiming for mass-market free-to-play distribution. The same engine, the same fee structure — but the real-world impact looks completely different depending on the specifics of what's being built and how it's being distributed.