Skip to content
AI Companion Tune
Menu

Character JSON will not import: format checks

Troubleshooting

For SpicyChat or OurDream, first check whether the file is valid JSON and actually a character export. If upload is rejected, malformed syntax, the wrong export type or unsupported structure are possibilities—not a confirmed diagnosis. If fields populate but are missing or the character will not save, investigate field mapping and editor constraints instead: SpicyChat explicitly requires manual completion after import. Neither retrieved importer source publishes a complete accepted JSON schema, so a generic “minimum character JSON” would be guesswork. [0, 9] [1] [10]

Checked 2026-10-02 · 13 sources · reviewed before publication

Try these in order

  1. 1. Identify the file and the failure stage

    Suggestion: preserve the original and troubleshoot a duplicate. Record whether the failure happens during upload, after fields populate, or when saving. Confirm that the file is a character export—not a conversation export, standalone lorebook or ordinary image renamed with a .json extension. Both documented import routes accept JSON or PNG, but that does not establish support for arbitrary JSON structures or ordinary PNG images. Record the originating app and export format/version before attempting conversion. [0, 9] [1] [10]

  2. 2. Separate JSON syntax from importer compatibility

    Suggestion: run the local check in the example below. If parsing fails, inspect the reported location for unquoted keys, single quotes used instead of JSON double quotes, trailing commas, unmatched brackets, unescaped quotation marks or literal line breaks inside strings. Remove Markdown code fences if they were accidentally saved with the file. Make syntax corrections only on your copy. If parsing succeeds, stop treating syntax as the confirmed cause: the retrieved provider sources do not publish a complete compatibility checklist. [0, 9] [1] [10]

  3. 3. Use SpicyChat’s documented import control

    For SpicyChat, open Create Chatbot from the main menu. In Avatar, select Import and upload the character .json or character-card .png. Review the populated name, greeting and personality. The guide instructs you to complete tags, visibility and advanced options manually before selecting Save; missing advanced fields therefore do not, by themselves, demonstrate a failed import. A JSON import supplies text data, so upload or generate an avatar separately. A compatible PNG character card includes both image and character data. [0] [1]

  4. 4. Use OurDream’s importer and expect a new picture

    For OurDream, open https://ourdream.ai/character-import. Drag and drop a PNG or JSON, or select Browse Files. The interface says only uploaded metadata is used: uploaded images are not used or stored, and a new display picture is generated at the end of import. A changed portrait is therefore consistent with the documented workflow, not evidence that the source PNG was malformed. The retrieved interface does not provide an accepted schema or a detailed field-mapping specification. [9] [10]

  5. 5. Fix save-time constraints without rewriting the export

    If SpicyChat populated the character but will not save, check its editor constraints: Name is 3–20 characters, with documented characters including letters, numbers, spaces, dashes and underscores; Greeting has a 2,000-character maximum; Personality has a 5,000-character maximum; Tags allows up to 12, and public characters require at least two. Scenario and example dialogue are optional advanced fields. These are editor constraints—not verified upload-parser rejection thresholds. [1, 2, 3, 4, 5]

    The Greeting page both permits “0” and describes the greeting as required. Suggestion: use a short, nonempty greeting while diagnosing a save failure rather than relying on that inconsistent wording. Complete visibility and other manually required options, then select Save. [0, 2] [1] [2] [3] [4] [5] [6]

A lorebook JSON needs a different import route

If your file is a standalone lorebook, use SpicyChat’s separate lorebook workflow rather than its character importer: Create → Lorebook, then upload the lorebook JSON. To attach it, use Character Editor → Advanced → Lorebook → Attach Lorebook → Save. Current documentation allows 5,000 entries, 2,000 characters per entry and one attached lorebook per character. It does not promise that importing a character card automatically imports an embedded lorebook. [6]

Suggestion: keep any separately exported lorebook alongside the original character file until you have checked the destination character. [7]

When validation is not enough

SpicyChat’s import guide states no subscription requirement; that is not proof of access on every account. OurDream’s public importer does not specify tier eligibility. Neither source establishes that paying changes JSON-format compatibility. Suggestion: do not upgrade solely to fix malformed or incompatible JSON. [0, 9]

If local parsing succeeds but upload still fails, collect the destination provider, exact error, source app, export format/version and a redacted structural sample. Remove private text, credentials and identifying details while preserving key names and value types. This is a suggested diagnostic package—not a published provider requirement. Without an accepted schema or the specific error, changing key names or flattening nested objects would be guesswork. [0, 9] [1] [10]

Example to adapt

A cleaner instruction

Suggested copy-ready local check, with Python 3 installed. Put a copy named character-copy.json in the current folder, then run:

python3 -c "import json; from pathlib import Path; p=Path('character-copy.json'); data=json.loads(p.read_text(encoding='utf-8')); print('JSON syntax OK; top-level type:', type(data).__name__)"

If your installation uses the command python instead of python3, substitute that name. A JSONDecodeError identifies a syntax problem and its location. A UnicodeDecodeError means this UTF-8-based local check could not decode the file; it does not establish a provider encoding requirement. Success verifies syntax only, not importer compatibility. Do not use this command’s output as a replacement character export.



If this still does not fix it

No uploads were tested. The supplied public sources do not establish complete accepted JSON schemas, supported card versions, encoding rules or upload-size ceilings for these importers. OurDream’s import quotas and tier eligibility are also unspecified. A locally valid JSON file is not guaranteed to import. [0, 9]

Services with a relevant feature

Shown because the current provider record matches this need. Check the exact plan and limitation before paying.

Ourdream

Checked 2026-10-02

The supplied public-documentation audit supports concrete procedures for PNG/JSON character-card metadata import, message-memory pinning, and prompt-based non-English text-chat switching. It also describes relationship selection during character creation and reserves custom prompting beyond presets for Premium. It does not verify editable stored memory, dedicated pronoun controls, French/Japanese-specific support, or exact Friend/Romantic presets. No imports or chats were tested. Buyers should confirm these unresolved requirements and their plan access before subscribing.

  • Editable or persistent memory
  • Character-card or character import
  • Documented multilingual text support
  • Documented French chat setup

Why it matches: Open the Character Card Importer and drag/drop a PNG or JSON file, or select Browse Files. The importer says only metadata is used: uploaded images are neither used nor stored, and a new display picture is generated at the end. The explanatory article describes parsing the card, detecting gender, filling appearance attributes, and loading it into the builder. Documented compatibility includes PNG SillyTavern V2 (chara), V3 (ccv3), and Ginger; JSON Tavern V2/V3, Faraday V4, Pygmalion/Character.AI exports, Agnaistic, TextGen WebUI, and a generic fallback. The article says imports normalize to CharacterCardV2 and map lorebooks to character_book. These are provider-documented claims, not tested compatibility results. The public importer does not specify tier restrictions, file-size limits, or processing charges; that does not establish free or unlimited importing.

SpicyChat

Checked 2026-10-02

The documentation provides actionable workflows for paid editable memory, JSON/PNG character import and free-text identity/persona context. Lyra V4 documents French and Japanese support at True Supporter or above, but language-menu options, current account availability and language quality remain unverified. Friendship, romance and pronouns can be expressed as written context, not verified dedicated controls. This is a documentation review, not evidence of tested behavior.

  • Editable or persistent memory
  • Character-card or character import
  • Documented French chat setup
  • Documented Japanese chat setup

Why it matches: Import compatible character-data .json or character-card .png files through Create Chatbot → Avatar → Import → upload the file. Import populates name, greeting and personality; complete tags, visibility and advanced options manually, then select Save. JSON requires a separately uploaded or generated avatar, while PNG includes image and description data. The guide specifies no subscription requirement, schema version, import-size limit or comprehensive field-compatibility guarantee. This documents character import, not chat-history migration.

Candy AI

Checked 2026-10-02

The documentation provides actionable French and Japanese chat setup, lists 20 memory slots for Premium Plus, and documents persona customization. Both language procedures require a reset that does not fully preserve long-term conversation memory. Memory editing, external character-card import, dedicated pronoun controls and selectable Friend/Romantic modes remain unverified. The evidence documents setup and entitlement details, not tested recall reliability or language adherence.

  • Editable or persistent memory
  • Character-card or character import
  • Documented French chat setup
  • Documented Japanese chat setup

Why it matches: No official character-card import workflow, accepted formats, compatibility rules or tier entitlement was verified in the retrieved documentation. Documentation of native character creation does not establish external-card import support. Import remains unverified, not necessarily unavailable.

Sources

Checked 2026-10-02

  1. ourdream.ai: Create your own AI Girlfriends
  2. Lorebook | SpicyChat
  3. Premium Features | SpicyChat
  4. Importing Characters | SpicyChat

Provider documentation tells us what a service describes. Unless a page explicitly says otherwise, we are not presenting it as a hands-on performance test.