Offline Interactive Fiction and Where Prose Lives

Offline interactive fiction works for one reason: every sentence is already in the file before you open it. A story compiled for the Z-machine carries all of its prose with it, so the interpreter on your phone is the whole machine. A narrator that writes each scene as you reach it has nothing to carry, and that is why it needs a connection.

• A story file holds its entire text, so an interpreter can run it with the network switched off.
• Parchment, the interactive fiction player for the web, ships as a single file you can download and use offline.
• Windows Frotz plays Z-code, the format Infocom used, along with several hundred later games written in it.
• Live AI narration cannot be downloaded in advance, because the next scene is not written until you ask for it.
• Reading a finished story back is a different job from generating it, and should not need the same connection.

What makes offline interactive fiction possible?

Compilation does. When a writer finishes a parser game, the output is a story file: a small program that holds every room description, every refusal and every ending the story will ever show. An interpreter executes it the way a console runs a cartridge. Put the file and the interpreter on one device and the work is complete on that device.

Two virtual machines carry most of the catalogue. Windows Frotz describes itself as “an interpreter that can play all the old Infocom text adventures”, and names the format plainly: “Z-code, or the Z-Machine, with the Z coming from Zork, Infocom’s first game”. Its README counts “several hundred games in this format that can be played with this interpreter”. The later machine is Glulx, built for larger stories.

Glulx shows the shape of the arrangement better than any description. The reference interpreter, Glulxe, is run as glulxe filename.ulx — one program, one file, no third party. If both are on your disk, so is the story. The words interpreter, story file and parser all get used loosely in this corner of the hobby; our interactive fiction glossary gives each one a single example.

The formats you will meet

Format	Where the prose sits	What reads it with no signal
Z-code, from Infocom onward	Compiled into the story file	A Z-machine interpreter such as Frotz
Glulx (.ulx)	Compiled into the story file	Glulxe, the reference interpreter
Adrift 4, Hugo, TADS 2/3	Compiled into the story file	Parchment’s single downloadable file
A live AI narrator	Nowhere yet, by construction	Nothing; the scene is made on request

Which players work with the network switched off?

Nearly all of them, and one of them is a web page. Parchment, which calls itself “the Interactive Fiction player for the web”, says in the same README that it “is also available as a single file, suitable for downloading and using offline”. Its single-file build covers Adrift 4, Glulx, Hugo, TADS 2/3 and Z-code — five formats in one document on your disk.

That is a useful test to apply to anything calling itself an offline reader. Does it hold the story, or does it hold a link to the story? A downloaded page that still calls home for its text has only moved the dependency. Parchment’s version passes because the formats it plays were designed to be self-contained in the first place.

Inform 7, the authoring system behind much of the modern catalogue, bundles Parchment so writers can “produce personal websites for your stories”. The result is a page that plays, not a page that streams. A story published that way is as portable as the file it came from, which is the whole mechanism behind offline interactive fiction: self-containment was a design goal here long before anyone worried about airplane mode.

What does a pre-written story give up?

Everything that depends on knowing what you did. A compiled story can branch, remember flags, and refuse an action with real wit, but each of those responses was written in advance by a person who had to imagine you. Walk outside the lines and the story has nothing to say, because nothing was written for the move you made.

That limit is the reason the genre invented its own crafts: the careful refusal, the response that covers a hundred phrasings, the puzzle that funnels you back. They are good crafts. They are also a budget. Every sentence costs a person an hour, so the story is as wide as its author’s patience, and not one scene wider.

The saves tell the same story from the other end. A story file remembers your run perfectly, because remembering means setting a flag the author declared and a response the author wrote. It cannot be surprised. Ask a parser game about a promise you improvised to a character who was never given dialogue for it, and the silence you get is not a bug; there was nothing there to find.

Why can’t a live AI narrator read offline?

Because the sentence you are about to read has not been written yet. Fabledrift, an interactive fiction app for Android, generates every scene when you reach it, from your move and the story’s structured memory, and the model that writes it is far too large to sit on a handset. There is nothing to download in advance. That is the honest trade for a story that can answer a move nobody anticipated.

We do not pretend this is costless. A file in your pocket keeps working in a tunnel; a narrator does not. The reasonable thing is to be exact about which parts of an app actually need the connection, rather than letting the whole library go dark when a train goes underground.

What should still work when the signal drops?

Anything that only reads. Generating a scene needs the connection; showing you a scene you already read does not, and neither does a record of what the story remembers. The two jobs get bundled together in most apps out of convenience, not necessity, and the bundling is what makes a dead connection feel like a dead library.

The sturdiest answer is to keep a copy in a format that has no runtime at all. Exporting a story as plain text produces a file that opens anywhere, the way a downloaded book does, with no interpreter and no server in the path. It is also the only form in which a story generated once is guaranteed to outlive the app that made it, which matters more than it sounds when re-reading a story that exists only once.

Packing for a flight with no signal

Decide before you leave what kind of reading you want. For a long flight, the back catalogue is unbeatable: download three story files and one interpreter, and nothing you do for the next nine hours depends on the aircraft’s wifi. The prose is fixed, and after forty years of authors working inside that constraint, a great deal of it is very good.

For a commute with gaps, keep both. Read live where there is signal, and carry a story file and a text export for the tunnels. The split is not a compromise between two products; it is two different things to do with a story, and only one of them has ever needed a connection.

So the question to ask of any reader on your phone is not whether it supports offline interactive fiction, but where it keeps the prose. If the answer is a file on your disk, the tunnel changes nothing. If the answer is a sentence not yet written, no setting will change that, and an app that implies otherwise is selling you a download that cannot exist.