Any Card → Character Card V3

1. Universal input

Drop in a V1 flat JSON, a V2 PNG (base64 in the chara tEXt chunk), a Voxta/CAI JSON, or an existing CharX — the engine normalizes any of them to a common persona model before upgrading.

2. Emitting the V3 schema

The normalized persona is written into a chara_card_v3 / spec_version 3.0 object with the full V3 data block, including group_only_greetings, an assets descriptor, and an extensions slot. The core persona — name, description, personality, scenario, greeting, and example dialogue — carries over intact.

3. Where V3 is used

V3 is the emerging standard adopted by newer frontends and by RisuAI, which reads V3 through its CharX container. Exporting to V3 keeps your character future-proof as more apps add support.

4. Private, client-side conversion

Every step runs in your browser using JavaScript. Your card is read into memory, upgraded, and returned as a download — nothing is transmitted to a server, so your character writing stays on your device.

How do I convert a character card to V3?

Upload any supported card — a V1/V2 PNG, JSON, YAML, or an existing CharX — and click Convert to V3. The tool normalizes the persona and writes a chara_card_v3 card object you can download.

What apps use Character Card V3?

RisuAI reads V3 natively through its CharX container, and support is expanding across newer frontends. Exporting to V3 future-proofs your characters.

Does converting to V3 lose any data?

The core persona — name, description, personality, scenario, greeting, and example dialogue — is preserved. V3 simply provides a richer container, so nothing essential is lost in the upgrade.

Is the conversion private?

Yes. It runs entirely in your browser. Your card is never uploaded to a server.