Engine licensing in 2026: seat fee or royalty wins

Every mobile studio picks an engine early, usually before revenue exists to weigh against the decision. Years later, that early choice is quietly costing a specific, calculable amount of money every year — and in 2026, the numbers on both sides of the ledger changed enough that it's worth actually running the math again instead of assuming the choice you made at zero revenue is still the right one at your current scale.

What each engine actually charges

Unity's pricing moved again this year. Unity Pro rose 5% on January 12, 2026, to $2,310 per seat per year, up from $2,200 — a flat, predictable annual cost regardless of how much the game earns. Unity Personal stays free up to $200,000 in revenue or funding, so a small team hasn't hit this cost yet, but it's a known number waiting at a known threshold. The runtime fee Unity floated and then cancelled in September 2024 isn't part of the current model — this is a straightforward per-seat license, not a per-install charge.

Unreal Engine runs the opposite structure: free until $1 million in lifetime gross revenue, then a 5% royalty on revenue above that line. There's no seat fee, no monthly cost while you're building — the cost only starts once the game is actually making real money, and it scales with revenue rather than headcount.

Godot charges neither. It's MIT-licensed, with zero royalties and zero seat fees, permanently. It went from a hobbyist tool to a credible production engine with its 4.6 release, which is the real story in 2026 — the zero-cost option got materially better at the same time the paid options got a little more expensive.

The math that actually matters

A seat fee and a royalty behave completely differently depending on team size and revenue, which is exactly why "which engine is cheaper" doesn't have one answer — it has one answer per studio.

A small team with a handful of engineers on Unity Pro is paying a fixed cost that doesn't move with revenue: five seats is roughly $11,550 a year whether the game earns nothing or earns millions. That's a real cost at the pre-revenue stage, and it's a rounding error once the game is genuinely profitable.

Unreal's royalty does the opposite. It costs nothing while you're building and testing, nothing in the first year of a modest launch, and then starts taking 5% of everything above $1 million — which, for a genuinely successful game, is a much larger absolute number than a handful of Unity seats ever would be. The tradeoff is real: Unreal is cheaper for a studio that's small, pre-revenue, or has a game that never breaks past that $1 million line. It gets more expensive than Unity, potentially by a wide margin, for a studio with a big team and a hit on its hands.

Godot removes the tradeoff entirely by removing the cost. The honest caveat is that "free" isn't the same as "equivalent" — Unity's roughly 48% mobile market share and the fact that it powers about 70% of top-grossing mobile games reflects a maturity in mobile-specific tooling, third-party plugin ecosystems, and studio hiring pools that a zero-cost engine doesn't automatically match just because the license is free. Godot 4.6 closed a lot of that gap for 2D and mid-complexity 3D titles, which is why it's now a genuine production option rather than a curiosity — but it's still worth verifying it covers your specific technical needs before treating the cost savings as the whole decision.

Where each engine actually fits

Unreal Engine 5 remains the realistic choice when a project genuinely needs cinematic 3D rendering on high-end phones — that capability isn't cheaply replicated elsewhere, and for a studio building toward that visual bar, the royalty is the cost of a capability with no real substitute. For most mobile studios building 2D, mid-complexity 3D, or hybrid-casual titles, the rendering ceiling isn't the constraint, which is where the seat-fee-versus-royalty math actually becomes the deciding factor instead of a technical requirement making the choice for you.

Running the decision honestly

The mistake is treating this as a one-time choice locked in at project start. It's worth revisiting at two points specifically: before you scale team size (because seat fees compound with headcount in a way that's easy to underestimate) and before you project past the $1 million revenue line on Unreal (because that's the exact point the royalty math flips from "free" to "a genuine cost against your margin").

Run the actual numbers for your specific team size and your realistic revenue projection, not the industry-average framing either engine's marketing uses. A five-person team building toward a modest, sustainable hit looks very different in this math than a fifteen-person team building toward a genuine breakout. The engine choice you made at zero revenue was a reasonable bet with the information you had then — it's worth checking whether it's still the right bet now that you have real numbers to run it against, the same way you'd want real revenue data behind any other recurring cost decision your studio makes.