
Techland has confirmed that Dying Light: The Beast, the latest entry in its zombie survival franchise, will release on August 22 2025 for PC and consoles. Initially conceived as downloadable content for Dying Light 2 Stay Human, the project expanded into a standalone sequel.
The new game marks the return of protagonist Kyle Crane, voiced once again by Roger Craig Smith. Crane’s reappearance comes as a surprise to many, as the character was presumed dead after the events of the first game’s expansion, The Following.
According to the official synopsis, players will explore Castor Woods, a post-apocalyptic tourist destination. After enduring 13 years of experiments, Crane escapes captivity and seeks retribution, uncovering a larger threat in the process.
Gameplay retains the franchise’s emphasis on parkour-based traversal and melee combat. Trailers have shown Crane’s more animalistic fighting style, highlighting brutal close-quarters encounters against both human enemies and the undead. Exploration of the open world remains central, with new mechanics tied to Crane’s transformation.
Players who own the Dying Light 2 Stay Human Ultimate Edition will receive The Beast at no additional cost, a decision stemming from its original status as downloadable content.
Techland has also released system requirements for PC. Minimum specifications include an NVIDIA GeForce GTX 1060 or AMD Radeon RX 5500 XT GPU, Intel i5-13400F or AMD Ryzen 7 5800F CPU, 16GB RAM, and 70GB of SSD storage. Recommended performance requires an NVIDIA GeForce RTX 3070 Ti or AMD Radeon RX 6750 XT. At the higher end, an NVIDIA GeForce RTX 4070 Ti or AMD Radeon RX 7900 GRE is advised, while ultra settings call for an NVIDIA GeForce RTX 5070 or AMD Radeon RX 9070 paired with 32GB RAM.
With its August launch approaching, Dying Light: The Beast promises to expand the series’ world while revisiting one of its most recognisable characters.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ