Engine
iepub treats interactive narrative as a readable work with rules, state, assets, and chapters that can travel together. It is not just a branching graph editor. It is a lightweight runtime model designed so authors can write, export, and read the same work without inventing a custom delivery stack each time.
Why it matters
Many interactive fiction tools are excellent at quick experimentation, but the runtime, data model, and published artifact often remain tightly coupled to one editor. iepub leans in the opposite direction. The book remains a structured publication with explicit manifest, story files, assets, and optional tools such as the character sheet used by Decadence.
Chapters, variants, rules, and assets stay inspectable. That makes export, validation, and debugging much more practical when a project grows past a quick prototype.
The engine is judged by the reading experience: clear chapter progression, portable assets, and predictable state across sessions.
Go deeper
See how narrative content, runtime behavior, and publication assets stay separated.
Authoring Write in VariantInspect the official authoring environment for scenes, choices, and export.
Reader Open the libraryBrowse published works and load a book into the web reader.
Platform See the full platform viewUnderstand how format, reader, writer, and example work fit together.