Skip to content

Card formats & compatibility

Pyre reads and writes interoperable Tavern-style assets.

Supported formats

Format Import Export Notes
chara_card v1 PNG Yes No Older embedded PNG format; re-exported as v2.
chara_card_v2 PNG Yes Yes Primary card format.
PNG with ccv3 key Yes No Read as card data; Pyre keeps the v2-compatible field set.
Raw card JSON Yes No Import-only for cards distributed as JSON.
Persona PNG/JSON Yes Yes PNG Pyre tags persona exports so re-import keeps point of view.
Lorebook JSON Yes Yes Standalone World Info or embedded character_book.
SillyTavern preset JSON Yes No Imported into Pyre preset format.
Pyre preset JSON Yes Yes Re-imports as an editable copy.
SillyTavern regex JSON Yes No Imported into Pyre regex rules.
.charx archives No No Not supported.

Field fidelity

Pyre supports the standard chara_card_v2 fields: description, personality, scenario, first message, example dialogue, system prompt, post-history instructions, alternate greetings, tags, creator fields, talkativeness, depth prompt, embedded lorebook, and opaque extensions.

Extensions

extensions data is preserved opaquely. Pyre does not need to understand every other app's private fields to keep them alive during import/export.

Embedded lorebooks

Cards with character_book can keep that book hidden and bound to the character, or extract it into your lorebook library. On export, bound lorebooks merge into the card PNG so the world travels with the card.

Personas

Personas export as PNG cards tagged as Pyre personas. Re-importing keeps them as personas instead of treating them as ordinary characters. Bound lorebooks and gallery images travel too.

Chat formats

SillyTavern chats import only through a full SillyTavern Download Backup .zip. Loose .jsonl files are not a supported import path yet.

Pyre exports chats as SillyTavern JSONL or Pyre JSON. Pyre JSON is archival and preserves more structure, but single-chat Pyre JSON re-import is not currently supported.

See also