Browser Visual Novels and Interactive Fiction: Games Without a Graphics Engine
No physics, no collision detection, no frame rate to worry about. The entire game is a tree of text and choices, and that simplicity is exactly why the format has quietly thrived in browsers for two decades.
Strip away the genre label and a browser visual novel or interactive fiction game is close to the simplest thing you can build and still call a game: a block of text, a small number of buttons representing choices, and a rule for which block of text comes next depending on which button you pressed. There's no render loop chasing sixty frames a second, no physics step, often not even a single sprite that needs to be redrawn on every tick. That simplicity is precisely what makes the format so well suited to a browser tab.
The Underlying Structure: A Directed Graph, Not a Line
The naive mental model of a choice-driven story is a tree — every choice splits into new branches, and those branches never reconnect. In practice, almost no interactive fiction of any real length is built as a pure tree, because a tree's branch count explodes exponentially with each decision point. A story with ten sequential binary choices, built as a strict tree, needs 1,023 unique passages. Writers instead build a directed graph where branches merge back together: three different early choices might all funnel into the same middle scene, with only the character's internal reaction to that scene varying based on which path got them there. This is the difference between a game that feels like it's tracking your choices meaningfully and one that's quietly re-merging you onto the same rails within a few screens, and readers can usually tell which one they're playing even without seeing the underlying graph.
State, Not Just Position
A well-built interactive fiction game tracks more than "which passage am I on." It tracks variables — a relationship score with a character, an inventory flag, a fact the player has or hasn't learned — and passages check those variables to alter their text even when the player has arrived at the same nominal location through different routes. This is what separates a genuinely reactive story from a "choose your path" structure that resets context at every branch point. Tools built for the format, most notably Ren'Py's official documentation, expose this directly as a scripting layer where variables persist across the whole playthrough and conditional logic gates what text or choices appear, letting writers build stories that remember a choice from twenty screens back without hand-wiring every possible combination.
Why the Web Is a Natural Home for This Format
A visual novel's asset budget is tiny compared to almost any other game genre — a handful of character portraits, a background image or two per scene, and text, which is the cheapest asset type that exists on the web by a wide margin. That means a full-length interactive fiction game can load near-instantly even on a slow connection, matching the low-friction expectation browser gaming has trained players to expect. It also means the entire genre translates cleanly to mobile browsers without the compromises that a physics-heavy or twitch-reflex game has to make to work on a touchscreen; tapping a choice button works identically whether you're on a laptop trackpad or a phone screen.
Save States Are Simpler, and That's a Feature
Because the entire game state is a small set of variables and a current passage identifier, saving progress in a browser interactive fiction game is close to trivial compared to saving progress in a physics-driven or procedurally generated game. The whole state fits easily in a small local storage entry, which is part of why these games can support features rarer elsewhere in browser gaming, like multiple named save slots or a full choice history log letting a player see every decision they made in a run without needing anything more elaborate than reading back a small stored object.
The Craft Problem Underneath the Simple Tech
The technical floor for building a browser interactive fiction game is genuinely low, which means the format's biggest challenge isn't engineering, it's writing craft: making choices feel consequential without the combinatorial explosion of branches becoming unmanageable for one writer or small team to maintain. The strongest examples in the genre tend to use a small number of major branch points with real long-term consequences, surrounded by many smaller choices that affect tone, characterization, and small callbacks rather than the plot's overall shape. That balance — a few choices that matter enormously, many that matter just enough to make the story feel responsive — is closer to a writing problem than a technical one, and it's a large part of why the format has stayed a haven for solo writers and small teams even as other browser game genres have pushed toward larger production budgets.