Choosing a roleplay AI
Looking for the best AI for long-form roleplay?
Bring your characters with you.
A card that reads well on message one isn't the hard part — staying coherent three hundred messages later is. LoreChat imports your existing card in seconds, then leans on a running story summary, pinned moments, memory notes and a story director that plans beats and a twist, so a long story doesn't quietly forget itself.
What people look for in a long roleplay
Every roleplay chat is good for the first ten messages — the card is fresh, the model has the whole conversation in view, and nothing has had a chance to drift. The differences show up later: whether a promise made forty messages ago still holds, whether the plot is going anywhere, and whether the model still remembers who's in the room.
That's a memory and structure problem more than a model problem, and it's why the comparison below is about what LoreChat actually keeps track of, not about which model answers faster.
- Wanting the story to remember facts established hours ago, not just the last few messages
- Wanting specific moments — a promise, a reveal, a name — pinned so they can't fall out of context
- Wanting a plot with actual shape: rising tension and a twist, not a flat conversation
- Wanting to see and edit what the chat remembers, via free-form memory notes
- Wanting scenes illustrated as the story develops, anchored to a consistent character look
What LoreChat actually does
| Feature | LoreChat |
|---|---|
| Character cards | Import PNG or JSON, Character Card V1, V2 and V3, including the embedded lorebook. |
| Lorebooks | Full `character_book` support — keys, secondary keys, scan depth, token budget, constant and selective entries. |
| Story structure | A story director drafts a premise, 4–8 beats with rising tension, and a twist held back until its moment. |
| Running summary | Updated every few replies so the story keeps track of what's happened, well past what fits in a visible history window. |
| Pinned moments | Up to 12 messages per chat pinned so they stay in the prompt even after they'd otherwise fall out of range. |
| Memory notes | A free-form, editable note the chat always carries — for facts you want remembered exactly, in your own words. |
| Personas | Set who "you" are per chat, separate from the character. |
| Illustrated scenes | The current moment is drawn automatically every few replies, or on demand, in a consistent style anchored to the card. |
| Access & pricing | No install, no API key. Free daily credits on every account, with Story Spark top-ups if you want more. |
| Content policy | Fiction only, fade-to-black: romance, tension and mature themes are welcome; explicit sexual content is blocked in chats, cards, shares and illustrations. Sexual content involving minors, non-consent, real people, or anything illegal is never allowed. Full list at /content-policy. |
How to migrate
Bring an existing card
- Find the card file — PNG or JSON, V1 through V3 — for the character you want to use
- Create a free LoreChat account
- Open /characters/import, drag the file in, and check the parsed fields
- Save the card and start a chat with the story director on
Starting from scratch
- Open /characters/new
- Write a concrete scenario — it's what the story director plans beats from, so specifics beat mood
- Add a first message that leaves the reader something to answer
- Save, then start chatting — pin the moments you don't want the story to lose
FAQ
What actually keeps a long roleplay coherent?
Not just a longer context window. LoreChat keeps a running story summary that updates every few replies, lets you pin up to 12 specific moments so they never fall out of the prompt, and carries a free-form memory notes field you can edit directly. The story director also tracks which beat the plot is in, so the story keeps moving rather than looping.
What does the story director do, exactly?
When a chat starts, it drafts a premise, 4 to 8 beats with rising tension, and a twist that stays hidden until its beat. As the chat grows it updates a running summary and steers each reply toward the current beat. It can be turned off per chat if you'd rather freewheel.
Do I need to write a huge character card for it to stay in character?
No — a bloated card actually crowds out the conversation itself. Put lasting facts in the lorebook, established facts in memory notes, and let pinned moments and the running summary carry the rest.
Do I need an API key?
No. LoreChat runs in the browser and the models are provided by the service.
Is there a content filter? Will my NSFW cards work?
There is a published content policy, and no: NSFW cards are rejected at import. LoreChat is fiction only and fade-to-black — romance, attraction, kissing, implied intimacy, mature themes and fictional violence are allowed; explicit sexual description is blocked in your messages, in replies, in cards, in shares and in illustrations. A card that contains explicit content, is labelled NSFW by its source, or instructs the model to write explicit scenes is refused at import; when the explicit content sits in one field, the refusal names that field. The full list is at /content-policy.