Source: Perchance AI RPG. Collection date: October 19, 2026, Asia/Shanghai. We created a disposable fictional adventure, entered distinct overview, story and notebook markers, then inspected the current-adventure save completed by the user. No AI-generated continuation or bulk export was needed.
Dated file inspection
| Field | Actual file observation | What remains untested |
|---|---|---|
| format | perchance-ai-rpg-v1 | Compatibility with other versions |
| storySoFar / storyOverview | Both exact synthetic markers retained | Imported editable state |
| notebook.tabs[].content | Separate test note retained | Narrator access to notes |
| responseStyle | Specific instruction string stored | Behavior after loading |
| themeSettingsByScheme | Light/dark objects with empty values and flags | Rendered restoration |
| keptImages | Empty list in this image-free fixture | Embedded versus linked image handling |
All file observations above were collected 2026-10-19 from the same Perchance source page and the resulting local save. Empty values are not failed-feature results.
Three seeded fields survived as separate data
The saved file placed our gate scene in storySoFar and our courier brief in storyOverview. Each contained its own dated marker and the text we had entered, rather than merging the overview into the narration. The notebook was separate again: notebook.tabs contained a page titled Page One with the private test-note marker inside its content value. That marker had been typed through the adventure notebook, not added to the story. The file therefore preserved a piece of player reference material that a plain story transcript would miss. The note’s presence in an export does not show that the narrator reads it. Our source fixture used only Ilya, a closed gate, a silver token and a red pouch; no unrelated adventure text appeared in this inspected object.
A snapshot of settings, including empty values
The responseStyle value contained a one-paragraph instruction excluding new player actions and foreshadowing. We had left the visible writing selector at Normal, so the saved string was more specific than the label shown in the interface. The file also included themeSettingsByScheme with separate light and dark objects. Their text-color, background-color and font-family values were empty, while italic and quote presentation flags had Boolean values. Several other fields existed without configured content: backgroundVisual and backgroundMusic were empty strings, shortcutButtons was an empty list, and keptImages was an empty list. These are observations of this unillustrated test adventure, not evidence that custom backgrounds, shortcuts or saved images cannot be exported. A present but empty field needs a different interpretation from a missing field.
File identity is distinct from successful restoration
The top-level format identifier was perchance-ai-rpg-v1 and the title was Untitled adventure. The delivered filename ended in .ai-rpg.json, and a standard JSON parser opened it without decompression. Notebook pages also carried a page identifier, a last-edit timestamp and an active-page reference. We retained the original bytes privately and removed those generated identifiers from the public excerpt because they add nothing to the field check. This object described the current adventure; we did not invoke the adventures-panel bulk export or inspect the user’s other stories. The earlier automated download listener had returned no file, but the user then completed saving and the local file supplied the evidence. We did not load it back, overwrite an adventure or test another device, so restoration and cross-device compatibility remain unmeasured.
Repeat the marker check
Start a disposable adventure. Put different harmless markers in the overview, story and adventure notebook. Use the current-adventure save control below the writing, background and music controls. Open the downloaded file as data, search for each marker and record the enclosing key. Do not assume an adventures-panel export has the same scope. Our redacted synthetic excerpt and field checklist CSV show what we inspected; the excerpt is not offered as an import-ready native backup.
Can I move a campaign to another tool?
This test does not establish that. JSON syntax and readable prose do not guarantee a compatible importer. Yesterday’s text save-sheet pilot checked an explicitly supplied ledger; today we inspected native file contents. Neither test certifies a full cross-tool migration.
What the reference pages cover
AI Dungeon’s settings guide describes a Download Adventure text backup, while FableAI’s memory guide discusses separate narrative memory layers. We did not export either service in this experiment. Perchance’s visible help describes browser-local adventure storage. Our original addition is this dated marker-to-file check, absent from those inspected references—not a claim that other products lack backups.