From Chub to RisuAI, without the bounce.
RisuAI is V3-native and happiest with .charx — a ZIP container holding the card JSON plus its assets. Chub hands you a V2 PNG. Feeding that PNG straight to Risu sometimes works, but a surprising share of hub cards bounce or import half-empty. Converting to .charx first upgrades the card to V3 and packages the avatar as a proper asset, which is the path Risu expects.
Convert a card
Drop in a card and download. Everything runs locally in your browser — nothing is uploaded.
PNG, JSON, or .charx. Converted entirely in your browser — the file never leaves your device.
Importing to a hub (RisuRealm / Chub)? .charx or V2 PNG are accepted most widely. A bare V3 JSON has no embedded avatar, so some hubs reject it.
Conversion notes
Pick a card and a target format, then convert. Any fields that don't survive are listed here so you can review them before downloading.
The route
Download the card from Chub
You'll get a V2 PNG with the card data in its metadata.
Drop it below and pick .charx
.charx is preselected on this page. The V2 → V3 upgrade is lossless; the report shows what's assumed.
Import the .charx into RisuAI
Use Risu's character import. The avatar arrives as the card's icon asset — no separate image step.
Migrating your whole library off Chub? Convert cards one by one and spot-check the change report — hub cards vary wildly in how well-formed their metadata is.
Questions
- Why .charx instead of just importing the PNG?
- PNG carries one image and one metadata blob. .charx is RisuAI's native V3 container: card JSON plus a real assets folder. Cards with lorebooks and extra fields survive the trip far more reliably.
- Does the lorebook carry over?
- Yes — character_book is converted to the V3 shape (groups, decorators preserved where present) and included in the container. The change report lists anything that had to be assumed.