Import World Books and Lorebooks into Tavern Studio

World books are worth importing carefully because they affect prompt behavior, not just organization. Tavern Studio can import SillyTavern-style World Info/lorebook assets and store them as structured local World Info records.

After import, the important step is verification: make sure entries are enabled, keys are sensible, and the world book is attached to the character or chat that needs it.

Who This Is For

  • SillyTavern users migrating World Info.
  • Writers with reusable setting documents.
  • Users whose character cards include embedded lorebooks.
  • People debugging why a lore entry does or does not enter context.

Core Content

World Info import needs to preserve entry content and trigger behavior. Keys, secondary keys, disabled state, insertion order, depth, sticky, delay, and cooldown settings can change how the model sees the world.

Do not judge success only by whether a file appears in the list. Test a real trigger in chat.

How Tavern Studio Handles It

Tavern Studio can import world books directly or through the full SillyTavern migration path. When a character card contains a characterBook/lorebook, Tavern Studio can create a World Info record and link it to that character.

For full migration, use Settings -> Data Management -> Import from SillyTavern, select the project root that contains the data folder, preview what was found, and import without modifying the original SillyTavern files.

Operation Steps

  1. Export or locate your SillyTavern World Info/lorebook JSON.
  2. Import it through Tavern Studio's import flow, or run the full SillyTavern importer.
  3. Open the World Info section.
  4. Check entry count, names, keys, and disabled states.
  5. Attach the world book to the relevant character or chat.
  6. Send a test message containing a trigger key.
  7. If the entry does not trigger, review key spelling, case sensitivity, whole-word settings, and extra matching sources.

FAQ

Can Tavern Studio import SillyTavern World Info?

Yes. World Info/lorebook import is part of Tavern Studio's SillyTavern-compatible asset workflow.

Do disabled entries stay disabled?

Imported state should be reviewed. If an entry is not appearing in context, check whether it is disabled or not selected for the chat.

Why does an entry not trigger?

Common causes include key mismatch, case sensitivity, whole-word matching, missing secondary keys, negative keys, or disabled entries.

Should I put lore in the card instead?

Only if it is essential identity or opening context. Conditional lore belongs in World Info.

Does import change my SillyTavern files?

The full migration importer is designed as a read-only import from the source project folder.

Next Step