Importing & exporting
Pyre is built to move cleanly through the Tavern-card ecosystem. Characters, personas, lorebooks, presets, regex rules, and SillyTavern backup content can come in; cards, personas, chats, lorebooks, presets, and full backups can go out.
What you can import
| What | Accepted formats | Where |
|---|---|---|
| Character cards | PNG with embedded chara / ccv3 data, or raw card JSON |
Characters +, From file, From URL, Discover, SillyTavern import |
| Cards by URL | chub.ai / characterhub pages, Chub numeric share links, BotBooru post/character pages, RisuRealm pages, direct .png / .json links such as catbox or pixeldrain |
Characters + -> From URL, or Discover import-by-URL |
| Embedded lorebooks | character_book inside an imported card |
Offered during card import |
| Standalone lorebooks | SillyTavern World Info export, bare character_book JSON, Pyre lorebook JSON |
Lorebooks library, BotBooru Download JSON, SillyTavern import |
| Presets | SillyTavern chat-completion presets, Pyre preset JSON | Presets import, SillyTavern import |
| Regex rules | SillyTavern regex JSON: single script, array, or regexScripts wrapper |
Regex rules import, SillyTavern import |
| Personas | Character-card PNG/JSON converted to persona, or native Pyre persona JSON | Personas import, SillyTavern backup import |
| SillyTavern chats | .jsonl chats inside SillyTavern's full Download Backup .zip |
Backup & Restore -> Import from SillyTavern |
Character cards
Pyre reads community-standard card PNGs and raw JSON. It supports old chara v1/v2 embedded data and v3 ccv3 PNG keys, while keeping the v2 field set Pyre understands.
On import, a card's opaque extensions block is preserved so data from Risu, SillyTavern, Chub, and related tools survives a Pyre round trip.
Import by URL
Paste a supported URL and Pyre fetches the card for you. Trusted card hosts can import directly. Arbitrary public HTTPS links show a review dialog first, then run through protections such as redirect refusal, anti-SSRF checks, DNS-rebinding guards, and a 25 MB cap.
Supported sources include BotBooru, chub.ai / characterhub, RisuRealm, direct .png / .json links, and common file hosts such as catbox and pixeldrain.
Discover and BotBooru
Discover opens trusted card hubs from inside Pyre when the platform supports an embedded browser:
- Android: embedded in-app browser.
- Windows: embedded Edge WebView2.
- Web/PWA via desktop or self-host hub: embedded through a separate-origin proxy.
- Linux and standalone public web: external browser fallback.
In embedded Discover, BotBooru's card download and lorebook Download JSON buttons can hand supported files directly to Pyre's confirm-before-import flow.
Note
Pyre is not affiliated with BotBooru. It treats BotBooru as a trusted community source for cards and lorebooks, not as Pyre's backend.
SillyTavern import
Use Backup & Restore -> Import from SillyTavern for the broadest import path.
You can select loose mixed files, and Pyre will sniff each one as a card, lorebook, regex rule, or preset. Or choose SillyTavern's full Download Backup .zip to import characters, worlds, presets, regex rules, personas with avatars, and supported chats in one pass.
The summary shows what landed and what was skipped. One bad file does not abort the whole batch.
Secrets are skipped
SillyTavern's secrets.json is hard-skipped. Pyre does not read or import API keys from a SillyTavern backup.
SillyTavern chats
Pyre can import SillyTavern chats through exactly one door today: SillyTavern's full Download Backup .zip, chosen from Backup & Restore -> Import from SillyTavern.
Supported behavior:
- chats bind to their matching imported character,
- persona hints are linked when available,
- timestamps are preserved,
- SillyTavern swipes become Pyre variants with the selected swipe active.
Not supported yet:
- loose single
.jsonlchat files, - SillyTavern group-chat logs,
- Chub chat logs,
- re-importing Pyre's own single-chat JSON export.
For moving Pyre chats between Pyre installs, use full backup or sync.
Presets
Pyre imports SillyTavern chat-completion presets and maps ST markers into Pyre tokens. Modular presets arrive as prompt blocks with roles, before/after-history placement, toggles, and depth where applicable.
Imported presets can carry sampling parameters and the supported impersonation / continue prompt fields. Pyre's own preset JSON re-imports as an editable copy.
Regex rules
Pyre imports SillyTavern regex scripts, including find/replace text, flags, trim strings, placement streams, and prompt/display stages where they map to Pyre. Scripts targeting streams Pyre does not have arrive disabled for review.
Re-imports skip duplicates and report how many rules were added.
What you can export
| What | Export format | Notes |
|---|---|---|
| Characters | Tavern-compatible chara_card_v2 PNG |
Bound lorebooks merge into character_book; gallery images export alongside where available. |
| Personas | Tavern-compatible PNG tagged as a Pyre persona | Bound lorebooks and gallery travel too. |
| Chats | SillyTavern JSONL or Pyre JSON | ST JSONL is portable but lossy; Pyre JSON keeps variants/branches/snapshots but is archival, not a single-chat re-import path yet. |
| Lorebooks | JSON | Re-importable by Pyre; can also be embedded into a card. |
| Presets | JSON | Re-imports as an editable copy. |
| Everything | Full backup JSON | Best path for moving a complete Pyre install. |
Chat export caveats
SillyTavern JSONL exports the selected variant as the visible message. OOC and scene turns are prefixed. Party chats collapse to a portable transcript with Pyre-specific attribution hints where possible, because ST does not have Pyre's full party/branch model.
Use Pyre JSON when you want an archival copy with variants, branches, and snapshots preserved.