A visual novel gives you a still illustration, a line of text beneath it, and a button that advances it. Every so often the text stops and offers two or three options, and the one you take decides which scenes you get next. What separates a strong one from a slack one is not that it branches — it is the shape of the branching, and there are about four in circulation.
Read, choose, replay.
Reading is most of it: you advance text at your own pace while backgrounds change and a track carries the mood, and a scene can run for an hour with no input beyond the advance key. A work with no choices at all has its own name — a kinetic novel, the label Key used for Planetarian — and it is a legitimate thing to build, provided you know that is what you are building.
Choosing happens at forks, usually two or three options a line long. Replaying is not optional the way it is elsewhere: nearly every engine ships a skip function that fast-forwards text you have already read, so a second route costs a fraction of the first. Finishing a visual novel is normal. Finishing all of it is the completion state.
Some add a verb. Ace Attorney — the series in which Phoenix Wright is the defence lawyer, not a separate franchise — alternates investigation with cross-examination, where you press a witness and present the exhibit that breaks a lie. Dating sims run affection numbers behind the choices, so your route is a consequence of who you spent time with; cozy farming sims run the same meters under a different genre.
The form grew up in Japan, and the untranslated catalogue is still where most of it lives; these are the shapes it standardised.
| Shape | How it works | What it costs you |
|---|---|---|
| The gauntlet | One correct path; a wrong choice hits a bad end and stops. | The forks become a quiz with a load button behind them. |
| The hub | A shared common route forks into one route per character. | You re-read the trunk every run — skip-read exists because of this. |
| The flag | A choice in the first hour sets a value you never see; it decides a scene in the ninth. | Nobody reaches the good ending blind; set flags cruelly and you have written a walkthrough dependency. |
| The true route | Locked until you finish the others, then reframes them. | The earlier routes become homework; the payoff has to be worth the tax. |
Real works mix them. Fate/stay night gates its three routes in sequence, so the order is part of the structure. Steins;Gate hangs its endings on which text messages you answer, which is the flag shape at its most deniable. The Zero Escape games ship a flowchart of every branch you have seen and let you jump straight back to a fork — an admission that the flag shape is hostile without one, and the most humane interface the genre has produced.
Skip-read makes the second run cheap; recontextualisation is what you spend it on. The move the form is best at is the playthrough that reveals the last one was incomplete — the same scene, read again knowing what the other character was doing that evening, meaning something else.
Be honest about how special that is. Film does it too, and so does any novel with a twist. What no other medium can do is make you the reason you missed it: nobody withheld the other evening, you took the route that hid it, and the game kept the record. A second run feels less like re-watching than like being shown your own blind spot.
The failure sits right beside the trick. Plenty branch generously for an hour, then funnel every path into one corridor, so the choices amount to picking which scenery you pass. The opposite is worse: routes that genuinely diverge, where the real ending demands hours of replayed text in the right order, with flags nobody mentioned.
Ren'Py, and it has been the answer since 2004 — Tom Rothamel's free,
open-source engine, where a script is dialogue lines and menu: blocks and the
genre's conventions arrive already implemented: save anywhere, rollback, a skip
that knows which lines you have seen, a text-history log, and both layouts the
form uses (ADV, the box across the bottom of the art; NVL, the full page of
prose). Doki Doki Literature Club is a Ren'Py game — a bright dating sim that
turns its own save files and interface into the material of its horror — and so
is a large share of everything independent in the form. Building those parts
yourself is a month you could have spent writing.
Which is the catch. The engine is free and the writing is the entire product: a mediocre visual novel is worse than a mediocre game of any other kind, because no movement and no mechanical texture will carry a weak chapter. Interactive fiction shares that exposure and drops the portraits as well.
Type: Visual novel (branching; a kinetic novel is the same form with no choices)
Core loop: Read a scene, reach a fork, take a branch, live with what it hid
Perspective: 2D character art over backgrounds; ADV text box or NVL full page
Win / lose: Which ending, not pass/fail — unless you write bad ends that stop the run
Session: A chapter at a sitting; skip-read makes every route after the first shorter
Progression: Flags, routes and endings — no power curve; seeing all of them is completion
Choose the shape before the first scene. A hub written as a gauntlet reads as a story punishing you for wrong answers it never signposted; a gauntlet written as a hub reads as a story where nothing you decide matters. Readers work out which one they are holding within an hour.