Unity’s Runtime Fee story ended in cancellation, not a current per-install cost

Unity cancelled its Runtime Fee for games customers on 12 September 2024. Its earlier software-terms post now carries a visible note pointing readers to that outcome. Historical terms post; Cancellation.

Separate historical uncertainty from a current cost

A planning model built while the fee was being discussed may have included scenarios for an installation-linked expense. Those scenarios can remain useful records of the decision environment at the time. They should not survive as unlabelled current costs after the cancellation.

Our recommendation is to search the studio’s budget assumptions and internal guidance for the old fee. Preserve the historical model, identify its purpose and create a current version using the terms that actually apply to the studio. This article does not quote current seat prices or certify any contract.

Do not turn cancellation into a free-engine claim

Removing one proposed charge does not establish that every other cost is unchanged. Engine subscriptions, services and commercial agreements still need their own records. A UA budget should distinguish fixed or allocated development costs from acquisition-linked assumptions rather than collapsing them into one cost-per-install figure.

The follow-up establishes the policy outcome, not the quality of the engine or the financial outcome of switching tools. A further story about a studio’s decision would require its own records and permission. For now, the concrete benefit is correcting the assumption set without rewriting the historical uncertainty out of the archive.

Inspect the evidence

Download the announcement-to-outcome evidence timeline. The extraction separates documented facts from our analysis and unknowns.

Further reading in the existing archive: Unity Enterprise Minimum Commitment: A Blackmail Claim; What Unity's Runtime Vulnerability Patch Means for Ads. These links provide background; this check does not independently verify their full contents.

Frequently asked questions

What happened next, and what should UA change after: Unity’s Runtime Fee story ended in cancellation, not a current per-install cost?

Confirm the Unity Runtime Fee cancellation follow-up already on this URL. Unity cancelled its Runtime Fee for games customers on 12 September 2024; its earlier software-terms post now carries a visible note pointing readers to that outcome. Separate historical uncertainty from a current cost: a planning model built while the fee was being discussed may have included scenarios for an installation-linked expense; those scenarios can remain useful records of the decision environment at the time, but they should not survive as unlabelled current costs after the cancellation. Search the studio's budget assumptions and internal guidance for the old fee; preserve the historical model, identify its purpose and create a current version using the terms that actually apply to the studio — this article does not quote current seat prices or certify any contract. Do not turn cancellation into a free-engine claim: removing one proposed charge does not establish that every other cost is unchanged; engine subscriptions, services and commercial agreements still need their own records. A UA budget should distinguish fixed or allocated development costs from acquisition-linked assumptions rather than collapsing them into one cost-per-install figure. The follow-up establishes the policy outcome, not the quality of the engine or the financial outcome of switching tools. For now, the concrete benefit is correcting the assumption set without rewriting the historical uncertainty out of the archive. No current per-install Runtime Fee is asserted, and no studio contract is certified.