SillyTavern Lorebook vs Character Card: what is different?

If you are new to SillyTavern, these two terms are easy to mix up:

• Character card: the character itself (identity, voice, behavior, starter content).
• Lorebook: background knowledge that can be injected when relevant.

Short version: a character card defines who is speaking; a lorebook provides what world facts can appear.

The simple mental model

Think of roleplay as a stage:

• The character card is the actor profile.
• The lorebook is the world reference binder.

You can run a character with little or no lorebook.
You can also reuse one lorebook across many characters in the same setting.

What usually belongs in a character card

A card should contain things that stay true for that character in most chats:

• Name, style, personality, tone, boundaries.
• Core motivations and stable backstory.
• Typical speech patterns and interaction style.
• Opening message and scenario framing.

In many workflows, this lives in card JSON fields like description, personality, scenario, first_mes, and examples.

What usually belongs in a lorebook

A lorebook should contain information that is world-oriented, optional, or situational:

• Places, organizations, timelines, factions.
• Item rules, magic systems, technology constraints.
• Side characters and relationship facts.
• Detailed setting history you do not want in every prompt.

Lorebook entries are commonly keyword-triggered, so they can be included only when needed.

Why they are separate (and why it matters)

Keeping them separate gives you practical benefits:

1. Token efficiency: not every world detail is loaded every turn.
2. Reuse: same worldbook can support multiple cards.
3. Maintenance: change world rules once, not in every character.
4. Consistency: easier to avoid contradictory setting details.

For beginners, this structure also reduces chaos when you debug bad outputs.

Where confusion usually happens

Mistake 1: putting everything into the card

If your card becomes huge and includes all world lore, you may get:

• Higher token pressure.
• Less stable behavior over long chats.
• Harder edits when setting details change.

Mistake 2: putting core personality into lorebook

If key character identity is only in lore entries, behavior can feel inconsistent because those entries may not always trigger.

Mistake 3: unclear keywords

If lorebook keys are too broad (or too narrow), entries may fire too often (or never), causing noisy or missing context.

A practical split for beginners

Use this starter rule:

• Put always-true character identity in the card.
• Put world facts and situational references in lorebook.

If you are unsure where a sentence belongs, ask:

“Should this appear in almost every reply from this character?”

• If yes, card.
• If no, lorebook.

Example (quick comparison)

Character card line:
“Mina is calm, precise, and avoids slang. She mentors the user in old map restoration.”

Lorebook entry:
“Guild Archive: damaged maps are tagged with three wax colors; red tags require two-person verification.”

The first defines Mina’s behavior.
The second defines world procedure that appears only in relevant scenes.

How this relates to SillyTavern and PNG cards

Many SillyTavern-compatible cards are PNG files with embedded JSON metadata.
A card can also include an embedded character book (character_book) depending on tooling and format version.

Even when both exist in one file, the concept split is still useful:

• Card fields for identity and baseline behavior.
• Book/lore entries for triggered world knowledge.

Final checklist before you ship a card

• Character voice is clear in the card without extra lore.
• World details are modular and not duplicated everywhere.
• Lorebook keys are specific and tested in chat.
• Long or niche setting text is not forced into every turn.

---

Edit SillyTavern-compatible PNG card metadata locally on Mac with Sillycard.