Loading…

Unity Software (U) backlog: remaining performance obligations

How much revenue Unity Software already has under contract, how fast it converts, and who it is with.

Data as of .

Unity Software backlog history

$0$1B$2BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$597M$2.18B0.3 yrs$249M
30 Jun 2026$505M$2.03B0.2 yrs$237M
31 Mar 2026$526M$1.92B0.3 yrs$230M
31 Dec 2025$494M$1.85B0.3 yrs$224M
30 Sep 2025$441M$1.80B0.2 yrs$226M
30 Jun 2025$400M$1.78B0.2 yrs$219M
31 Mar 2025$309M$1.79B0.2 yrs$188M
31 Dec 2024$334M$1.81B0.2 yrs$186M
30 Sep 2024$327M$1.97B0.2 yrs$190M
30 Jun 2024$352M$2.06B0.2 yrs$176M
31 Mar 2024$357M$2.15B0.2 yrs$170M
31 Dec 2023$384M$2.19B0.2 yrs$187M

Questions

What is Unity Software's backlog?
Unity Software reported $597M of remaining performance obligations at 30 Sep 2026, up 35% from a year earlier and up 18% from the previous quarter. That is 0.3 years of trailing revenue already under contract. Book-to-bill last quarter: 1.15.
How fast does Unity Software's backlog turn into revenue?
Over the last twelve months Unity Software recognised revenue equal to about 444% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.