Skip to content

Importing & exporting cards

Pyre reads and writes the standard chara_card_v2 format, so your characters, personas, lorebooks, and presets move freely between Pyre and the rest of the ecosystem.

Importing characters

Pyre accepts character cards in three ways.

From a PNG

Drop in a chara_card_v2 PNG — the SillyTavern/Tavern standard, where the card JSON is embedded in the image's tEXt/chara block. Pyre reads both v1 and v2 cards, so an older card still imports cleanly.

From JSON

Raw chara_card JSON files import directly, for cards distributed as plain .json rather than embedded in an image.

By URL

Paste a link to a card and Pyre fetches it for you:

  • Trusted hosts import automatically.
  • Arbitrary URLs go through a manual review dialog that surfaces the URL so you can confirm it before anything downloads.

Why the review step

Showing the URL before the fetch keeps you in control of where Pyre reaches out. Trusted hosts skip the dialog; anything else asks first.

Import sources

Pyre can pull cards from a small set of trusted card hubs.

BotBooru (flagship)

BotBooru is the community card hub Pyre integrates with directly, and it's where Discover opens by default. Browse the site inside Pyre's in-app window and one-tap PNG import pulls a card straight into your library. The safety model:

  • the host is verified before any download fires (no SSRF),
  • redirects are refused, and
  • downloads are size-capped at 25 MB as an out-of-memory guard.

Note

Pyre is not affiliated with BotBooru — it's a convenience integration into a public community. See Cross-device sync for how Discover behaves per platform, or the BotBooru / Discover availability table.

Other trusted hosts

The in-app browser is locked to a trusted-host allowlist that also includes chub.ai, characterhub, and their CDNs. The same host-verified, redirect-refused, size-capped fetch applies to imports from any of them.

Exporting characters

chara_card_v2 PNG export

Save any character — one you made or one you imported — back out as a Tavern-compatible PNG. The export is full-fidelity:

  • bound lorebook entries are merged into the card's character_book, so other apps see the world too,
  • the opaque extensions block round-trips untouched, and
  • creator notes are carried over.

That means a card exported from Pyre lands in another Tavern-compatible app — or on BotBooru, or in a Discord channel — with its lore and metadata intact.

Personas

Personas import and export like characters:

Action Formats
Persona export chara_card_v2 PNG
Persona import .png or .json

A persona's mini-gallery images are included in its export, the same way they're carried when you convert a character with Add as persona. See Characters & personas.

Lorebooks

Lorebooks (World Info) import and export both ways:

  • Standalone — a lorebook on its own as a file.
  • Embedded-in-card — a character_book carried inside a character. On import you can keep it bound to that character; on export, all bound entries merge back into the PNG's character_book.

Manage them under More → Lorebooks. See Lorebooks (World Info).

SillyTavern preset import

Bring your existing SillyTavern presets in. Pyre parses ST's prompt-pipeline DSL — prompts plus prompt_order with the chatHistory marker — and maps it onto Pyre's own template tokens:

SillyTavern marker Maps to
charDescription {{description}}
charPersonality {{personality}}
scenario {{scenario}}
personaDescription {{persona}}
dialogueExamples {{mesExample}}
worldInfoBefore / worldInfoAfter {{wiBefore}} / {{wiAfter}}
enhanceDefinitions resolved into the template

It also carries over impersonate/continue overrides and sampling parameters. Re-importing a preset that Pyre itself exported passes through cleanly. See Presets & sampling and Macros & template tokens.

Chat transcripts

You can also export a conversation as a chat transcript — the running text of a single chat, separate from the cards involved.

See also