Import and export troubleshooting

When a card breaks, follow the next fix.

Start with the symptom: JSON errors, a PNG with only an avatar, a blank first message, or a Lorebook that does not trigger.

What you get

Each issue follows “What happened → What to do next”. Client prompt templates and field support can differ, so recheck after fixing.

JSON will not importSee fix
What happened

The file is not valid JSON, or quotes and newlines were damaged during editing.

What to do next

Export V2 JSON again; keep explanatory text outside the code block.

PNG has only an avatarSee fix
What happened

Compression or re-encoding may have removed embedded card metadata.

What to do next

Use the original PNG, or keep a JSON backup from the same export.

First message is blankSee fix
What happened

The chosen client has no opening message to display.

What to do next

Fill in first_mes in the workspace and run the export check again.

Lorebook does not triggerSee fix
What happened

The test text does not contain a keyword, or the entry is disabled.

What to do next

Check keywords, case settings, and the enabled state.

Clients behave differentlySee fix
What happened

Prompt templates, field precedence, and extension support can vary by client.

What to do next

Inspect imported fields, then verify again with the target client template.

Next step

Return to the character-card workspace to edit real fields, run checks, and export.

Open the inspector