How Witcher Spinoffs Stay Canon-Friendly

The Witcher universe has grown from Andrzej Sapkowski’s novels into a multimedia franchise of globally recognized games, a TV series, and multiple spin-off projects. Every new title set on the Continent brings both excitement and risk: fans want fresh ideas, but those ideas must still feel like The Witcher. That tension becomes especially sharp with spinoff games developed outside CD Projekt Red’s main Witcher RPG team.

This article examines how a recent Witcher spinoff handled those challenges. The studio behind the project worked closely with CD Projekt Red’s lore experts, writers, and producers, repeatedly pitching ideas and adjusting anything that strayed too far from accepted canon. At one point, they even considered something as wild as hordes of zombie witchers — a concept that, unsurprisingly, didn’t survive the vetting process.

By looking at this process, we can better understand how big franchises keep their identity intact while still allowing external teams to experiment, where the line gets drawn for lore, and why even the wildest ideas can be useful in development — even if they never appear on screen.

The Expanding Witcher Universe and Why Canon Matters

Since CD Projekt Red’s The Witcher trilogy popularized Sapkowski’s world, the franchise has become one of the most recognizable fantasy IPs in games. The studio has already confirmed a “new saga” of Witcher titles built in Unreal Engine 5, emphasizing that it intends to keep expanding the universe over the long term.¹ As the franchise grows, consistency becomes more important.

Canon in a transmedia universe like The Witcher serves several roles:

• Protects the tone and atmosphere – Witcher stories live in a morally gray, grounded dark fantasy setting. If a spin-off drifts into pure power fantasy or camp, fans notice instantly.
• Preserves key rules of the world – Witcher mutations, magic systems, and monster ecology follow established logic. Changing those rules casually breaks immersion.
• Keeps characters coherent – Geralt, Ciri, Yennefer, and others have well-defined arcs. New stories can’t casually rewrite their pasts.
• Supports future projects – CD Projekt Red’s upcoming Witcher games must fit with everything that already exists, including spin-offs.

Maintaining that consistency is hard enough when one studio controls everything. It becomes even more complex when external teams or specialized spinoff studios create their own interpretations of the world.

How Spinoff Studios Work With CD Projekt Red

When a partner studio develops a Witcher spinoff, it can’t simply treat the IP as a loose inspiration. CD Projekt Red, as the franchise owner, remains heavily involved in how the world is used and expanded. For the project discussed here, the developers described a process that involved multiple layers of review and feedback.

Key elements of that collaboration typically include:

• Initial concept approval – Before full development begins, the core pitch (genre, timeframe, main protagonist, central mechanic) must be signed off by CD Projekt Red stakeholders.
• Lore consultation – Dedicated lore specialists compare proposed locations, monsters, factions, and magical systems with existing canon from both the books and the games.
• Narrative oversight – Writers and narrative designers at CD Projekt Red review story beats, character arcs, and endings to ensure they do not contradict known events.
• Iterative feedback cycles – As the spinoff changes over time, major story, art, and design revisions go back to CDPR for sign-off.

The result is a kind of creative tug-of-war: the external team pushes for new angles and wild ideas, and CDPR acts as a guardian of tone, history, and internal logic. The best outcomes happen when both sides respect each other’s roles.

Who Are the “Loremasters” and What Do They Do?

One term that often comes up is “loremaster.” While job titles differ between studios, the role typically refers to people who maintain and enforce the franchise’s internal consistency. In large IPs, this can be a formalized team responsible for a living lore bible.

For Witcher projects, a loremaster or lore team might:

• Record important details from all previous games and expansions.
• Cross-check ideas against Sapkowski’s novels and short stories.
• Flag contradictions (for example, resurrecting characters known to be dead or altering the nature of witcher mutations).
• Provide references and material for external writers so they can ground their stories.

This approach is increasingly common in big video game universes. Studios like Blizzard and Riot maintain dedicated lore oversight for World of Warcraft and League of Legends respectively, in order to track an expanding number of stories, spin-offs, and media crossovers.² CD Projekt Red follows a similar pattern for The Witcher, especially as it plans multiple new games and external collaborations.

When Creative Freedom Meets Hard Limits

Spinoff developers are hired precisely because they bring a fresh perspective: different genres, new gameplay systems, or unusual visual styles. But they work under clear constraints. The anecdote about “hordes of zombie witchers” illustrates how the creative process often starts with extremes, which are then pulled back toward something that fits the world.

From a design standpoint, zombie witchers might sound appealing: fast, distinctive enemies that merge familiarity (witchers) with horror (undead). But lore-wise, this idea cuts against what witchers are. They are rare, sterile, heavily mutated monster hunters created through painful rituals, not a mass-producible army that can simply rise from the grave. Bringing them back as hordes would fundamentally undermine the sense that each witcher is almost unique.

Reasons this concept likely drew a firm “no” during reviews include:

• Undermining rarity – Part of the emotional weight in Witcher stories is that witchers are disappearing, not multiplying.
• Breaking magical rules – Resurrection and necromancy in this universe have specific limitations; random mass reanimation of mutated bodies would be a big leap.
• Shifting the tone – A zombie army leans more into pulp horror than grounded dark fantasy.

Even so, exploring such outlandish ideas can be useful. They clarify where the red lines are and sometimes inspire scaled-back concepts that preserve the mood without destroying canon. For instance, the team could pivot to witcher specters, cursed training grounds, or experimental alchemical abominations originating from a single failed school.

Shapes of Acceptable Experimentation in Witcher Spinoffs

Spinoffs often succeed when they experiment in areas that don’t directly rewrite core lore. Some relatively safe zones include:

• New characters within existing structures – Inventing a lesser-known witcher from one of the established schools, rather than rewriting Geralt or Ciri.
• Side stories in untouched regions – Exploring parts of the Continent that were only hinted at in the main trilogy.
• Alternative game genres – Card games, mobile titles, or tactical spin-offs that use the world’s flavor without retelling central arcs.
• Micro-lore expansions – Filling in the history of witcher schools, minor sorcerers, or obscure monster species.

The spinoff highlighted by the GamesRadar article chooses exactly this route: it plays with an established Witcher concept, then adds a new mechanical twist and a fresh visual treatment, while leaving the core timeline and major characters mostly untouched. That balance is key to keeping the franchise flexible without fragmenting its identity.

Balancing Gameplay Needs with Lore Consistency

Even when everyone respects canon, game design sometimes pulls in a different direction than narrative consistency. Designers must occasionally bend lore rules to serve pacing, difficulty, and player clarity.

Typical friction points include:

• Enemy variety – Lore might suggest certain monsters are exceedingly rare, but the game needs enough encounters to stay engaging.
• Character power curves – A hero might start “too competent” according to canon, forcing designers to find narrative excuses for limited abilities early on.
• Loot and progression – Realistic economies and lore-friendly scarcity conflict with the satisfaction of frequent upgrades.

To mitigate such tensions, some studios explicitly distinguish between soft canon gameplay decisions and hard canon story beats. As long as core events and world rules remain intact, they tolerate some fudging in enemy counts or resource availability, especially in spin-off titles that are not meant to carry the central saga forward.

Table: Canon vs. Gameplay – Common Trade-Offs

Why CD Projekt Red Is So Protective of Witcher Lore

CD Projekt Red has repeatedly signaled that The Witcher is not a closed trilogy but a long-term franchise. In its official communications, the company frames the newly announced Witcher saga as the beginning of a new generation of games built in Unreal Engine 5, created in strategic partnership with Epic Games.¹ With that kind of investment, it’s not hard to see why CDPR is careful about how external projects treat canon.

There are also business and reputation reasons for this cautious approach:

• Brand trust – Fans return because they expect a certain mood and quality of storytelling. A canon-breaking spin-off can erode that trust.
• Future flexibility – If spin-offs drastically alter the world, future mainline titles may be boxed into awkward corners.
• Transmedia alignment – Netflix’s Witcher series and other adaptations add additional layers of interpretation; CDPR must keep its own version internally coherent.

This doesn’t mean every single detail must line up across all media, but it does mean CDPR needs a stable foundation. Having multiple layers of approval — from loremasters to producers — is one way the studio tries to achieve that.

How Wild Ideas Still Help Development

Even though zombie witcher hordes never made it past the drawing board, the fact that the idea was proposed is important. Game design thrives on breadth early and focus later. Some benefits of pitching wild concepts include:

• Clearing the creative backlog – Designers and writers get extreme ideas out of their system, then refine what remains.
• Stress-testing the rules – Outlandish proposals help document exactly which parts of the lore are flexible and which are non-negotiable.
• Inspiring scaled-down versions – A rejected idea can be reworked into a smaller, more grounded concept that still feels fresh.

In many studios, the early pre-production phase explicitly encourages this mode of thinking. Nothing is sacred yet, and the job of lorekeepers is not to stifle creativity but to shape it into something that can sit comfortably alongside existing canon.

FAQ: Witcher Spinoffs, Lore, and Canon

What This Tells Us About Franchise Storytelling

The story of the rejected zombie witchers is more than an amusing anecdote. It represents the constant negotiation between innovation and respect for source material that all large franchises face. Every Witcher spinoff must answer the same questions:

• How far can we push the tone before it no longer feels like The Witcher?
• Which rules of the world are flexible, and which are foundational?
• How do we create new experiences without rewriting beloved stories?

For CD Projekt Red and its partners, the answer lies in robust communication, structured review processes, and a willingness to say no — even to ideas that might be exciting in a vacuum. The result, when it works, is a growing universe that still feels cohesive, where each new spinoff adds flavor without breaking the core recipe.