Format guidance, not a tested transfer service. We checked public specifications and product guides. End-to-end imports, field preservation and old conversation continuity have not been tested.
Start with what the file carries.
- Character definition
- Identity, behavior and a starting premise. A V2 card has named fields for description, personality, scenario, first message and dialogue examples, plus metadata. Our builder produces a new JSON definition in that shape.
- PNG character card
- A card can put descriptive data inside an image file. An ordinary avatar PNG is only an image; renaming it or choosing the PNG extension does not add a character definition. Check that the file actually came from a card export.
- Scenario file
- A platform can package a whole scene rather than one card. DreamGen documents private scenario export and import. That establishes a route for its scenario file, not compatibility with every character-card editor.
- Chat archive
- A record of a conversation. It is separate from the definition that starts a character. Even if a destination loads a definition, old chats, summaries, provider-side state and paid access have not been transferred by that action.
What the reviewed guides establish.
Read each row in one direction. An import document for the destination does not establish an export feature in your current service. A documented route still needs a file-level check.
| Platform | Documented route | Check separately |
|---|---|---|
| SillyTavern | Character panel import and export actions. Official guide | Supported version, retained fields, avatar and any linked lore in your installed version. |
| CrushOn.AI | JSON or PNG character-card imports into the creator. Official guide | Missing creator fields and visibility after import. Native export remains unestablished here. |
| PolyBuzz | Public guidance for importing downloaded character JSON or PNG cards. Official guide | The current import flow, preserved fields and a separate avatar for text-only JSON. Native export remains unestablished here. |
| DreamGen | Scenario export to a file for private sharing and import. Official guide | Compatibility outside DreamGen and whether a different format is needed for a card editor. |
Character.AI, Janitor AI and SpicyChat native exports have not been established in our current review. This describes a research gap, not proof that an export is impossible. Third-party extraction tools are outside this guide’s tested scope.
Move one character before moving a collection.
- Keep an untouched original. Save the file and your own written definition separately. Record the source platform and date.
- Identify the format. Inspect whether it is a card, a scenario or a chat archive. For a V2 JSON card, inspect the spec marker and data fields instead of relying on its filename.
- Inspect the destination after import. Compare name, description, personality, greeting and examples with the original. Check lore and metadata separately.
- Choose the model and setup. A definition describes a character; it does not include a running model, subscription or media allowance.
- Start a small new scene. Check the greeting and speaking style. Record edits and dropped fields before migrating more characters.
This is a suggested checklist. Our own builder exports have been checked for their generated structure; we have not imported them into these products or measured conversation behavior.
If the platform has no verified export.
Work from material you created and can access: the backstory, personality instructions, greeting, scenario and example dialogue. Keep world facts in a separate note so you can decide where they belong in the destination. A text brief gives you a readable backup even when a file import is unavailable.
A hidden character definition or an old account’s stored memory cannot be reconstructed by a file-format tool. Keep those gaps explicit. Our free character card builder helps write a new definition from your own text; it does not access platform accounts.
Common questions.
Is every PNG portrait a character card?
No. A card PNG carries additional descriptive data. An ordinary portrait does not become a card by renaming it. Check the export source and the destination’s import result.
Will a character card carry the conversation’s memory?
A definition and a chat archive are different artifacts. A card can supply background text, but this does not transfer old conversations, provider-side state or establish later recall.
Can I use the same JSON card everywhere?
Do not assume that. The file version and the destination’s supported fields matter. Inspect a small import first and keep a readable text brief for manual reconstruction.
Does a V2 card include an avatar?
The JSON definition generated by our builder contains text and metadata. It does not embed an image. A destination may let you add an avatar separately; a PNG card is a different package.
Primary sources & scope.
Public sources reviewed for the file structure and the routes above. The platform passports contain the broader feature review and its dates. We do not install extraction extensions, log in to provider accounts or promise a universal migration.