Why Call of Duty Bet on the IW Engine: The Boring Quake-III Heir Behind 500 Million Copies — And Why 60fps Beat Pretty Graphics

Short answer: Call of Duty runs on Infinity Ward's proprietary IW engine, a 20-year incremental fork that started from id Tech 3 (the Quake III Arena engine) for Call of Duty 2 onward. Infinity Ward stuck with it instead of switching to Unreal because COD sells feel — locked 60fps, low input lag, readable sightlines, and a yearly pipeline three studios can ship on — not screenshot realism. The current line is IW 8.0 for Modern Warfare (2019) and Warzone, and IW 9.0 for Modern Warfare II (2022) onward, unified across Infinity Ward, Treyarch, Sledgehammer and Raven.

That choice looks unfashionable next to Unreal Engine 5 or Frostbite. It is the reason COD still exists as a yearly product.

The question players actually Google

“What engine does Call of Duty use?” is one of the most repeated engine questions in shooters. Google suggests 10 variants — what engine does cod use, what engine does warzone use, what engine does call of duty mobile use, what graphics engine does call of duty use — and Bing suggests the same cluster plus iw8, iw engine, call of duty game engine. The franchise page confirms the scale behind the curiosity: over 500 million copies sold as of October 2023, 100 million monthly active players, $30 billion revenue by 2022, and Guinness verification as the best-selling FPS series ever.

The answer changed by era, which is why so many forum answers contradict each other:

• 2003 Call of Duty: id Tech 3 derivative. Infinity Ward was founded in May 2002 by 22 ex-2015 Medal of Honor: Allied Assault developers, funded with $1.5 million for 30% by Activision, then fully acquired in October 2003 the day after COD 1 shipped.
• 2005–2016 (COD 2 to Infinite Warfare): IW 2.0 through IW 7.0 — same lineage, renamed each generation.
• 2019–2020 (Modern Warfare reboot + Warzone): IW 8.0, described as “an entirely new engine” with photogrammetry, streaming and ray-tracing support, shipping October 25, 2019 and powering Warzone’s 150-player Verdansk.
• 2022–present (Modern Warfare II, Warzone 2.0, Modern Warfare III, Black Ops 6/7): IW 9.0, “powered by a new version of the IW engine,” released October 28, 2022 and the fastest COD to $1 billion in revenue. Activision calls this the unified engine — all studios on one base with shared tools, cross-play and one Call of Duty HQ launcher.

id Tech 3 itself lists the IW engine as its successor alongside id Tech 4, noting IW was used from Call of Duty 2 onward. That single sentence explains 20 years: COD never rewrote, it forked.

Why not Unreal? Three constraints most explainers miss

Most articles say “Activision wanted control.” That is true but vague. The specific constraints were:

1. 60fps is the product, not a setting

From Call of Duty 2’s Xbox 360 launch — 1.4 million units in year one with an 85% attach rate to new Xbox 360s — Infinity Ward locked 60fps on console while competitors targeted 30fps with better lighting. IW’s renderer, job system, streaming and audio mixer were all budgeted backward from that number: smaller maps with dense occlusion, baked lighting + selective dynamic lights, aggressive LOD, 60Hz server tick targets, and animation cut to preserve input latency.

Unreal could do 60fps, but Epic’s demo-driven roadmap in 2006–2014 prioritized visual features over COD’s exact latency budget. Owning the engine let Infinity Ward say no to a pretty feature that cost 3ms. Licensees cannot say no that easily.

2. Three studios, one calendar

Since 2005 Activision ran a rotation: Infinity Ward improves the engine for one game while Treyarch ships on the updated prior engine, then they swap. Sledgehammer and Raven later joined. That only works if the API is boring and stable.

A third-party upgrade — say Unreal 3 to Unreal 4 in 2014 — would have forced all four studios to retool at once and broken the yearly ship date that funds everything. The IW fork let them merge features incrementally: Treyarch’s Zombies systems, Sledgehammer’s traversal, Raven’s Warzone live-ops tooling, all back-ported into IW 8.0/9.0.

The 2022 unification was an admission this had partially failed — by 2020 each studio had drifted into its own IW branch, which is why Warzone integrations broke weapons and file sizes ballooned past 200GB. IW 9.0 was less a new engine than a forced re-merge.

3. Netcode and tools over renderer

id Tech 3’s snapshot + delta-compression + Huffman UDP netcode gave COD a head start on 12–18 player 60Hz matches, then 64-player Ground War and finally 150-player battle royale with cross-play and cross-progression. Warzone hit 6 million players in 24 hours and 100 million downloads by April 2021 on IW 8.0 — a scale test Unreal licensees rarely attempt with a modified shooter base.

Equally important: COD’s content factory — Gunsmith with up to 60 attachments per gun, seasonal weapons, operators, maps — needs artist tools that non-engineers can run. IW’s editor chain is ugly but purpose-built for that factory. General engines optimize for being general.

What IW gained — and what it cost

Gained:

• Consistent gunfeel across 20 games. A Modern Warfare 2 (2009) player can pick up Black Ops 6 and aim correctly in 30 seconds.
• Scalability from 6v6 to 150 players without changing engines. Warzone’s Buy Stations, Loadout Drops, Gulag 1v1 respawn and Plunder economy were added as modes, not rewrites.
• Live-ops speed: seasons, weapon tuning, anti-cheat updates ship without waiting on Epic or DICE.
• Photoreal-ish reboot without losing speed: Modern Warfare (2019) reworked multiplayer for tactical play, added 100+ player Ground War, Gunfight 2v2, and sold over 30 million units by September 2020 while keeping 60fps on base PS4/Xbox One.

Cost:

• Visual ceiling. Frostbite’s destruction (Battlefield) and UE5’s Nanite/Lumen still embarrass IW in tech demos. COD maps are corridors with skyboxes, not fully destructible cities.
• File size and tech debt. Three merged branches + 4K assets + Warzone = infamous 200GB+ installs.
• Single-player compromise. Modern Warfare II’s campaign is praised but its water physics, swimming and vehicle hijack systems feel bolted on compared to a purpose-built open-world engine.
• Talent moat that cuts both ways. Twenty years of internal knowledge makes hiring fast for COD, slow for anyone else — new engineers must learn a Quake-III-descended codebase no school teaches.

My take: the engine is a calendar, boredom is the moat, and “dated” is strategy

Here is where I diverge from the usual “COD engine old, Unreal better” consensus. I think three contrarian points explain COD better than any renderer comparison:

1. IW is not a renderer, it is a release calendar compiled to C++.

Unreal asks “what could you render?” IW asks “can three studios ship every October at 60fps without crunching the tools team to death?” That reframes every “why not switch” debate. Switching engines would not just change graphics — it would cancel a $30-billion yearly cadence for 2–3 years. No board approves that to get nicer reflections. Frostbite’s mandate at BioWare (Dragon Age, Mass Effect) proved the opposite: forcing an FPS engine onto RPG teams for corporate synergy broke games. Activision avoided a mandate by letting each COD studio keep its IW branch — until drift forced the IW 9.0 re-merge. Boring incrementalism beat grand unification for 15 years.

2. 60fps is not a tech spec, it is a brand promise that filters the audience.

Most critics compare still screenshots. Players buy motion. COD’s low time-to-kill (150–300ms) only feels fair at 60fps+ with low latency. Drop to cinematic 30fps and every death feels like lag, no matter how good Lumen looks. My read: Infinity Ward correctly treated 3ms of input latency as more valuable than any lighting feature. That is why “COD looks dated” never hurt sales — readability is the feature. Enemies must pop against the background at 100 meters while sprinting. Photoreal clutter would make the game worse.

3. The fork-don’t-rewrite doctrine is the real lesson, and Warzone proved its limit.

Twenty years of forking Quake III sounds insane until you list the alternative graveyards: id Tech 5/6 pivots, Frostbite RPG rewrites, Slipspace for Halo Infinite. IW survived by never rewriting. But Warzone exposed the bill: when Verdansk, Rebirth Island, Caldera and Fortune’s Keep had to share one client across Modern Warfare, Black Ops Cold War and Vanguard content, loadout and weapon-balance parity collapsed. Unified IW 9.0 + Call of Duty HQ was not innovation — it was debt collection. Indie devs should copy the first 15 years (fork, don’t rewrite) and heed the last 5 (schedule the re-merge before three branches become three engines).

If I were advising a small FPS team, I would steal COD’s order of operations: lock tick rate + target fps first, lock map size + player count second, choose renderer third. Most indies do it backward.

What indie devs can steal this week

• Budget backward from feel. Pick 60fps or 120fps on your weakest target hardware, then cut features to hold it. Do not add Lumen-style features and hope optimization saves you.
• Build the Gunsmith, not the gun. COD’s 60-attachment tuning system looks like content, but it is retention: players theory-craft instead of churning. A tiny attachment + stat-bar system beats 10 more guns.
• Design modes as content, not code. Gulag, Plunder ($1M cash race), Resurgence (respawn while squad lives), DMZ extraction — all shipped as modes on IW 8.0/9.0. Prototype modes first; engine features second.
• Unify late, but unify. If you fork for DLC or co-dev, schedule a merge milestone. COD waited too long and paid in gigabytes.

Train these COD fundamentals free in your browser

You cannot practice Warzone’s 150-player rotations without installing 200GB, but you can drill the underlying skills that IW rewards — positioning, loadout switching, and objective discipline — in lightweight browser shooters.

If you die because you take fair 1v1s in the open, run BuildNow GG on EasyHub. Its five modes — Freebuild, V-Arena, BoxFight, Zone Wars and Aim Training map directly to COD drills: Freebuild for 90s and high-ground takes (think rotation to circle), BoxFight for edit-peek shotgun timing (think Gulag 1v1s), Zone Wars for final-circle positioning with a shrinking zone. The page’s sensitivity 3–6, FOV 90–100, and shotgun-vs-rifle-by-range advice is the same logic as COD Gunsmith range discipline.

If you lose because you chase kills and ignore objectives, run Hazmob FPS: Online Shooter. Its seven documented modes — Team Deathmatch, Free for All, Capture the Flag, Domination, Search and Destroy, Elimination and Gun Race with 55+ customizable weapons force the Domination/Capture-the-Flag lesson COD players learn late: standing on the point with teammates wins more than distant kills. Start with Team Deathmatch to learn one map’s lanes, then Domination for rotations, then Search and Destroy for no-respawn patience — the same progression from 6v6 to Search to Warzone.

Neither browser game replicates IW’s netcode or recoil, but both train the decisions IW punishes: open-field peeks, wrong gun at wrong range, and solo pushes without cover. Fifteen minutes of BoxFight peeks + one Domination match is a better warm-up than another YouTube loadout video.

FAQ

Does Call of Duty use Unreal Engine?
No. Mainline COD has never shipped on Unreal. It shipped on id Tech 3 derivatives, then IW 2.0–9.0. Call of Duty Mobile uses Unity (TiMi), Warzone Mobile uses a mobile-adapted IW branch — which is why mobile feel differs.

What is the current COD engine?
IW 9.0, introduced with Modern Warfare II (2022) and shared across Warzone 2.0, Modern Warfare III (2023) and Black Ops 6 (2024) via the unified engine + Call of Duty HQ launcher. IW 8.0 powered Modern Warfare (2019) and Warzone 1.0.

Why does COD still hit 60fps on old consoles?
Because the engine budgets everything else around it: map size, player count, lighting, and file size all yield to frame time. That is the Quake-III inheritance — snapshot netcode, delta encoding and lean OpenGL roots optimized for speed over spectacle.

Should indies copy IW?
Copy the doctrine, not the code. You cannot replicate 20 years of tools, but you can replicate the discipline: lock fps, fork boring tech, build artist tools early, and prototype modes before rewriting renderers.

Engine history moves fast: Modern Warfare 4 is scheduled for October 23, 2026 and Black Ops 7 launched November 14, 2025 per the series timeline — expect IW 9.x iterations, not a rewrite, unless Activision announces otherwise.