Two scenes identical in their facts can read differently: one as "in canon," the other as "fanon." The difference isn't in what happens but in where the rule it happens by comes from. Confusing these two sources is behind half the arguments in the comments.
I'll work the line on concrete examples and show when leaning on fanon is safe and when it burns you.
Canon is the source: what's directly in the original work. The book, the series, the game, the manga. If the text says Sherlock Holmes plays the violin and keeps his tobacco in a Persian slipper, that's canon, because Conan Doyle wrote it.
Canon has a clear property: it can be checked. You take the source, find the scene, quote it. The argument ends.
Fanon is the community's conventions that aren't in canon but "everyone writes that way." It's born from gaps: where the source is silent, the fandom fills the void with a shared decision, and over the years it becomes nearly mandatory.
A classic example is the BBC series Sherlock. In it Mycroft worries about his weight, and the fandom turned that into the steady fanon of "Mycroft on a diet," though in canon it's a line or two. Or the matter of Sherlock's scarf: the way he ties it became almost a recognizable sign of the character among ficwriters, though plot-wise it's nothing.
In The Lord of the Rings it's the same on different material. Tolkien's canon says almost nothing about the daily life and characters of hobbits beyond the main ones; the fandom built Sam up as a practical cook, and gave the LegolasβGimli line the shape of a firm friendship "after an initial enmity." That part is in the book, but fanon expanded it into a whole genre of scenes.
The mechanism is always the same, in three steps:
The key condition: good fanon doesn't contradict canon, it fills its silence. Bad fanon quietly rewrites what canon states outright, and that's where the problems start.
Sometimes fanon even gets fixed officially. On BBC's Sherlock the writers consciously picked up fandom theories and wrote them into later episodes, so the line between canon and fanon shifted there in real time more than once. It's a rare case, but it shows the main thing: canon isn't always a frozen quantity, and what's "just fanon" today can become source text tomorrow.
A working rule for the line:
For a deeper look at a fandom where this line is especially visible, see the guide on Harry Potter, where plenty of "everyone knows" is in fact fanon.
OOC (out of character) is when a character acts against their own canon-set personality. It's a variety of the same problem: you crossed the canon line, only in behavior rather than in facts. An Aragorn who abandons his companions for gain is OOC, because canon built him on the opposite.
An important nuance: OOC isn't always a mistake. If you're writing an AU where circumstances differ, the character has the right to behave differently, provided the change is visible and motivated. The mistake is unintentional OOC, when you think you're writing the canon character and a different person under their name comes out.
The same source distinction helps here too. Often the "canon character" a writer is afraid to depart from is a simplified fanon version: Legolas in the book is more reserved and older than his fandom image of a young, cheerful archer. If you don't confuse where a trait is canon and where it's a collective simplification, it's easier both to hold the character and to break them deliberately β because you know exactly what you're departing from.
No, if it's on purpose and visible to the reader. Deliberate OOC is a tool: "what if Boromir hadn't yielded to the Ring," "what would Sherlock be like if raised differently." Here the change of character is the point of the text. It goes wrong when the OOC is unintentional: you announce a canon character and write someone else, and the reader feels a rift you didn't intend. So the problem isn't OOC as such, it's the mismatch between the promise and the text.
By a source check. Ask: "Can I point to a specific scene, line, or sentence where this is stated?" If yes, it's canon. If the answer that comes back is "well, it's obvious" or "everyone writes it that way," it's fanon, however widespread. It helps to reread the source now and then without the fandom layer: a great deal of "canon," on inspection, turns out to be a collective agreement. That doesn't make it bad. You need to know what you're dealing with.
Once the line is visible and the first scene won't come, hand the description of the world and situation to the generator. It removes the blank-page fear and returns a draft where you then place canon and your interpretation yourself. Neighboring fandom breakdowns are in the The Lord of the Rings and Sherlock hubs.
Posts are written by Fanficia's AI editorial team with our author personas.
Describe the idea β the AI drafts a chapter and you stay the editor.
Open the generator βA systematized glossary of fandom slang: work status terms (WIP, OS), character terminology (OTP, ship, OC), genre abbreviations, and platform vocabulary.
Core fanfiction genres β romance, angst, fluff, hurt-comfort, crack, gen β how to read tags, how genres combine with ratings, and how many to use in one work.
What OOC means in fanfiction, the difference between intentional and accidental out of character, and four concrete checks to keep your characters true to canon.
Andrii ran tabletop campaigns for about ten years; now he tests software and takes other people's universes apart bolt by bolt. He likes it when canon holds together: timelines, magic rules, who's related to whom. He writes fandom guides and explains how to keep worldbuilding consistent even when you're writing past where the authors stopped.