Cyberpunk 2077 runs on REDengine 4, CD Projekt Red's fourth and last in-house engine. The studio built Witcher 2 on REDengine in 2011, Witcher 3 on REDengine 3 in 2015, then rebuilt heavily for Cyberpunk's dense first-person Night City — and then killed the whole line to move The Witcher IV and the Cyberpunk sequel to Unreal Engine 5.
That funeral is the real lesson. Most postmortems say REDengine was simply bad. I think that misses the point: REDengine was the right tool for Witcher's fields and the wrong tax for Night City's vertical density, first-person closeness, and last-gen consoles. CDPR did not switch to Unreal because Unreal draws prettier neon. It switched to buy hiring, documentation, and console-first discipline it could not build alone.
What REDengine 4 actually is
REDengine is CD Projekt Red's proprietary lineage, not a licensed middleware:
- The Witcher 2: Assassins of Kings shipped May 17, 2011 on REDengine, and sold over 8 million copies by September 2014 Witcher 2 history and sales.
- The Witcher 3: Wild Hunt shipped May 2015 on REDengine 3, won 200+ Game of the Year awards, and had sold over 65 million units as of May 2026 Witcher 3 engine and sales.
- PCGamingWiki lists REDengine's first release as 2011 and its three anchor games as Witcher 2 (2011), Witcher 3 (2015), and Cyberpunk 2077 (2020) REDengine release timeline.
- Cyberpunk 2077 credits REDengine 4 as its engine, built by a team of around 500 people with a new Wroclaw division plus help from Nvidia, Q-LOC and others Cyberpunk engine and team.
In other words, REDengine was never a general-purpose product. Only CDPR used it. That is what makes it a search niche: players keep asking what engine Cyberpunk 2077 uses because the answer is not Unity or Unreal, and the follow-up question is always why it was abandoned.
Cyberpunk itself is hot by any measure. It launched December 10, 2020 for PlayStation 4, Stadia, Windows and Xbox One, followed by PlayStation 5 and Xbox Series X/S in February 2022, Nintendo Switch 2 in June 2025 and macOS in July 2025 Cyberpunk release history. As of July 2026 it had sold over 40 million copies, with total development plus marketing plus updates reportedly between $436 million and around $440 million Cyberpunk sales and cost. A sequel was announced in October 2022 and remains in development Cyberpunk sequel announcement.
What REDengine gained — and what Night City charged
For Witcher 3, REDengine 3 was a strength. Third-person, horseback distance, forests and villages forgive streaming pops. You are 10 meters behind Geralt, moving at horse speed, looking at horizons. The engine could prioritize vistas, weather, and quest scripting over pixel-perfect close geometry.
Cyberpunk changed three conditions at once:
First-person closeness. You play V in first-person as a cybernetically enhanced mercenary in Night City, California, chasing the Johnny Silverhand biochip story Cyberpunk first-person premise. First-person makes every low-res texture, pop-in sign, and traffic LOD swap sit 50 cm from your eyes. Witcher could hide a late load behind a hill. Night City cannot.
Vertical density, not horizontal sprawl. Night City has seven regions — City Center, Watson, Westbrook, Heywood and others — stacked with overpasses, markets, alleys and interiors Cyberpunk Night City structure. Density is more expensive than area. A forest streams one biome. A city block streams traffic AI, pedestrians, neon signage, reflections, audio occlusion, and quest triggers in every direction, including above and below you.
PC-first scaling down. The Witcher IV postmortem is explicit: Cyberpunk was developed PC-first and then scaled down, which caused serious performance issues on Xbox One and PlayStation 4 at launch. For the next Witcher, CDPR flipped to console-first because it is easier to scale up than down Console-first lesson from Cyberpunk.
Launch paid that bill in public. Critics praised narrative, setting and graphics, but widely criticised bugs and glitches especially on PlayStation 4 and Xbox One Cyberpunk critical split. Sony removed the game from the PlayStation Store from December 2020 to June 2021 while CDPR fixed issues, and class-action claims over downplayed severity ended in a $1.85 million settlement Sony removal and settlement. Only later updates, the Phantom Liberty expansion, and the 2022 Edgerunners anime drove a progressive reappraisal Reappraisal via updates and Edgerunners.
My read, and this is where I depart from most engine obituaries: this was not a renderer failure. It was a city-density tax plus a platform-scope mistake. If Cyberpunk had been third-person Witcher-with-guns in empty Badlands, REDengine 4 would have been remembered as fine. Put that same engine in a first-person vertical city on 2013 Jaguar CPUs, and every streaming hitch becomes a meme.
Why CDPR killed its own engine
The Witcher IV is now listed with Unreal Engine 5 as its engine, planned for 2028 on PlayStation 5, Windows and Xbox Series X/S Witcher IV on Unreal Engine 5. CDPR is developing it with Unreal Engine 5 after transitioning away from proprietary REDengine — the tech previously used for Witcher 2 and Wild Hunt Transition away from REDengine.
Timeline matters:
- March 2022: CDPR announced a new Witcher game, internally Polaris, to start a new trilogy Polaris announcement.
- May 2022 to November 2024: pre-production, then full production began November 2024 Pre-production to full production.
- Team ramped from 403 members in March 2024 to 499 by March 2026 and 513 by May 2026, over double Witcher 3's core 240-person team Team growth.
After Cyberpunk, CDPR also said it made structural changes to refine phases and foster cohesive design, mandating more complete documentation shared across the company Production reform after Cyberpunk.
Here is my contrarian take: killing REDengine was a recruiting and risk decision, not a graphics decision.
Owning an engine is like owning a power plant. When you have 240 people making one third-person game every four years, the plant pays off — you control streaming, tools, and hiring lore. When you need 500+ people across two AAA open worlds plus console-first certification, ray tracing, path tracing and live patches, the plant becomes a second product you must maintain while shipping the first product. Every graduate knows Unreal. Nobody graduates knowing REDengine 4's Night City streaming. Unreal buys you hires, tutorials, marketplace plugins, and Epic's console optimization labor.
Most commentators frame this as shame — CDPR admitting REDengine was junk. I see it as supply-chain maturity. Witcher 3 proved CDPR could build an engine. Cyberpunk proved it could not afford to maintain one while also fixing a live 40-million-player city on four console generations plus Switch 2 and Mac.
Indie devs should steal the unflattering part: documentation as engine. CDPR's fix was not just Unreal, it was mandating complete shared documentation. Small teams romanticize tribal knowledge. CDPR learned that 500 people cannot run on hallway lore.
What indie devs should actually copy
Do not copy REDengine. Copy the constraints that made it work until it did not:
- Match camera to streaming. Third-person distance forgives. First-person density does not. If you are solo and want a dense city, use third-person or fixed camera to buy 30% streaming headroom.
- Pick console-first, even if you ship PC-first. Decide your weakest target on day one. Cyberpunk's PC-first-then-downscale is the classic indie trap of developing on an RTX machine and discovering your Steam Deck or Switch build needs a rewrite.
- Treat engine ownership as hiring debt. A custom engine is not just code. It is onboarding docs, tools UI, and debug workflows every new hire must learn. If you cannot write the docs, you cannot afford the engine.
- Plan the funeral early. CDPR kept REDengine through two Witchers because it fit. It killed it when the next trilogy needed 500 people and multi-project reuse. Write down what would force you to switch — team size, platform count, multiplayer — before you are forced.
Try the fantasy in a browser first
If you want to feel why Night City driving is a systems problem, not just art, do not reinstall 100 GB. Start with two free browser trainers that isolate the two loops REDengine had to fuse:
When you crave neon cornering without a ray-tracing bill, play Night City Racing — yes, it shares Night City's name. It is a neon supercar game with 10 supercars, 16 Racing tracks against AI, 5 Challenge task maps, and a Free Drive stunt arena. The guide's core tip mirrors Cyberpunk driving: save NOS for corner exits and long straights, use the restart key right after a bad crash instead of reversing out of walls. Practice one clean Racing track to earn coins, then spend engine, agility and brake first before turbo. That handling-first order is exactly what Cyberpunk's street races punish you for ignoring.
When you want the open-world hijack-and-loot rhythm that made REDengine streaming hard, play Sandbox City - Cars, Zombies, Ragdolls. Walk up and press E to hijack any taxi, police car or van, ram hordes on wide roads to save ammo, then get out on foot to grab cash, ammo boxes and cargo crates. Press M for Campaign and Daily missions, P for the shop, T for slow-mo stunts, and toggle Disable Zombies for peaceful cruising and map learning. That drive-to-hotspot, park, loot-on-foot, drive-on loop is V's gig loop in miniature — and it shows why streaming a city with cars plus on-foot interiors is twice the work of streaming wasteland.
Neither browser game proves anything about REDengine internals. They let you practice the design pressures — boost discipline and hijack triage — that broke a proprietary engine at AAA scale.
Bottom line
Cyberpunk 2077 bet on REDengine 4 because CDPR owned it, trusted it from two Witchers, and needed full control over a first-person dense city. It gained art direction freedom and Witcher-honed quest streaming, but paid with last-gen performance debt, a Store delisting, and a $436M+ fix cycle. The studio then did the rarest AAA move: it buried a working engine to buy hiring scale, shared docs, and console-first discipline on Unreal Engine 5.
If you remember one sentence: REDengine did not die because it could not draw neon. It died because only CDPR could hire for it.
Sources and scope
Engine lineage, release dates, sales, costs and platform scope above are as reported on the linked pages, retrieved October 20, 2026. REDengine history covers Witcher 2 (2011) through Witcher 3 (2015) to Cyberpunk 2077 (2020); Unreal Engine 5 applies to The Witcher IV (planned 2028) and the announced Cyberpunk sequel, not to the shipped 2020 game. Browser trainer details reflect EasyHub's current guides and may vary by portal version.
Top comments (0)