CD Projekt Ditches 15 Years of REDengine for Unreal Engine 5

Fifteen Years of Proprietary Engine Sacrificed to UE5

REDengine carried three generations of CD Projekt RED games: The Witcher 2 in 2011, The Witcher 3 in 2015, and Cyberpunk 2077 in 2020. This proprietary engine, developed and refined over more than a decade and a half, won't see The Witcher 4. The studio has officially announced the shift to Epic Games' Unreal Engine 5, marking the death of a tool that had consumed considerable person-years of development.

This isn't routine technical surrender. Abandoning an in-house engine means relinquishing fine-grained control over the development pipeline, losing battle-tested internal tools, and stepping away from a codebase every senior developer knew intimately. It's a gamble on the future, complete with the collective learning curve that entails.

Cyberpunk 2077 Isn't the Culprit, but It's in the Room

The studio is careful to state that abandoning REDengine didn't stem directly from Cyberpunk 2077's disastrous launch. It's an understandable clarification—attributing this structural choice solely to 2020's troubles would be reductive. The shift to UE5 reflects much broader concerns: recruitment, ecosystem compatibility, reducing technical debt.

Still, the context lingers. Cyberpunk 2077 exposed the limits of an in-house engine pushed to its absolute breaking point on platforms it wasn't built for. The catastrophic PS4 and Xbox One launch in 2020 revealed a structural fragility that REDengine couldn't overcome alone. CD Projekt RED won't say that's the reason for the change, but it's hard to ignore that this experience weighed on the decision.

Unreal Engine 5: Safety Net and Accelerant

Choosing UE5 isn't incidental. Epic Games has established its engine as the de facto standard across a significant portion of the industry: Fortnite, and also Black Myth: Wukong in 2024 (Game Science), Hellblade II in 2024 (Ninja Theory), and Stalker 2 in 2024 (GSC Game World) all run on UE5. Technologies like Nanite and the Lumen lighting system offer rendering capabilities that would have demanded years of additional R&D to develop in-house.

For CD Projekt RED, UE5 also represents an HR advantage. Recruiting developers fluent in a niche proprietary engine with limited public documentation is structurally harder than attracting talent trained on Unreal Engine, which remains one of the most taught environments in game development schools. The available talent pool is mechanically larger.

What CD Projekt RED Loses in the Switch

The transition carries real costs beyond the symbolism. World-creation tools developed for The Witcher 3 and refined for Cyberpunk 2077—notably REDkit, now available to modders—aren't directly portable. The production pipeline, shaders, AI systems, and navigation tech built over fifteen years will need to be rewritten or adapted in a different environment.

There's also a question of visual identity. REDengine produced recognizable rendering, a certain atmospheric density in environments that contributed to the aesthetic of CD Projekt's games. UE5, used by dozens of studios, sometimes generates a standardization of look—what some call the "UE5 look," that characteristic lighting and ultra-detailed textures that end up resembling each other across games. The studio will need to work hard to preserve its own visual signature within a standardized technical framework.

A Rational Gamble on a Structurally Painful Decision

CD Projekt RED didn't take this decision lightly, and the final result—The Witcher 4—will tell whether the sacrifice was worth it. What's clear right now is that the studio chose pragmatism over technical pride. Fifteen years of REDengine is a legacy, not an absolute competitive advantage against the demands of a next-gen open-world RPG in 2026 and beyond.

It's a defensible choice, perhaps even inevitable. But calling this transition a simple tool upgrade would be dishonest. It's a cultural rupture for a studio that had built part of its identity on the ability to develop its own technology. The next Ciri will have to prove that UE5 can be harnessed in service of a vision—not merely deployed.