Skip to content
AI Companion Tune
Menu

Import a character JSON into SpicyChat: what to expect

Setup guide

Use SpicyChat's JSON import to transfer a character definition, not as a full conversation migration. It documents automatic population of name, greeting, and personality; missing tags, visibility, or advanced settings must be completed manually. A JSON file also needs a separate avatar, and the guide does not promise chat-history transfer. [1]

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

Start here

A setup you can edit

Use this as a draft, not as a magic prompt. Keep only the details that actually matter to your character.

Suggested copy-ready content for Example dialogue; the placeholder format is documented by SpicyChat. Adapt the identity and relationship to your character rather than treating this as recovered information. [3]

<START>
{{user}}: Who are you, and how do you know me?
{{char}}: I'm Mara, your longtime friend and a research librarian. I speak English in a calm, direct style. Tell me what you want to investigate today.


Build it step by step

01

1. Keep the original JSON available

If you already have the character .json, start with that file; you do not need to repeat an export procedure. Suggested precaution: keep an untouched copy so you can compare the result and recover omitted details. [1]

02

2. Use Create Chatbot → Avatar → Import

In SpicyChat's main menu, select Create Chatbot. Go to the Avatar section, select Import, and upload the character file. Import is located in Avatar even though a JSON file supplies text data rather than the avatar image. [1]

03

3. Verify the transferred character definition

Review name, greeting, and personality—the three fields the import guide says are populated. Suggested check: compare each against the original, especially identity, relationship, speaking style, and opening message. Do not treat successful upload as proof that every source field survived. [1]

04

4. Finish the avatar and opening presentation

Upload or generate an avatar separately when importing JSON. Check or supply the Title too: the import guide does not promise title population. Suggested greeting check: keep the opening from the character's perspective rather than narrating actions or feelings for the user; SpicyChat's creation guidance recommends this approach. [1] [8]

05

5. Set tags and both visibility choices

Complete tags and visibility manually. You can choose up to 12 tags; Public characters require at least 2. Public appears in listings/search, Unlisted is accessible to anyone with the link, and Private is accessible only to its creator. Suggested starting choice: Private while you inspect the result. Separately review definition visibility, which controls whether others can view personality, example dialogue, and scenario—not who can access the character. [1] [2] [3]

06

6. Complete advanced fields, then Save

Review or recreate optional Scenario and Example dialogue rather than assuming they transferred: the import instructions leave advanced options for manual completion. SpicyChat documents {{user}}, {{char}}, and <START> for example dialogue. Use the suggested example below if helpful, then select Save. Suggested final check: start a fresh conversation and compare its identity and opening style with your intended setup; identical behavior is not established by the import documentation. [1] [4]

Missing content or a rejected file

A missing avatar is not evidence that the JSON import failed: SpicyChat describes JSON as text data, while a compatible PNG character card contains both image and character data. An ordinary PNG image is not necessarily a character card.

If the file is rejected or the three promised fields are incomplete, the documentation does not provide enough schema detail to identify a universal repair. Suggested fallback: retain the original file, then manually copy its name, greeting, and personality into the corresponding character fields and review the remaining settings individually. Do not assume that renaming a file or repeatedly uploading it resolves compatibility.

Treat Lorebooks separately. The current Lorebook guide documents a separate .JSON import and attachment through Character Editor → Advanced → Lorebook → Attach Lorebook → Save. One Lorebook can be attached per character; the reviewed guidance says Lorebooks currently work with private characters only. Character import does not promise automatic transfer of an embedded Lorebook. [1] [9]

Definition length and plan expectations

A large imported definition does not create more conversation capacity. SpicyChat says definitions share context with messages and instructions, and recommends roughly 800–1,100 tokens for a concise character setup. That is a writing recommendation, not an import acceptance limit. The definition-limit support article confirms limits exist but supplies no numerical field limits; it recommends a Lorebook for extensive background.

The import instructions state no subscription prerequisite, but that is not an explicit guarantee of identical access on every tier. For subsequent chats, the support plan table lists 4,096 context tokens for both Free and Get A Taste, versus 8,192 for True Supporter. Get A Taste adds Memory Manager without enlarging that documented context window. Do not upgrade merely to compensate for an oversized definition; first decide which details belong in the core personality. [1] [5] [7] [8]

Separate import problems from saving and publishing problems

Successful field import does not establish that the character can be saved or publicly published. For “Something went wrong” when saving, SpicyChat recommends reviewing ambiguous wording and contacting support with the character fields, avatar, and exact error message. For an avatar-upload error, its support guidance lists dimensions exceeding 1,000 pixels on either side among possible causes; that is not a JSON-import limit.

Public characters undergo review, and Private or Unlisted visibility does not exempt a character from moderation. Import capability also does not grant permission to publish another user's character or description as your own. [3] [11] [12] [13] [14]

Keep this limitation in mind

SpicyChat does not document a supported JSON schema/version list, file-size ceiling, field-by-field conversion specification, or truncation rules. Complete, lossless transfer of arbitrary character JSON—and migration of existing conversations—cannot be promised. This guide describes the documented workflow, not a tested import. [0]

Next step

Build your setup

Where this setup may fit

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

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.

Lovescape

Checked 2026-10-02

The supplied public documentation supports conversational memory correction, last-response regeneration, general relationship-type configuration, and character-profile editing. Friend and Romantic partner roles are documented, but their exact selectors and behavior are not. Memory is documented on all plans, while free character creation has subscription-dependent character counts; neither establishes equal performance or role-specific entitlements. Buyers needing a dedicated memory editor, character-card import, French/Japanese text-chat setup, or pronoun controls should treat those requirements as unverified, not proven unavailable. This is a documentation review, not a hands-on test.

  • Editable or persistent memory
  • User persona / profile controls
  • Friendship / platonic relationship setting
  • Romantic relationship setting

Why it matches: Character-card import is not verified: no import procedure, upload control, supported card formats, or field mapping is documented in the supplied evidence. The comparison discusses an inability to export Lovescape character cards, but an export restriction does not establish whether import is available. No import plan or format requirements can be determined.

Sources

Checked 2026-10-02

  1. Plans and what's included : SpicyChat
  2. Why there's a character limit on the definition fields : SpicyChat
  3. Creating a character : SpicyChat
  4. Lorebook | SpicyChat
  5. How review and approval works : SpicyChat
  6. "Something went wrong" when saving a character : SpicyChat
  7. "Something went wrong" when uploading an avatar : SpicyChat
  8. What isn't allowed — the short version : SpicyChat
  9. 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.