Unity published a clarified runtime fee FAQ with worked examples after studios said public docs still disagreed on thresholds.
Unity’s latest note is paperwork with consequences: a cleaned FAQ after studios found runtime fee examples that did not agree with each other. No dramatic new formula landed in the headline. The company tried to make the existing story readable. For finance leads, readability is the product.
What to trust
Trust the dated FAQ over a year-old blog comment and over a Discord screenshot. Unity added worked examples for common studio sizes so people can map themselves without interpretive dance. If your last quote deck cited a thread from a prior policy scare, rebuild the sheet.
A clarification can still change someone’s number if they had been using the wrong mental model. That is not the same as Unity rewriting the fee overnight, but it will feel similar in a budget meeting. Bring the FAQ PDF or a dated screenshot into the room.
Studio hygiene
Archive the page. Assign one owner for Unity commercial interpretation. Stop letting five producers maintain five spreadsheets. When Unity updates again—and it will—you want a single diff, not folklore.
Runtime fees became a trust problem as much as a math problem. A coherent FAQ will not heal every bruise, but it beats contradictory docs. Read it once carefully, then stop arguing from memory.
Questions to send Unity in writing
If your studio shape is weird—co-development, work-for-hire, live-ops with shared IP—email Unity with the FAQ paragraph you think applies and ask them to confirm in a ticket. Save the reply next to the FAQ. Verbal assurance from a sales engineer evaporates. Clarified public docs help the common case. Unusual deals still need unusual paper. Do that before the board asks for a single number.
Board one-pager
Summarize the FAQ in five bullets: who pays, when it triggers, what counts as revenue, what examples Unity gave, and what remains ambiguous for your studio shape. Attach the FAQ date. Boards hate surprise platform taxes more than they hate predictable ones. A clarified document is your chance to replace rumor with a shared baseline. If Unity updates again, revise the one-pager the same day—do not let Slack lore outrun the binder.