What The Last of Us Part II’s $220 Million Budget Measures

Video game development cost can describe production spending, a capitalized software asset, or a broader lifecycle budget. Sony’s approximately $220 million development disclosure for The Last of Us Part II measures production investment, not the publisher’s complete commercial commitment.

In a declaration submitted in the FTC–Microsoft litigation, Sony described approximately $220 million in development costs for The Last of Us Part II over 70 months, with a peak of about 200 full-time employees. Sony discussed global marketing spending separately without providing a title-level amount. The disclosure did not supply an all-in total combining production, promotion, distribution, and continuing support.

Sony also disclosed $212 million in development costs for Horizon Forbidden West, excluding marketing. Activision’s approximately $700 million figure for Call of Duty: Black Ops Cold War covered lifecycle spending, including post-launch work. Placing those amounts in the same budget ranking obscures a basic operational difference: the figures cover different activities and periods.

A useful analysis therefore starts with what the number measures, rather than its size: which work it covers, when costs enter the calculation, which platforms are included, and which obligations continue after release.

Key Points

• Scope signal: development-only and lifecycle figures describe different spending commitments; their difference is not a measure of production efficiency.
• Accounting risk: capitalized payroll can exclude early project work while including noncash compensation and allocated overhead.
• Launch exposure: Sony’s $220 million development disclosure does not quantify the game’s marketing campaign or complete commercial investment.
• Continuing obligations: ports, patches, infrastructure, moderation, and customer support can extend spending beyond the original release budget.

A comparison framework begins with the cost boundary

“Budget” can refer to planned spending, accumulated expenditure, an accounting asset, or a completed lifecycle total. These are different measurements. A planned production allocation does not establish final spending; a software asset does not capture every project-related expense; and a lifecycle figure may contain years of work beyond the launch build.

The following public figures illustrate the distinction. Release years identify the products, not the accounting periods in which every dollar was incurred.

Publisher, title, and release year	Disclosed amount	Cost boundary	Limit of the comparison
CD Projekt — Cyberpunk 2077 (2020)	$174 million	Development costs	Does not establish a complete global launch or lifetime budget.
Sony — Horizon Forbidden West (2022)	$212 million	Development, excluding marketing	No separate allocation between PlayStation 4 and PlayStation 5.
Sony — The Last of Us Part II (2020)	Approximately $220 million	Development over 70 months; marketing discussed separately	No all-in total or clear treatment of outsourcing in the disclosed amount.
Activision — Call of Duty: Black Ops III (2015)	More than $450 million	Lifecycle spending	No standardized breakdown separating launch development, post-launch work, and other cost categories.
Activision — Call of Duty: Modern Warfare (2019)	More than $640 million	Lifecycle spending	Not equivalent to a pre-release production budget.
Activision — Call of Duty: Black Ops Cold War (2020)	Approximately $700 million	Lifecycle spending, including post-launch work	Does not establish an itemized marketing, infrastructure, or support allocation.

The Sony development disclosures and Activision lifecycle figures answer different questions. Sony’s amounts describe the scale of production for particular releases. Activision’s figures describe a broader commitment to producing and sustaining those games. Neither category, by itself, establishes how much spending was avoidable or how efficiently a studio operated.

A comparable budget record needs the publisher, title, release date, platform scope, cost period, accounting basis, and treatment of marketing and post-launch work. Currency also matters. Nominal dollar amounts associated with releases across different years do not control for inflation, exchange rates, or changes in labor costs.

Capitalized payroll is not the same as total project spending

Labor is frequently the largest production input, but an accounting disclosure may capture only the portion recognized as software development costs. Capitalization means recording qualifying expenditure as an asset rather than immediately recognizing it as an expense. Under the relevant U.S. software accounting treatment, capitalization can begin after technological feasibility is established and continue until general release. Costs incurred outside that window may receive a different accounting treatment.

The categories extend beyond base salaries. PLAYSTUDIOS’ accounting disclosures describe qualifying payroll and payroll-related costs, stock-based compensation, consulting fees, and third-party development fees. Depending on the policy and project stage, directly attributable materials and allocated overhead can also enter the software asset. These policies illustrate the accounting distinction; they do not establish how Sony calculated its $220 million figure.

A project can therefore accumulate substantial work before its reported software asset begins to grow. Concept development, research, feasibility activity, and failed prototypes may be expensed immediately. Later production work may be capitalized. The eventual asset balance can omit real project effort without implying that the effort was costless.

The reverse distinction also matters. Stock-based compensation contributes to accounting cost without matching a contemporaneous cash payroll payment. Allocated overhead assigns shared costs to a project rather than identifying a payment made exclusively for that title. A capitalized development figure is consequently neither a complete cash-spending total nor a simple count of salaries.

Capitalization also changes when costs reach the income statement; it does not eliminate the underlying resource commitment. An analysis combining capitalized additions with later amortization—the recognition of those asset costs as expense—risks counting the same production expenditure twice. The accounting policy and reconciliation between opening balances, additions, amortization, and impairments determine what the reported movement means.

Headcount and duration explain exposure, not a complete budget

Horizon Forbidden West was developed over approximately five years with about 300 staff, alongside its $212 million development figure. For The Last of Us Part II, Sony’s approximately 200 full-time employees represented peak staffing across a 70-month development period. Neither staffing figure supplies a project-wide labor ledger.

Peak headcount is not average staffing throughout production. It may also exclude external art, animation, localization, quality assurance, porting, and co-development teams. Sony’s disclosure did not clarify whether all outsourcing costs were included in the $220 million, and external contributors need not appear in the full-time employee count. Shared engine specialists and central technology groups introduce further allocation differences. Multiplying headline headcount by project duration and an assumed salary therefore produces a model, not a reconstruction of the disclosed budget.

Schedule exposure depends on the work remaining. A delay involving a large production team has a different cost profile from a narrower certification or compatibility phase. Rework, retained contractors, and parallel platform branches can extend expenditure, but these disclosures do not provide a universal monthly cost of delay.

Marketing changes launch exposure without changing the production figure

A game marketing budget can sit entirely outside the amount described as development. Horizon Forbidden West provides an explicit example. For The Last of Us Part II, Sony discussed substantial global marketing costs separately but did not quantify the campaign. That distinction supports treating $220 million as a development benchmark, not assigning a specific additional marketing bill.

Trailers, paid media, events, creator campaigns, retail activity, and regional promotion are not automatically included because a headline calls its number “the cost of the game.” Marketing can be substantial and, in some business models, exceed core development spending. Mobile games have a particularly pronounced paid user-acquisition burden. That does not establish a standard marketing-to-production ratio for AAA—large-budget publisher releases—PC games, or independent projects. Doubling a development disclosure to estimate an all-in launch budget substitutes an assumption for a missing line item.

The operational distinction is between spending that creates the product and spending intended to generate demand. Publishers may combine paid campaigns with platform promotion or an existing franchise audience, but those routes have different dependencies. Evaluating launch exposure requires a separate campaign allocation and clarity about publisher-funded versus partner-funded promotion; the production disclosure supplies neither.

Platform scope can move costs outside the original release

Horizon Forbidden West launched on PlayStation 4 and PlayStation 5, but its $212 million disclosure does not isolate each platform’s contribution. A combined production total cannot reveal how much engineering was shared or how much work addressed different performance targets, memory limits, testing requirements, and certification submissions.

A later PC version creates another boundary. Depending on the title, work can include graphics settings, shader and driver testing, controller and ultrawide support, anti-cheat integration, Steam or Epic Games Store integration, and continuing compatibility maintenance. A budget attached to the original console release does not automatically include that later work.

Simultaneous releases place more platform work inside the initial production schedule. Staggered releases can separate porting expenditure from the original launch, while external porting specialists shift work into development-service fees. These arrangements change timing, coordination, and cost visibility; outsourcing does not remove the underlying engineering or support requirement.

Regional ratings, content restrictions, and storefront access can also change release scope. A worldwide budget figure does not establish availability in every territory, and localization alone does not resolve market-access constraints. The relevant comparison is the set of platforms and territories covered by each amount, rather than an assumed universal porting cost or certification timetable.

Lifecycle budgets capture obligations that survive launch

The approximately $700 million lifecycle figure for Black Ops Cold War is useful precisely because its boundary extends beyond the initial build. Post-launch content and live operations belong to a different operating commitment from completing a release candidate.

Lifecycle spending can include downloadable content, seasonal production, server infrastructure, security, moderation, customer support, analytics, patches, and platform maintenance. Not every title incurs every category, and the Activision totals do not provide a standardized allocation among them. Treating the full amount as launch development overstates the precision of the breakdown.

A patch delivered without a separate player charge still consumes engineering, quality assurance, localization, deployment, and support resources. Some subsequent development may qualify for capitalization, while maintenance and other operating activity may be expensed. “Post-launch” describes timing, not a single accounting category.

Finite support plans and recurring content operations consequently have different risk profiles. A continuing service links future expenditure to content cadence, technical reliability, and player demand. Assessing that burden requires the support period and included activities; active-user measures describe usage but do not reveal the cost of maintaining the service.

What a budget figure can—and cannot—say about market risk

CD Projekt’s Cyberpunk 2077, released in 2020, illustrates the boundary problem in another widely cited number: its $174 million development cost does not establish a complete launch or lifetime budget. The figure describes production scale without resolving every later support, platform, or promotional commitment.

Nor does dividing a budget by a game’s retail price establish a reliable break-even sales threshold. Consumer spending is not publisher receipts: platform and distribution arrangements, discounts, taxes, subscriptions, and continuing costs affect the relationship. A large production number alone cannot explain a studio restructuring or demonstrate that a release underperformed its operating plan.

A usable risk profile separates the disclosed production amount, accounting treatment, release scope, launch campaign, and continuing obligations. Where a component lacks a title-level disclosure, it remains unspecified—not zero, and not a fixed percentage inferred from another game. For The Last of Us Part II, the unresolved marketing amount and outsourcing treatment prevent a complete cost reconstruction; they do not diminish the value of the development disclosure itself.

Conclusion

Sony’s approximately $220 million figure measures development investment in The Last of Us Part II, not a complete commercial cost. Its value as a market benchmark depends on preserving that scope: comparisons with lifecycle budgets require equivalent periods and activities, while profitability analysis also requires publisher receipts and costs beyond production. Without those distinctions, a budget ranking measures disclosure differences as much as production exposure.