The Witcher IV running on consoles is a milestone, not a final FPS promise

The Witcher IV running on its target platforms during development is an encouraging production milestone. It is not the same thing as a final performance promise. CD Projekt's explanation is most useful when read as a change in when hardware problems are confronted, rather than as a guarantee that those problems have all disappeared.

In Game Developer's August interview, co-CEO Michał Nowakowski described builds running across the target platforms and a process that addresses platform issues at milestones. He contrasted that with assumptions made during Cyberpunk 2077's development about adapting a PC-led project later.

Finding the constraint while the design can still move

The practical value of an early console build is feedback. If a feature is too expensive in memory or rendering time, the team can encounter that constraint while it is still deciding how the feature should work. Waiting until more content depends on it can make the eventual adjustment more disruptive.

That does not mean early builds must already perform like a finished release. Development software changes continuously, and a working build can still contain temporary assets, incomplete optimization and unresolved bottlenecks. The production benefit is having the target machine participate in the decision, rather than treating it as a destination to reach after the main decisions have been made elsewhere.

This is an analysis of a documented development approach, not a newly announced launch date. It also does not establish identical visual settings or frame rates across machines. “Running” describes a useful threshold, but a consumer buying a finished game will care about consistency throughout the experience, not merely whether a build starts.

The Unreal demonstration answers another question

Epic's State of Unreal 2025 report described The Witcher IV technology demonstration running on a standard PS5 at 60fps with ray tracing. It also explicitly distinguished the demonstration from the game itself. The impressive number belongs to that bounded presentation.

A technology demonstration can show that a particular combination of rendering, animation and streaming works under its chosen conditions. A full game has to sustain its behavior across a much broader set of situations. Quests, traversal, encounters and player choices can combine in ways that a guided demonstration does not need to expose.

The two pieces of evidence therefore complement each other without becoming interchangeable. The demo shows a concrete technical result; the production interview explains an effort to keep platform constraints visible during development. Neither alone proves the final game's performance.

Our earlier Witcher 3 update coverage dealt with changes to an already released game, where players can inspect the result. The Witcher IV is at a different stage. The encouraging sign is not that CD Projekt has declared the hardware problem solved. It is that the studio says the hardware gets to object while there is still time to change the answer.