Character Cards (V2 Spec)

Abolitus supports standard character-card import so you do not need to rebuild your library manually.

For many users, this is the fastest way to go from "I am curious about the app" to "my real library already lives here."

If you have accumulated good cards over time, importing them is almost always better than rewriting them from memory.

Why Character Cards Matter So Much

Character-card import is often the highest-value migration feature because character identity is usually the hardest thing to reconstruct manually.

If the card already carries the tone, framing, and greeting that made the character work for you, preserving that foundation saves enormous time.

What Usually Imports Well

Character-card imports are best for carrying over:

• name,
• description,
• scenario,
• greeting,
• personality framing,
• and other common fields used across mainstream roleplay-card formats.

These elements usually carry the emotional identity of a character, which is why card import matters so much.

Supported Sources

In practice, this is useful for cards coming from ecosystems such as:

• SillyTavern,
• JanitorAI exports,
• and other tools that follow common card conventions.

If a card comes from a tool with slightly different naming or packaging conventions, it may still import successfully as long as the important fields are recognizable.

How to Import

The usual workflow is simple:

1. obtain the PNG or JSON card,
2. drag it into Abolitus or use the import flow,
3. open the imported character and review the fields before starting a serious scene.

That review step matters more than people think.

A card can import correctly at the data level while still needing small editorial cleanup to feel perfect in live use.

What You Should Check After Import

Always verify:

• greeting quality,
• scenario text,
• personality tone,
• example dialogue if present,
• and any voice or extra presentation defaults you care about.

Imported cards often work immediately, but a quick review saves a lot of confusion later.

What Does Not Always Transfer Perfectly

Some qualities are not stored purely inside the card itself.

For example:

• the old platform may have wrapped the card with hidden system instructions,
• the old route may have had stronger or weaker alignment,
• and sampler defaults may have changed how the same greeting felt.

That is why a migrated card should be tested in a short real conversation before you decide whether it needs revision.

Older Card Formats

If a card comes from an older or slightly different format, Abolitus can often still convert the important fields into a usable modern character record.

The key point is that you should not assume an old card is unusable just because it was not created specifically for Abolitus.

Large-Library Strategy

If you are importing dozens or hundreds of cards:

1. import a small representative batch first,
2. test greeting quality and tone,
3. decide whether you want a default wrapper or persona pattern,
4. only then import the archive at scale.

That workflow prevents a large library from landing in a half-tuned state that feels worse than it really is.

A Good Success Standard

The right success standard is not "the imported card is identical to the old platform in every hidden way."

The better standard is:

• the character still feels like itself,
• the important fields survived,
• and Abolitus gives you enough control to finish the tuning pass quickly.

Related Pages

• Read Migration Overview for the bigger strategy when cards are only part of the move.
• Read SillyTavern Migration if your library comes from a heavier local-roleplay setup.
• Read JanitorAI Migration if your expectations were shaped by a hosted platform rather than a local-first client.