Character cards can now be imported and exported as structured JSON. Standard V1, V2 and V3 PNG or JSON cards are accepted. Export automatically creates a V3 PNG when the card has a usable portrait, or JSON when it does not; cards with multiple linked world books let you choose which one to embed.
World books can now be imported and exported as widely compatible JSON. Compatible world-book data embedded in PNG files can also be imported.
Improvements
Editable character cards now use structured V3 JSON as their canonical data. Existing Markdown cards receive a matching JSON copy while the original file remains untouched for rollback to an older app version. This removes Markdown-heading ambiguity without discarding existing data.
Character-card and world-book round trips preserve data the app does not edit. Standard fields, extension data, asset declarations, embedded world books and unknown future fields are retained across import, edit, export and Workshop packaging.
Subscribed world books are edited at their real source location. Changes no longer go to an unused shadow copy, and imported or subscribed linked world books load correctly in conversations.
All new and revised interface text in these workflows is localized across all 31 supported languages.
Fixes
Character-card text containing Markdown headings is no longer truncated or assigned to the wrong field. Literal text such as "##", section-like names, fenced code blocks and large descriptions now survive saving and reopening intact.
Adding, replacing and removing a custom character image works again. Images are stored in the writable profile directory, failures are reported instead of being silently swallowed, and the editor keeps unsaved input available for retry. Workshop packages now include the correct portrait.
One damaged character card can no longer hide the entire character list. Valid cards continue to load, while the damaged entry remains identifiable and removable.
Common single-value and list variants import without losing greetings, alternate greetings or tags.
Character cards and world books retain booleans, priorities, keys and unknown fields through editing and export. JSON files with a byte-order mark are also accepted.
Built-in character cards shared to the Workshop now use the currently selected interface language.
Workshop validation now recognizes valid V3-only character-card PNG files and rejects ordinary or damaged images with a clear error.