What is Character Card V2? The roleplay card format explained
Updated
Character Card V2 is a shared format for AI roleplay characters, marked by "spec": "chara_card_v2". It wraps the original card fields (name, description, personality, scenario, first message, example dialogue) in a data object and adds alternate greetings, creator notes, a system prompt, post-history instructions, tags and an optional lorebook. UnsavedAI imports V1, V2 and V3 cards and exports V2.
Try it now, free, no account neededStart a story with Nora BellThe shy librarian has been leaving you notesThe shape of a V2 card
A V2 card is a JSON object with three top-level keys. Trimmed down, it looks like this:
{ "spec": "chara_card_v2", "spec_version": "2.0", "data": { "name": "Nora Bell", "description": "...", "personality": "...", "scenario": "...", "first_mes": "...", "mes_example": "...", "creator_notes": "...", "system_prompt": "", "post_history_instructions": "", "alternate_greetings": [], "character_book": null, "tags": ["romance", "bookish"], "creator": "", "character_version": "1.0", "extensions": {} } }
The spec and spec_version lines tell an app which rules to read the card by. Everything about the character lives inside data.
What V2 added over V1
- alternate_greetings: extra opening messages, so one character can start several different stories. See alternate greetings.
- system_prompt: instructions from the card author that replace or extend the app's main prompt.
- post_history_instructions: a note placed after the chat history, right before the model replies. Useful for short reminders about style.
- character_book: a lorebook bundled with the character. See what a lorebook is.
- creator_notes, tags, creator, character_version: information for people browsing cards, not for the model.
- extensions: a place for apps to store their own extra settings without breaking other apps.
V1 cards had the six core fields at the top level with no wrapper. V3 ("chara_card_v3") builds on V2 with extras such as embedded assets, and PNG V3 cards also carry a "ccv3" chunk. Most apps read all three.
Common mistakes
- Editing a PNG card in an image editor and saving it: the card text inside is usually stripped. Edit the fields in an app and export again.
- Putting the whole backstory in creator_notes. Most apps show that field to people, not to the model.
- Filling system_prompt with generic rules ("you are a helpful roleplayer"). If the app uses it, it can override better instructions the user already set up.
- Hand-editing JSON and leaving a trailing comma, which makes the file fail to import.
V2 in UnsavedAI and other apps
SillyTavern, Chub and most character apps read and write V2. On UnsavedAI you can import a V1, V2 or V3 card as PNG or JSON at /chat/custom: the name, description, personality, scenario, greeting, example dialogue and up to five alternate greetings come across. Characters you make can be downloaded as a V2 file, so they open in SillyTavern with nothing lost from the core fields. Try importing a card and talking to it, or start with a house character like Nora Bell to see what a well-filled card feels like.
Questions people ask
Is Character Card V2 the same as a Tavern card?
Yes, people often call them Tavern cards or TavernAI cards because the format grew out of TavernAI and SillyTavern. V2 is the version most apps share today.
Do I need V3?
Not for most characters. V2 covers everything a normal roleplay character needs; V3 matters mainly when a card bundles extra assets.
Does the lorebook inside a card work everywhere?
Only in apps that support lorebooks. Apps without one simply ignore the character_book field and use the rest of the card.
