Lorebooks on a phone
SillyTavern lorebooks on mobile: how World Info works, how to import it, and why entries stay silent
A lorebook (SillyTavern’s World Info) is a JSON file of keyword-triggered entries: when recent messages mention an entry’s keyword, its lore text gets injected into the prompt until your token budget fills up. On Android or iPhone, import the JSON into a SillyTavern-compatible client like Foreverse, bind it to the chat, and test a known keyword. If nothing fires, check binding, keywords, scan depth, budget, and probability in order.
Available for iPhone and iPad in selected regions outside mainland China. Not available on the mainland China App Store. Download help
How do lorebooks actually work?
Think of a lorebook—called World Info in SillyTavern—as a conditional encyclopedia. Every entry pairs trigger keywords with a snippet of worldbuilding. Right before each turn, the app scans the latest chat turns for matching keywords, splices matching snippets into the prompt, and stops once the lorebook’s token cap is full. Because the LLM only receives the entry body (never the title or trigger words), each entry needs to read clearly on its own. SillyTavern’s docs also set expectations straight: injecting lore nudges the model, without guaranteeing the model will use that fact in its reply.
Four knobs govern almost everything. Scan depth sets how many recent messages get searched—1 checks only the latest message, while 0 skips chat history and only evaluates recursive triggers and Author’s Notes. Constant entries bypass keyword checks and claim budget first on every turn. Once the token budget fills up, remaining matches get dropped even if their keywords appeared. Finally, recursion allows one triggered entry’s text to wake up another entry. Foreverse’s worldbook engine supports these World Info mechanics plus V3 decorators (@@activate and @@dont_activate), though defaults aren’t identical: scan depth defaults to 4 on Foreverse for Android versus 2 in desktop SillyTavern.
How do I add a lorebook to a character on my phone?
If a lorebook was embedded inside a character card, importing the card brings it automatically. Standalone .json lorebooks import separately. Menu labels below follow Foreverse’s Android guide. Foreverse’s App Store listing says the app imports character files and our iPhone page lists lorebooks as importable JSON, though we haven’t logged exact iOS screen names yet.
- Save the lorebook as a raw JSON file
Export the World Info JSON from SillyTavern (or grab it from a card site) and transfer it to your phone as an intact file.
- Import via the SillyTavern hub
Go to Me → Essentials → Import from SillyTavern. You’ll see dedicated slots for cards, chat logs, worldbooks, presets, regex scripts, and Quick Replies—tap the worldbook option and select your JSON.
- Check that it arrived
Check Me → Advanced settings → Character Cards & Tavern → Tavern Asset Hub and compare the worldbook count with what you imported.
- Bind the lorebook to your active chat
Inside the chat, open the menu → Current status → World lore and toggle the book on. Unbound lorebooks sit idle in your library—the single most common reason a newly imported book appears broken.
Using SillyTavern’s own mobile web UI instead? Its docs point out that long-pressing Persona Lore or Chat Lore opens the book picker (replacing Shift-click on desktop).
Can I move a SillyTavern lorebook to another app?
Often yes, but never perfectly. Here is what each platform’s own documentation promised when we checked on 2026-11-15.
| App | Import method | What survives (and what gets dropped) |
|---|---|---|
| Foreverse | Import from SillyTavern hub, or bundled inside a card | Runs SillyTavern World Info logic including recursion, scan depth, constants, and token budgets. Android defaults to scan depth 4 (vs. 2 in SillyTavern). |
| Character.AI | Create → Lorebook → Import (plain text or JSON up to 10 MB, or pasted text) | Listed as beta for c.ai+ on its import help page, while its plan chart shows basic Lorebook on free/lite and advanced on c.ai+. Keeps only title, keywords (capped at 8 per entry), and content—stripping regex keys, secondary filters, trigger probabilities, timed effects, order, and insertion position, so entries can fire more often than before. |
| JanitorAI | Paste the entries array into a Lorebook script’s Source Code view | Janitor’s docs specify copying the inner contents of the entries array rather than the outer key. Both user and bot messages trigger entries unless depth is 1. |
| Layla | Import the JSON file as a standard lorebook | Layla’s 14 Sep 2024 post states phrase-based injection works the same way as SillyTavern. |
Want to audit a file before migrating? Drop your JSON into our free browser tool, Lorebook Migration Doctor, to see which fields another app will strip, or read our breakdown of lorebook migration traps.
Why is my lorebook not triggering?
Rule out the free checks before burning API tokens. Start by confirming the book is actually toggled on and bound to this character or chat. Next, inspect your keywords: plain keys split on commas and ignore case by default, while /pattern/ keys run as regular expressions. Make sure that keyword actually appeared inside your current scan depth—a town mentioned ten turns ago is invisible if scan depth is set to 2.
Still missing? Check whether constant entries or oversized lore blocks already chewed through your token budget, whether trigger probability is below 100%, whether sticky/cooldown/delay timers are holding the entry back, or whether a secondary condition like NOT ANY vetoed the match.
Don’t judge by whether the character’s reply sounds knowledgeable—a plausible answer alone proves nothing. In Foreverse, long-press the reply and tap Prompt to open Prompt Inspector, then search for a phrase from the lore entry. To test before you burn messages, paste your JSON and sample chat lines into our browser-based lorebook trigger simulator. Keep in mind the simulator doesn’t model token-budget cutoffs or sticky/cooldown counters, so an entry that passes there can still get trimmed in a live chat. We walk through more cases, including three real support tickets, in why lorebooks fail to trigger.
How do I get lorebooks from JanitorAI?
JanitorAI houses lorebooks inside its Scripts system and documents how to paste SillyTavern entries in. We found no help article showing a standalone Janitor lorebook export button. Your reliable workaround is card import: whenever a lorebook is embedded inside a character card file, importing that card carries the lorebook along regardless of source site. Foreverse can also fetch standalone lorebooks by link from Chub; for other repositories, download the JSON file first and import locally (see our URL import notes).
Check the content rules of any site you download from, and only import lorebooks you have permission to use.
When a mobile lorebook is the wrong fix
- The entry is already in Prompt Inspector, yet the model ignores it. World Info can’t force obedience—trim the entry into blunt, front-loaded facts or switch models.
- You want semantic recall without exact keywords. Keyword matching is literal; meaning-based retrieval needs embeddings (SillyTavern’s Vector Storage extension or an embedding model configured in Foreverse), so test carefully before counting on it.
- You expect Character.AI to honor complex SillyTavern triggers. Character.AI drops regex keys, secondary logic, and probabilities on import.
- You mark every single entry Constant. Constants eat context on every turn and crowd out recent dialogue.
FAQ
How do lorebooks work?
Every entry pairs trigger keywords with lore text. Before each turn, the app scans recent chat messages for those keywords and injects matching lore into the prompt up to your token budget. The model only sees the lore text, never the keywords.
Why is my lorebook not triggering?
Walk down this list in order: confirm the book is bound to the active chat, verify a keyword sits inside your scan depth, check that the token budget isn’t already spent, and inspect probability, timed effects, and secondary filters. Confirm injection inside Prompt Inspector rather than guessing from the reply.
How do I add a lorebook on my phone?
Save the lorebook JSON to your phone and load it into a SillyTavern-compatible app. On Foreverse for Android, go to Me → Essentials → Import from SillyTavern → worldbooks, then bind the book inside your chat under Current status → World lore.
Can I import a SillyTavern lorebook into Character.AI?
Partially. Character.AI’s help docs describe lorebook import (beta for c.ai+, plain text or JSON up to 10 MB), keeping only titles, up to 8 keywords per entry, and body text while stripping regex keys, secondary filters, and probabilities.
Does Foreverse support SillyTavern lorebooks?
Yes. Foreverse runs SillyTavern World Info rules—recursion, scan depth, constant entries, token budgets, and V3 @@activate / @@dont_activate decorators. Watch out for default differences (Android defaults to scan depth 4 vs. SillyTavern’s 2), and note that third-party desktop extensions don’t install directly.
Sources
- SillyTavern docs: World Info (checked 2026-11-15)
- Character.AI help: Importing Lorebooks (checked 2026-11-15)
- Character.AI help: C.ai lite compare plans (lorebook tiers) (checked 2026-11-15)
- JanitorAI help: What are Scripts? (checked 2026-11-15)
- Layla: Layla supports SillyTavern Lorebooks (14 Sep 2024) (checked 2026-11-15)
- App Store: Foreverse - AI Story Studio (checked 2026-11-15)