Preview · revised 2026-05-21 · corrections welcome

The character card compatibility matrix.

Field by field: which parts of a Tavern V2 / V3 character card we expect to survive when you take it to Chub.ai, RisuAI, or SillyTavern — based on the public specs and our initial import / export checks. We publish this preview openly so creators can plan migrations instead of guessing, and so the community can correct us where it's wrong.

supported·~ partial / dropped on older clients· not supported·– not in this spec
fol. iii.v

Field by field

Each row is one card field. Spec columns show whether the field exists at all; platform columns show whether the host preserves it on import / export.

fieldV2V3ChubRisuSillyTavern
name
description
first_mes
personality
scenario
mes_example
creator_notes
system_prompt
post_history_instructions
alternate_greetings[]
tags[]
Chub uses tags for search; Risu / ST surface only as metadata.
~~
creator
character_version
character_book (lorebook)
Entry-level fields differ between V2 and V3 — see below.
extensions.*
Platform-specific keys; foreign keys are kept but ignored.
~~~
assets[]
V3-only multi-asset (icon / background / emotion). Lossy when exported to V2 hosts.
~
nickname
~
creator_notes_multilingual
V3-only; non-V3 hosts read English notes only.
source[]
~
group_only_greetings[]
~~
creation_date / modification_date
~~~
lorebook entry.use_regex
Older clients treat the key literally — regex characters render as plain text.
~~
lorebook entry.decorators[]
@@-decorator syntax in entry content; older clients show the raw tokens.
~~
fol. iii.b

How we built it

Specs come straight from the public V2 / V3 references malfoyslastname/character-card-spec-v2 and kwaroran/character-card-spec-v3.

The platform columns are a best-effort preview compiled from each client's published behavior, community reports, and our own initial import / export checks as of 2026-05-21. Client behavior changes — sometimes silently — so treat each cell as a working hypothesis rather than a guarantee. We'll publish versioned fixtures and tested client builds with the closed beta in Q3.

If a row looks wrong to you, the fastest fix is an email or a Discord ping — we'd rather be corrected than wrong, and we'll credit the contributor on the next revision.

Trademarks belong to their owners. This page describes interoperability between the public specs and clients; it does not imply endorsement.