How to recreate a Character.AI character in another app

To recreate a Character.AI character in another app, prepare a short set of character notes, a checked account of the history you want to keep, and a clear scene to start from.

That gives the new setup something specific to work with. It does not transfer the original AI, its hidden settings, or everything that happened in a long conversation.

If you still need a private copy of your chats, start with the Character.AI export guide. If you have not chosen where to play next, the alternatives comparison covers JanitorAI, Kindroid, Nomi, and fiabai. This guide focuses on what to write once you are ready to set up a character again.

Cover: AI-generated illustration of Rowan Vale, an original fictional adult character used in the examples below. It is not an app screenshot.

What you can recreate

Start with a character you created, or material you have permission to reuse. Gather the background, traits, and writing examples you want to preserve, rather than assuming a public character's full definition is available.

Character.AI's definition visibility guide distinguishes access to a character from access to their Definition. Being able to chat with a character does not mean you can see their hidden settings. Being able to see something is not, by itself, permission to copy it into another service.

An AI's description of itself is also not a reliable way to recover a creator's private definition. You can use a description as a draft of how the character comes across to you, then check it against the material you are entitled to use.

Nomi's migration guide makes the distinction directly: there is no direct transfer of an AI, but information about identity, personality, and shared history can help recreate a character as a Nomi. Treat this as a new setup based on selected information, not a promise that the same personality or every memory will be restored.

Keep your original archive separately. Remove unnecessary real names, contact details, and other private information from the smaller note you plan to enter into a new service.

Make a character setup note

Use one editable document before dividing the information among the new app's fields. The template below is a writing aid, not a file format an app can necessarily import.

CHARACTER
Name and adult age:
Appearance:
Personality, background, and motivation:

VOICE
Tone, length, and narration style:
An original dialogue example:

YOUR PERSONA AND RELATIONSHIP
Who you play:
How the two characters know each other:

CONFIRMED HISTORY
Important events and their lasting consequences:

CURRENT SCENE
Where and when:
What is happening:
What is still unresolved:

BOUNDARIES AND PLAYER CONTROL
Content limits:
Which actions and dialogue the player decides:

An explanatory diagram of this guide's template, not an app screen or an official import format. The copyable version is above.

Check a summary before using it

Choose facts that will matter when the conversation resumes. A name, a changed relationship, a promise, or an unfinished task is usually more useful than a transcript of every small gesture.

JanitorAI's Chat Memory guide separates the environment, relationship, current plot, character notes, and important past events. That is a useful way to review a summary without treating every detail as permanent background.

You can draft a summary yourself. If you ask an AI for help, give it only the material you intend it to read and check the result against that material. For example:

Summarize the roleplay excerpts below as brief factual notes. Separate the character's background, established relationship, completed events, current situation, and unresolved questions. Do not invent missing details or turn a possible outcome into something that already happened. Mark anything the excerpts do not establish as unknown.

This is an example request, not a transcript of an actual export or migration. If the relevant part of a conversation is missing, an AI-generated recap does not fill that gap with verified history. Leave uncertain details out until you can check them.

A worked example: Rowan Vale

Rowan is an original fictional character for this guide: a 28-year-old former travelling performer who now looks after an old theatre. The setup and story facts below are invented writing examples, not records of a Character.AI chat or results from another service.

For the player's role, this example uses Alex, an adult volunteer helping at the theatre. You can replace that role and name with your own.

CHARACTER
Rowan Vale is 28. He was a travelling stage performer.
He now manages and cares for an old theatre.
He has loosely tied dark navy hair and grey-green eyes.
He wears an ivory shirt and a charcoal waistcoat.
He is observant, quietly playful, and careful with old props.
He wants the theatre to remain a welcoming place.

VOICE
Warm, understated English with occasional dry humour.
Use short dialogue and brief third-person action descriptions.
Original example line:
"A little dust never ruined a performance. A loose hinge might."

YOUR PERSONA AND RELATIONSHIP
Alex is an adult volunteer helping with the evening's clean-up.
Rowan and Alex are friendly colleagues, not established partners.
Alex decides Alex's own words, actions, and feelings.

CONFIRMED HISTORY
For this fictional setup:
- Rowan and Alex finished putting away the stage props.
- Alex told Rowan a letter had been left in the audience seats.
- Rowan agreed to help look for it.

CURRENT SCENE
The theatre has closed. Rowan and Alex are beside the stage.
The audience seats are empty and the house lights are dim.
Rowan has a small lantern. The letter has not been found.
Neither its contents nor its precise location is established.

BOUNDARIES AND PLAYER CONTROL
Keep the scene non-explicit and free of graphic violence.
Write Rowan's actions and the surroundings.
Leave Alex's decisions and dialogue to the player.
Let the player choose the next place to search.

Notice where the information goes. Being observant belongs to Rowan's character. Having agreed to help is an event in this example's history. Standing beside the stage is the current situation. Finding the letter is not an event yet.

Explanatory diagram of the invented example, not a chat log. A possible discovery stays unresolved until it happens in the story.

You do not need to preserve every sentence of this example. Keep what defines your character and the scene you want, then shorten or split the note to fit the destination's fields. Change the relationship explicitly if you want a different one; do not rely on a new model to infer it from a familiar name.

Put each part in the right field

The same note will need different placement in different apps. Read what each field is for before pasting a whole profile into the first box that looks suitable.

JanitorAI

The character creation guide says Character Bio is for people browsing the character, not information used by the bot.

For the Rowan example, put his identity, traits, background, and dialogue example in Personality. Use Scenario for the theatre setting and Alex's relationship to him, and Initial Message for the opening. Keep the ongoing situation and important events concise in Chat Memory, following its memory guide.

Character.AI's Definition guide documents its own variables and dialogue format. Do not assume those conventions carry over unchanged. Use clear names in your working note, then adapt any placeholders or dialogue examples to the receiving app's guide.

Kindroid

Kindroid's customization guide calls the former Backstory field Personality. Use that for Rowan's identity and background, Key Memories for relevant established facts, and Example Message for the voice and response format you want.

Keep Response Directive short and specific rather than pasting the entire note there. Define Alex separately through a user persona so that information about the player is not mistaken for Rowan's biography.

The greeting is supplied when creating a Kindroid and becomes its first chat message; the guide says it is not a greeting field you can edit later in settings. Distinguish an initial greeting from a message you send to establish a new scene in an existing chat.

Nomi

Backstory+ has sections for different kinds of context. Put foundational identity and background in Backstory, guidance about expression in Inclination, and the active situation in Current Roleplay. Use the relevant sections for appearances, preferences, and boundaries.

Nomi's migration guide also suggests Mind Maps for supporting history, people, places, themes, and goals. Group related information rather than trying to turn every exchanged line into a separate permanent fact.

fiabai

fiabai's character guide separates the character's core from the scenario. Put Rowan's appearance, personality, and voice in the character setup, and use Base dialogue examples for short original exchanges that demonstrate how he speaks.

In the scenario, define You and the character, Who you are in this scenario, the setting, and the Opening scene. Put the preference to leave Alex's decisions to the player in Narration and style rules.

For a free-talk scene, place relevant starting context in Setting (the base for the chat). The guide distinguishes that field from phase-based progression; do not put essential context only in a field the selected mode does not receive.

None of these placements proves that an app can import a Character.AI export file. If you want to use an importer, check its supported source and format separately before giving it your archive.

Start from a clear scene

Once the character and relevant context are set, begin with the moment you want to play. Avoid a first message that merely says “Remember everything from before?” when the new app has not received that history.

For Rowan, a restart message from the player could be:

Continue the fictional theatre scene from the setup notes. Rowan and Alex have finished putting away the props. The letter is still missing, and they are beside the stage after closing. Write Rowan's next action and line in warm, understated English, with brief third-person narration. Leave Alex's words, feelings, and choice of where to search to me.

AI-generated illustration of the example's starting scene, not a screenshot or a reply produced by any of the services above.

After a few exchanges, check the parts of the setup you can actually observe:

• Does Rowan sound like the voice you described?
• Does the conversation keep the friendly-colleague relationship rather than inventing a different one?
• Does it preserve the starting facts without announcing that the letter was already found?
• Does it leave the player's dialogue and decisions open?

If the opening is too long, revise the voice guidance or example. If the relationship is wrong, state it more clearly in the relevant context. If it invents a completed event, correct that fact before extending the scene. Change one part at a time so you can see what helped.

A short scene can reveal a mismatch in tone or starting context. It cannot prove long-term memory accuracy or that the new character will behave exactly like the old one. Keep your editable note, update it with events you have checked, and use it to start from a scene you actually want to continue.