Skip to content
An independent field guide to AI character platformsResearch edition · October 2026
charactersFind your fit
KEEPING A CHARACTER YOU CREATED

AI character cards: JSON and PNG.Know what is inside the file.

A character card is a reusable definition: who a character is, how they speak and how a scene begins. JSON stores that information as text; a card PNG packages data with an image. Neither is the same as a chat archive. Start with an original example, then check the file your destination actually accepts.

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.

A complete Character Card V2 JSON example.

Mara Vale is our original lighthouse archivist. The file below is generated with the same serializer as our builder. Download it unchanged to inspect the structure, or open the example in the builder and rewrite the premise. No provider account or hidden character definition was used.

Inspect the complete V2 JSON file
{
  "spec": "chara_card_v2",
  "spec_version": "2.0",
  "data": {
    "name": "Mara Vale",
    "description": "Mara Vale is an adult archivist responsible for the maps stored beneath a working lighthouse. She wants to find the missing page of a coastal survey before the next supply boat leaves. She carries a brass compass with a cracked lid and treats every claim as something to verify.",
    "personality": "Patient, observant and dryly humorous. Mara asks one precise question at a time, describes tangible details and explains how she reached a conclusion. She treats the visitor as a collaborator with their own choices.",
    "scenario": "A storm has delayed the supply boat. {{user}} arrives at the lighthouse with an unsigned map. Mara recognizes the paper but does not know who drew it.",
    "first_mes": "Mara clears a space on the map table. “That paper is older than the ink on it.” She points to a small mark beside the harbor. “Where did you find this?”",
    "mes_example": "<START>\n{{user}}: Are you certain the mark is a code?\n{{char}}: “Certain? No.” Mara opens her notebook. “It appears on three surveys, always beside a place where the tide changes. We can test the fourth.”",
    "creator_notes": "An original mystery-writing example by Characters.best. Adapt the definition and opening scene to your own project. No conversation performance is implied.",
    "creator": "Characters.best",
    "character_version": "1.0",
    "tags": [
      "original character",
      "mystery",
      "coastal exploration"
    ],
    "alternate_greetings": [],
    "system_prompt": "",
    "post_history_instructions": "",
    "extensions": {}
  }
}

In V2, spec is chara_card_v2, spec_version is 2.0, and the character fields sit inside data. first_mes holds the greeting and mes_example holds example dialogue. The field-by-field builder guide explains where to put your own writing.

Creator notes are reader-facing metadata, not personality instructions. This example leaves prompt overrides empty and contains no lorebook, avatar or chat history. These choices match our builder's scope; they are not a claim that V2 forbids additional fields. Read the V2 specification.

If editing the downloaded JSON by hand, preserve double quotes around keys and strings. Escape a quote inside a string as \" and a line break as \n; do not add comments or a trailing comma. The builder handles this formatting for you. A structurally valid file still needs an import check in your chosen app.

Why a PNG or JSON character card will not import.

First preserve the original file. Then use the symptom to choose one check, rather than repeatedly changing the extension or overwriting the card.

A practical diagnostic checklist · not a tested product error catalogue
What you seeWhat to checkNext step
A PNG opens as a portraitAn image viewer alone cannot establish whether the PNG contains card data. A screenshot or avatar may only be an image.Use the creator's explicit card download, then inspect the imported definition. Renaming a portrait to JSON cannot add missing fields.
The JSON cannot be readThe download may be an HTML error page, a chat archive or malformed JSON rather than a card.Open a copy in a text editor. For V2, check the markers and nested data object against the example above. Keep the original intact.
The JSON parses but the app rejects itValid JSON is not necessarily a supported character format.Confirm the destination's accepted version and use character import rather than chat import. If necessary, move your own fields with the text brief.
The character appears without an avatarA text-only JSON definition does not supply an image.Add an image you have permission to use through the destination's avatar control, or use a supported card PNG from its original source.
The greeting works but lore or history is missingThese may have been separate files, app-specific settings or absent from the export.Compare the stored definition, lorebook and chat files separately. Do not infer that a successful character import transferred all account data.

In SillyTavern, the character panel has separate character import, avatar, lore and export controls. Inspect the result there before testing a conversation. The interface and model can interpret the same definition differently.

Looking for a character cards archive?

Distinguish a library of downloadable definitions from a directory of characters you can chat with. Our public character collection links to source profiles and credits creators; those links do not establish that a card file is available or licensed for reuse. A public introduction is not the full character definition.

  1. Find the original creator or publisher. Prefer an explicit card download with format and version information over a reposted portrait.
  2. Read the reuse terms and dependencies. Keep credits and notes with the file; check whether a separate lorebook or setup is required.
  3. Keep a small local record. Save the source URL, download date, creator, version and your edits alongside the untouched file.

To start without a third-party archive, use our six original character templates. Each opens an editable definition that you can download as V2 JSON. A character card is a file format, not a promise of compatibility with Character.AI or another service that happens to use the word “character”.

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.

Primary-source routes · no import round trip performed
PlatformDocumented routeCheck separately
SillyTavernCharacter panel import and export actions. Official guideSupported version, retained fields, avatar and any linked lore in your installed version.
CrushOn.AIJSON or PNG character-card imports into the creator. Official guideMissing creator fields and visibility after import. Native export remains unestablished here.
PolyBuzzPublic guidance for importing downloaded character JSON or PNG cards. Official guideThe current import flow, preserved fields and a separate avatar for text-only JSON. Native export remains unestablished here.
DreamGenScenario export to a file for private sharing and import. Official guideCompatibility 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.

  1. Keep an untouched original. Save the file and your own written definition separately. Record the source platform and date.
  2. 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.
  3. Inspect the destination after import. Compare name, description, personality, greeting and examples with the original. Check lore and metadata separately.
  4. Choose the model and setup. A definition describes a character; it does not include a running model, subscription or media allowance.
  5. 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.

V2 structure and SillyTavern character controls were reread on . This was a scoped source check; the other platform routes retain their earlier review dates. 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.

Read the research methodology and editorial policy.