A retcon is the moment canon management stops being about preventing change and starts being about controlling it. Sometimes you need to alter something you've already established — reveal that an event wasn't what it seemed, revise a rule that's boxing you in, recontextualize a character's past. That's a legitimate and often brilliant move. The danger is that changing established canon is exactly the operation most likely to break a world, because established facts have dependents, and altering one without following its consequences leaves contradictions scattered behind it.
So the question isn't whether to ever change canon — long stories, and especially long franchises and series, sometimes must. The question is how to change it deliberately and completely, so the result reads as a designed revelation rather than an author losing track. This guide is about that: what separates a retcon from a plot hole, and how to make a change to your world without the change quietly breaking a dozen things you've forgotten.
A retcon is a decision; a plot hole is an accident
The same altered fact can be either the best moment in your story or its most damaging error, and the only difference is intention and control. A retcon is you deciding to change canon and then owning that change everywhere it reaches. A plot hole is canon breaking because you forgot what you'd established. From the outside they can look identical — both are a contradiction with earlier material — which is why readers judge them entirely on whether the change feels authored or accidental. Your job is to make sure yours is unmistakably the former.
What signals 'authored' is that the change respects the reader's investment in what came before. The best retcons recontextualize rather than erase: the earlier events still happened and still mattered, but now mean something different, and often something richer. The reader gets to re-read the past in a new light, which is a gift. A retcon that simply declares the old material void spends the reader's trust instead of rewarding it, and that's the version that reads as a plot hole with a press release. The line between the two is respect for the canon you're changing.
Map the blast radius before you change anything
The technical heart of a clean retcon is knowing exactly what the fact you're changing currently touches. Every piece of established canon has dependents — scenes that rely on it, characters shaped by it, other facts that only make sense because of it — and a change ripples out to all of them. Change a character's history and every scene built on that history may now need to shift. The retcons that break worlds are the ones made without seeing this dependency web, so the change lands cleanly in one place and silently contradicts five others.
This is precisely where a single source of truth earns its keep, because it lets you see what a fact connects to before you alter it. When your canon is a web of related, findable pieces rather than a memory, you can trace the full reach of a change, update every dependent, and know you've caught them all. When it's not, you're changing one thread of a tangle you can't see and hoping nothing else was attached. The ability to see and check those connections is the difference between a retcon you control and one that controls you — the same argument canon management makes about deliberate change.
After the change, the discipline is to update the record itself, immediately and completely. A retcon isn't done when you've written the reveal; it's done when the source of truth reflects the new canon and every contradicting fact has been revised or removed. Leave the old canon standing in your bible and you've created the worst kind of continuity trap — a reference that now disagrees with your own story. Fold the change all the way through, and the retcon becomes solid ground you can keep building on.
The longer the story, the higher the stakes
Retcons get both more tempting and more dangerous as a story grows. A long series accumulates canon you may want to revise years later, and it accumulates readers who know that canon intimately and will notice instantly if you break it. The same change that would pass unremarked in a standalone can detonate across a beloved franchise, because more has been built on top of the fact you're moving. Longevity raises the reward of a good retcon and the cost of a careless one.
The protection is the same discipline scaled up: a canon you can actually track across the whole series, so that when you revise something in book five you can see everything it established across books one through four. We cover keeping that continuity intact over a long, multi-installment work in tracking canon across a series, and the specific error patterns a botched retcon creates in common continuity errors. Handle canon this way and change stops being a threat to your world — it becomes one more thing you can do to it on purpose.
Frequently asked questions
- What is a retcon?
- A retcon — short for retroactive continuity — is a deliberate change to something already established as canon, so that the past of the story now works differently than it originally did. A reveal that a character's death was faked, a new backstory that recontextualizes earlier events, a rule of the world quietly revised in a later installment: all retcons. The key word is deliberate. A retcon is a choice to alter the record, which is what separates it from a continuity error, where the record breaks without anyone intending it.
- Are retcons always bad?
- No — a well-executed retcon is one of the more powerful tools in long-form storytelling, and readers often love the ones that work. The difference is whether the change respects what came before or ignores it. A good retcon recontextualizes earlier events so they still make sense, or even make more sense, in light of the new information; a bad one simply contradicts them and hopes no one notices. The craft is in changing canon in a way that pays off the old material rather than invalidating it.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free