Creator guide · Card specs v1–v3
How to make a character card for SillyTavern
To make a character card for SillyTavern, write concrete facts in description, a scene-in-progress opener in first_mes, and two or three voice samples in mes_example, then export as a PNG with an embedded tEXt chunk, JSON, or V3 .charx. You can build cards in desktop SillyTavern, in our free browser Card Studio, or offline on Android inside Foreverse, our mobile roleplay, companion, and AI novel app.
Available for iPhone and iPad in selected regions outside mainland China. Not available on the mainland China App Store. Download help
Which fields actually matter when you write a character card?
Technically, name is the only required field in SillyTavern's character design documentation. In real chats, four fields carry almost the entire character: description, first_mes, mes_example, and scenario. Know the billing difference before you start typing: every token inside description, personality, and scenario is permanent and gets resent on every single turn, while mes_example drops out once live conversation history fills the context window.
First-time card authors tend to stuff personality with vague adjectives. “Gentle, intelligent, mysterious, loyal” gives a language model nothing concrete to play, so five different characters end up sounding like the same polite chatbot. Observable habits and stakes work much better: where this person is standing at 2 a.m., what they clock about {{user}} first, what they want in the next ten minutes, and what they will lie to hide. Keep permanent fields tight. SillyTavern's docs note that a 1,000-token definition eats half the memory of a 2,048-token model, and the editor turns its token counter red whenever your card crosses half of the active context window. Modern cloud models give you far more room, yet bloated permanent text is still sent and billed on every turn.
Treat first_mes as your style blueprint. Whatever perspective, formatting, and paragraph length you use in the opening message, the model will copy on turn two. Close that opener mid-scene—a question hanging in the air, keys dropped on a counter, a door held half open—so the player has an obvious hook to answer instead of inventing the premise alone. Then add two or three mes_example exchanges (each marked with <START> in Tavern syntax) where {{user}} and {{char}} stay strictly on their own sides. If your sample dialogue shows {{char}} narrating how {{user}} feels or reacts, the model will hijack the player's actions all session long; run your draft through our Impersonation Checker to catch those lines before export.
How do V1, V2, and V3 character cards differ?
Under the hood, a SillyTavern card is a community-standard JSON object saved raw, embedded inside a PNG's metadata, or zipped alongside extra media. Picking V2 versus V3 determines which frontends can read your lorebooks, expression sprites, and decorators. We checked both GitHub specifications against our mobile import spec.
| Generation | Spec marker & container | Key fields added | Where it breaks |
|---|---|---|---|
| V1 (TavernAI era) | No spec header; flat JSON or PNG tEXt chunk named chara | name, description, personality, scenario, first_mes, mes_example | No alternate greetings, no embedded lorebook, no creator notes |
| V2 (May 2023) | spec: "chara_card_v2" (2.0); JSON or PNG tEXt chunk named chara (UTF-8 → Base64) | alternate_greetings, character_book (lorebook), system_prompt, post_history_instructions, creator_notes, tags, extensions | Single avatar image only; forwarding a PNG through chat apps often strips the chara chunk |
| V3 (CCv3) | spec: "chara_card_v3" (3.0); PNG tEXt chunk named ccv3, JSON, or .charx zip with root card.json | assets array (sprites, backgrounds, audio via embeded:// URIs), nickname, group_only_greetings, multilingual creator notes, lorebook @@ decorators | V2-only frontends ignore ccv3 chunks and @@ decorators unless a fallback chara chunk is also written |
Watch out for one quirk in the Character Card V3 specification if you pack archives by hand: internal asset URIs inside a .charx zip are spelled embeded://path/to/asset.png (with a single “d”), and internal zip paths are case-sensitive ASCII. Also avoid sending raw PNG cards directly as chat photos on WeChat, Discord previews, or X/Twitter: image compression strips the tEXt metadata chunk. Always share an uncompressed file download, a zip, or a .charx / JSON export.
How can I make a SillyTavern card online without setting up Node.js?
Our team builds Foreverse, so weigh our view accordingly. We put our own card-authoring and inspection tools online for free so creators would not have to spin up a local Node.js server just to draft a character. Everything in Card Studio and Card Checkup runs inside your browser tab—nothing gets uploaded.
- Draft the permanent fields in Card Studio
Open /labs/card-studio, fill in
name, write concrete behavior indescription, set the immediate scene inscenario, and keep an eye on the live token counter per field. Your work autosaves in local browser storage; if you juggle multiple drafts or want live AI-slop and impersonation warnings as you type, use Card Workbench Pro. - Write an active opening scene and alternate greetings
Give
first_mesa clear time, place, and an immediate prompt for{{user}}to react to, then add one or twoalternate_greetingsfor alternate starting routes. Check macro expansion with Card Studio's preview or Macro Playground so stray{{char}}tags do not slip through. - Attach portrait art and export as V2 or V3
Drop an avatar image into the editor and export a V2 or V3 PNG card (or plain JSON). If you ever need to inspect or repack an existing card image byte-for-byte, PNG Card Embed & Extract reads and writes the Base64
tEXtchunks directly. - Run Card Checkup before starting a 50-turn test chat
Drag your exported file onto /labs/card-checkup. It checks the spec header, splits permanent tokens from one-time and keyword-triggered tokens, highlights dead lorebook entries with blank keys, and catches encoding glitches.
- Import into desktop SillyTavern or send straight to Foreverse
On desktop SillyTavern, open the Characters drawer and click Import Character from File. On mobile, click Send to my app inside Card Studio (uses email verification code sign-in) or import the PNG, JSON, or
.charxfile locally in Foreverse. On Android you can also draft offline from scratch under Characters → Create → Write it yourself; full steps are in our mobile card-writing guide.
How do you playtest a new card and stop out-of-character drift?
Throw three different openers at every new card: a lore check, mundane small talk, and an abrupt plot curveball. Change only one field between test runs so you can tell which edit actually moved the voice. A common cause of out-of-character drift is an internal contradiction—say, an aloof personality paired with a chatty, eager greeting—or testing edits inside an old chat thread instead of starting fresh.
Looking at what works in the wild helps set expectations. In our July 2026 census of 19,776 public cards on Mufy (950 million total chats across 4,596 creators), the median greeting among the top 1,000 cards ran 1,232 characters of prose, and one in three included a $-command list in creator notes. Correlation cannot prove why those cards drew crowds, but their openings are long, finished scenes rather than a one-line “Hey, what do you want?” Whenever world details only matter in certain rooms or subplots, pull them out of description and move them into an embedded character_book so they only cost tokens when keywords fire.
Manual edits, portrait swaps, and file exports in Foreverse are completely free. You only spend compute when you tap per-field AI suggestions or run live test chats, either through your own API key across 60+ preset providers at list rates or on our official metered channel (first sign-in includes 5,000 credits, 1 credit = $0.0001). Keep one mobile detail in mind: starting a chat clones the library card into that specific chat world, so after editing a master card under Characters → Edit character, open a new session (or edit that active chat's copy from the top-bar avatar) to test your changes.
Who should stick to desktop SillyTavern instead of Foreverse?
Foreverse imports V1–V3 cards and exports standard tavern-compatible PNG or JSON files, though desktop setups still win for several creator workflows:
- Authors who depend on third-party SillyTavern extensions (such as LLM-assisted Character Creator add-ons or full STscript pipelines): desktop SillyTavern supports the whole extension ecosystem, while Foreverse runs its built-in plugin center and an STscript subset.
- Collectors keeping dozens of work-in-progress cards at $0: Foreverse's free tier caps local storage at 3 character cards, 3 books, and 3 companions until the one-time $19.99 Pro unlock, whereas desktop SillyTavern stores unlimited files in a local folder.
- Writers who want one live workspace synced automatically between PC and phone: Foreverse has no cloud sync or web chat client, so cards move as exported files or via one-way Send to my app.
FAQ
Can I build a SillyTavern character card without writing raw JSON?
Yes. Visual editors—including SillyTavern's Character Management drawer, our free browser Card Studio (/labs/card-studio), and Foreverse's three-step creator on Android—give you ordinary text fields and pack the V2 or V3 JSON and PNG tEXt metadata automatically when you export.
Why did my PNG character card stop working after I sent it over Discord or WeChat?
Most chat platforms resize or recompress images sent in conversation, wiping the PNG tEXt chunks (chara and ccv3) that hold the character JSON. Send PNG cards as uncompressed file attachments, put them inside a zip, or export as .charx or .json instead.
Should card authors still use W++ or PLists formatting in 2026?
You do not need W++. SillyTavern's own documentation states a description can use any style, plain text included, while linking PList and Ali:Chat guides for creators who prefer compact lists. Heavy bracket syntax like [Character("name") {Mind("cold" + "smart")}] burns permanent tokens on punctuation; plain sentences or concise fact lines work cleanly without the overhead. Save rigid templates for status bars or lorebook entries where exact field labels help.
What belongs in description versus an embedded lorebook?
Anything true in every single scene—name, baseline personality, relationship to {{user}}, and core speech habits—belongs in description because it stays in the prompt every turn. Secondary characters, town histories, item stats, and subplot triggers belong in an embedded lorebook (character_book in V2/V3) so they stay out of context until their keywords appear in recent messages, keeping long chats cheaper and sharper.
Does Foreverse lock my cards into an app-only format?
No. Every card's detail screen in Foreverse exports a standard tavern-compatible PNG (portrait plus embedded metadata) or raw JSON. Because we have not tested every field combination against every SillyTavern build, double-check complex lorebooks and regex scripts after moving a card across apps.
Sources
- Character Card V2 Specification (malfoyslastname/character-card-spec-v2) (checked 2026-11-15)
- Character Card V3 Specification — PNG ccv3 & CHARX (kwaroran/character-card-spec-v3) (checked 2026-11-15)
- SillyTavern Documentation — Character Design & Permanent Tokens (checked 2026-11-15)
- SillyTavern Documentation — Characters Management & Import (checked 2026-11-15)