© 2026 The ChroniclerHelpFor AI assistantsPrivacyTermsImpressumWiderrufAGBVerträge hier kündigen / Cancel contracts hereSupport
The Chronicler
HelpOpen the app
Help centre / Getting started

Import your world from Foundry VTT

Export journals, actors, items and scenes out of Foundry as JSON or a ZIP, upload them to Bootstrap campaign, and approve the wiki entries The Chronicler proposes.

On this page

  1. Export from Foundry
  2. Upload to The Chronicler
  3. What gets read
  4. Nothing is added until you approve it
  5. Size limit
  6. What we deliberately do not do

If your campaign already lives in Foundry VTT, you do not have to retype it. Foundry can write any journal entry, actor, item or scene out as a JSON file, and The Chronicler reads those files directly.

We never connect to your Foundry server and we never ask for a Foundry login. You export the files yourself and upload them — that is the whole arrangement.

Export from Foundry

Foundry's export is a right-click away. In your world:

  1. Open the Journal (or Actors, Items, Scenes) sidebar tab.
  2. Right-click a document → Export Data. Foundry saves a .json file such as fvtt-JournalEntry-the-dead-marshes.json.
  3. Repeat for everything you want imported, or install one of the community bulk exporters (Easy Exports, Foundry Bulk Exporter, Adventure Importer/Exporter) and export a whole folder as one .zip. The Chronicler reads the ZIP and the loose JSON files identically.

The filename does not matter. The Chronicler recognises Foundry documents by their shape, so renamed files still import.

Upload to The Chronicler

  1. Go to the campaign Overview.
  2. Open Bootstrap campaign.
  3. Drop the .json files, or the export .zip, into the upload box and press Start bootstrap.

You land on the bootstrap review page while it processes.

What gets read

Foundry documentWhat The Chronicler takes
Journal entryThe entry name, every page name, and each page's text. This is the prose the wiki is built from.
ActorThe name, the Foundry actor type, and the biography or notes field. An actor of type npc becomes an NPC candidate; type character becomes a player character candidate.
ItemThe name and description — an item candidate.
SceneThe name only, as a location candidate. A scene is a map, not prose.

Any other actor type — a vehicle, a group, a hazard, a type specific to your system — is not typed for you. Its text still goes through, and the AI may propose it as an entity of whatever type fits; we would rather read your prose than guess a label.

Biographies are read system-agnostically. A D&D 5e actor's biography, a Pathfinder 2e actor's public notes, and a bespoke system's description field all work; if nothing biography-shaped is there, the actor still imports with its name.

Anything in a ZIP that is not a readable document — images, maps, module code, audio — is skipped. A JSON file that is not a Foundry document is still read as text, so exports from other note tools usually work too.

Nothing is added until you approve it

Everything an import proposes arrives as a candidate on the bootstrap review page. You rename, retype, keep or dismiss each one, and only then does it become a wiki entry. Imported text is AI-owned prose: it is never written as canon, and it can never overwrite a summary you have approved or a name you have locked. See The GM is the authority on canon.

Every entity that comes from an import records where it came from — that it was a Foundry import, which file it was in, and the Foundry document's own id — so a wrong import is findable and removable rather than a mystery six months later.

Size limit

One bootstrap run reads up to 100,000 characters of text in total, and a single file inside a ZIP must be under 5 MB. A long-running Foundry world will be bigger than that, and the run will tell you so rather than importing a third of your world silently. Export in batches — your world book first, then your NPC folder — and run bootstrap once per batch.

What we deliberately do not do

There is no "connect my Foundry account" button, and there never will be: your world is self-hosted and your data is yours, so a file you export is both the safest and the most complete route. For the same reason we do not offer a D&D Beyond or Roll20 account importer — see Import a transcript or notes for the routes those platforms do sanction (a D&D Beyond PDF character sheet, a Roll20 chat archive you saved yourself).

Still stuck?

Email support@thechronicler.app and tell us which campaign and session you were looking at.

More in Getting started 7

What The Chronicler does

Record or upload a game session and get a recap, a growing campaign wiki, quest tracking and prep notes without writing them yourself.

The GM is the authority on canon

AI output is always a suggestion. Anything you lock, approve or confirm is never overwritten by later processing.

Create an account and sign in

Sign in with email and password or with Google, Discord or Twitch, then confirm the recording notice once.

Create a campaign

A campaign is the container for sessions, the wiki, quests and players. Name it, pick a system, and the rest fills in as you play.

Your first session, start to finish

Get a session in, let processing run, name the voices, check the recap and release it to players.

The campaign Overview and Catch up

The campaign's first page — one next action, a Needs-you list, the latest session, and the Catch up list of sessions still to wrap up.

Import your notes — Obsidian, LegendKeeper, World Anvil or a plain folder

Zip your notes folder, drop it into Import Notes & World, and approve the wiki entries The Chronicler proposes. Nested folders are walked and every entry keeps its path.

← Back to the help centre