Character Card V2 / V3 and editor compatibility: don’t lose fields
Part 4. Exact V2/V3 definitions belong to specs and ST release notes; here: what goes wrong in editors.
Why a card “breaks after editing”
Different character card editors support different spec versions, extensions, and nested keys. Outcomes:
- Silent drop of unknown keys.
- ST ignores some fields on import.
- You “saved” but actually exported a smaller subset.
Rule: copy the original before import; diff exports when possible.
V2 vs V3 in plain language
“V2” often maps to the Character Card V2 community spec; “V3” may mean different things in different tools (card spec vs UI features). Don’t memorize a fake V3 key list—verify with your ST build and exports.
Do:
- Read the V2 explainer and your ST version docs.
- Check export spec / spec_version fields.
- After import, spot-check fields against field series.
Checklist (verbs)
- Duplicate the PNG:
name.backup.png. - Edit → export from the target editor.
- Skim JSON for
extensions,character_book, etc.—still present? - Import into ST → new chat smoke test.
See also
Previous: (3/5) Third-party editors
Next: (5/5) Extensions, LLM, cover art
Series index: Silly Tavern card editors · index
Edit PNGs locally so “saved” really means saved—try Sillycard on macOS. Features: App Store and in-app copy.