Importing and editing characters

Review the content before saving#

A character defines the person you talk to: their name, personality, writing style, greetings, and dialogue examples. It is separate from the model, so the same character can be used with different models. Expression and instruction following vary by model; a successful import does not guarantee identical behavior to the original app.

1. In Create, select a card file or paste settings. Supported formats include CCv1/v2/v3 JSON, PNG files containing card metadata, and CHARX.
2. Review the name, greetings, images, settings, selected history, and conversion limits in the preview.
3. If an item has the same name, choose a new import or an explicit update rather than assuming it will be overwritten automatically.
4. Save, use “Open character” (キャラを開く), select a greeting, and begin the conversation.

For Hub content, open its details and import preview from Discover. Entering a URL alone does not save it. Importing also does not make a character official. Check the author, source, and content-specific license, and use it within the permissions granted to you.

Make personality and dialogue examples specific#

For a first character, start with a short introduction, speech rules, a greeting that invites a reply, and a few dialogue examples. The manual Character.AI-style paste format requires Name. Put Definition last; the text that follows becomes its body. Here is an example for a fictional library guide:

Name: Rio
Description: A guide who helps visitors find books in a quiet library
Greeting: Welcome. What kind of story are you looking for today?
Definition: Speak calmly in English. Do not invent details about unfamiliar books.
{{user}}: I'd like an adventure story.
{{char}}: Would you prefer a journey or a mystery to solve?

The editor lets you refine greetings, style, scenario, dialogue examples, Lore, images, and generation settings. Concrete examples of questions and reply length often communicate your intent better than a label such as “kind” alone. To define the user's role or the setting separately, continue to Personas and worlds.

Understand Lore and migration limits#

A Lorebook supplies names and world knowledge when they become relevant. For example, use “north archive” as a keyword for the short definition “a room containing old voyage records.” Entries are selected according to activation conditions and estimated budgets, rather than all being inserted every turn. Researcher Debug lets you inspect which entries were used.

Support also differs for SillyTavern settings, BYAF scenarios, and Risu common-card extensions. Character.AI uses manual pasting or JSON; account access and automatic retrieval of all history are unsupported. Round-trip acceptance in external apps is incomplete, so inspect migrated settings, images, and dialogue examples. See Data and privacy for image URLs and Hub communications.

Use saved revisions and choose an export format#

The original file and edited revisions are stored separately. Existing conversations keep their selected character, preset, and Lore revisions; they do not automatically switch to the latest edit. Changing a greeting, for example, does not silently replace the settings of an ongoing conversation. Check and explicitly switch the conversation's revision when you want the update.

• CCv2/v3 JSON or PNG: move a card to a compatible app; check differences in V3-specific fields and additional images.
• CCv3 CHARX: bundle the card and embedded images.
• Kyalulu backup: restore edited content, settings, selected history, and images within Kyalulu.
• Original: retrieve the imported bytes, including unsupported elements retained there.

A card alone cannot represent all conversation history or Kyalulu settings. Review the export's loss report and open it in the destination app to verify the result. Imported history also does not automatically create successful generation records or memories. Manage memory separately, or choose another guide from the index.