If you want Claude to write character dialogue, use Claude Sonnet 5.5 for most scenes and switch to Claude Opus 5.5 for the handful of conversations the book turns on: the confession, the breakup that isn't quite a breakup, the interrogation where nobody says what they know. Haiku 5.5 is fine for brainstorming lines you'll rewrite anyway. Fable 5.2 is Anthropic's most expensive model, but it's pitched at hard technical work, and for dialogue it's hard to justify paying double what Opus costs.
The model matters less than people think, though. Every Claude model has a house voice: articulate, warm, complete sentences, each speaker answering the question that was actually asked. Put three characters in a room and you get three polite versions of Claude. The fix is the same on every tier, and most of this guide is about that fix. Pick the model first, then spend your effort on the prompt.
Which Claude model is best for fiction dialogue?
Here's the current lineup as of mid-November 2026, with Anthropic's API prices per million tokens and how I'd use each one for dialogue. All four have a 1M-token context window and can write up to 128K tokens in one go, so context size is no longer a reason to pick one over another.
- Claude Sonnet 5.5 ($2 in / $10 out). The default for drafting. It keeps speakers apart well when you give it voice notes, follows "don't" instructions reliably, and it's fast enough that you'll actually regenerate a weak exchange instead of settling for it.
- Claude Opus 5.5 ($4 in / $20 out). Better at subtext. When the point of a scene is what a character refuses to say, Opus is more likely to let the silence do the work instead of having someone explain their feelings two lines later.
- Claude Haiku 5.5 (from $0.10 in / $0.50 out). Cheap enough to ask for twenty versions of one line. Its dialogue flattens faster than Sonnet's, so treat it as a brainstorm partner, not a drafter.
- Claude Fable 5.2 ($8 in / $40 out). Released November 9 and aimed at coding, finance and science. It writes good dialogue, but so does Opus at half the cost.
To put the prices in real terms: Claude's current tokenizer works out to roughly 1.8 tokens per English word. A 3,000-word scene with 20,000 words of story context costs about 13 cents on Sonnet 5.5 and about 25 cents on Opus 5.5, before any thinking tokens. That gap is small for one scene and large for a whole novel, which is why I'd save Opus for the scenes where a reader would notice. If you're weighing Claude against GPT or Gemini rather than choosing within Claude, the full comparison of AI models for fiction covers the other families.
One note for API users: Sonnet 5.5 defaults to high effort and Opus 5.5 defaults to medium. If Opus dialogue feels rushed or generic, raise its effort before you decide Sonnet is "better." In the Claude app you just pick the model from the menu.
Why do all of Claude's characters sound the same?
Because you described them instead of showing them. "Marcus is gruff and distrustful" gives the model an adjective, and Claude turns adjectives into its own voice with a slight frown. A gruff Claude character still speaks in full, grammatical sentences and still answers every question directly.
There's a quick way to see it. Take a dialogue-heavy scene Claude wrote for you, delete every name, tag and action beat, and read it cold. If you can't tell who's talking, the voices have collapsed into one. Writers on r/WritingWithAI have been running this "strip the tags" test for a while, and it almost always fails in the same places: arguments and emotional beats, where the model's instinct to sound reasonable is strongest.
The other cause is drift. You can spend an evening tuning a character's clipped, abrasive cadence, and twenty messages later the model has smoothed her into a polite office worker. Long chats bury your early instructions. The cure is to stop relying on the chat's memory and hand the voice notes back every single time that character appears. If your characters also all sound like they went to the same university, this fix for AI characters who all sound educated deals with vocabulary specifically.
How to build a voice sheet Claude will actually follow
A voice sheet is a short block per character, six or seven lines at most, that you paste above the scene request. Anthropic's own prompting docs say examples are one of the most reliable ways to steer Claude's tone, and that's exactly what this is. Keep it short. A long sheet gets averaged; a short one gets copied.
- Two or three real lines the character would say, from a situation unlike the scene you're writing. Claude copies the rhythm, not the content, so a line about ordering coffee can teach it how she'll talk at a funeral.
- One or two speech habits. Sentence length, contractions or none, answering questions with questions, a filler word nobody else uses. Stop at two. With more, Claude starts repeating the tics every other line and the character becomes a parody.
- How they dodge. What does this person do when asked something they don't want to answer? Change the subject, make a joke, go quiet, get pedantic about a detail? This one line does more for arguments than anything else on the sheet.
- What they want in this scene. Someone who wants to leave gives short answers. Someone who wants forgiveness over-explains. Claude can't infer that from a personality sketch.
- One thing they never say. A word, a phrase, an admission. Claude respects negative instructions well, so use them.
Build the sheet from lines you wrote yourself, not from lines Claude already polished. Otherwise the sheet just describes Claude's voice back to it. For regional speech and personal word choice, the guide on building a character's dialect and idiolect goes deeper, and if you're keeping all this in a larger reference document, a story bible models actually follow shows how to format it so the voice notes don't get lost among the worldbuilding.
Prompts that get distinct voices out of Claude
Here's the drafting prompt I use with Sonnet 5.5. The voice sheets go above it, and the scene brief goes where the brackets would be, except I write it out in full every time.
Write the kitchen argument between Dana and Theo from the scene brief above, about 900 words. Use the voice sheets exactly. Dana talks in short declaratives and never apologizes. Theo hedges, over-explains, and answers questions with questions. Neither of them says what they're actually angry about: the missed funeral. Nobody gives a speech longer than three sentences. At least two of Theo's questions go unanswered. Keep dialogue tags to "said" and use them only where the speaker would otherwise be unclear. No narration explaining what anyone feels.This works because every instruction is something Claude can check its own draft against: sentence shape, a banned topic, a length cap, unanswered questions. "Make the dialogue feel tense" gives it nothing to check.
When a scene is already drafted and two voices are blurring, don't ask for a full rewrite. That gives the house voice another turn at every line. Run a blind test instead.
Below are two voice sheets, then a scene with every name, dialogue tag and action beat removed. For each line, tell me who you think said it and how confident you are (high, medium or low). List every line that could plausibly belong to either character. Do not rewrite anything yet.It works because it turns a vague feeling ("they sound alike") into a short list of specific lines, and it keeps Claude from touching the lines that already work. The model's guess isn't proof, so trust your ear if you disagree with it.
Then fix only what failed:
Rewrite only the lines you flagged as low or medium confidence so each one matches its speaker's voice sheet. Leave every high-confidence line exactly as written. Show each change as the old line, then the new line, with one sentence on what you changed and why.Asking for old and new side by side stops Claude from quietly polishing everything else in the scene, which it will do if you hand back a clean copy. For scenes with four or five speakers, the same method scales, but writing group scenes with distinct voices covers the extra traffic-control problems.
Where Claude's dialogue still goes wrong
Even with good voice sheets, Claude has a few habits you'll want to watch for. None of them are deal-breakers. They're just predictable, which means you can plan for them.
- Beats and adverbs around every line. Claude loves "she said quietly, setting down her mug." You can ban it in the prompt, but I find it cheaper to trim these in revision than to fight them in every request.
- The tidy resolution. Left alone, Claude wants arguments to end in understanding. If the scene should end unresolved, say so explicitly: "The scene ends with neither of them conceding."
- Explaining the subtext. Sonnet in particular will sometimes write a perfect loaded exchange and then add a paragraph of narration telling you what it meant. Cut the paragraph, or switch that scene to Opus. The guide on prompting for subtext-heavy dialogue has more ways to keep the meaning under the surface.
- Everyone is a good listener. Real people interrupt, mishear, and answer the question they wish you'd asked. Claude's characters tend to respond precisely to the last line spoken. A single instruction like "Theo answers the question before last, not the last one" breaks that pattern fast.
- Softening sharp characters over time. This is drift again. If a deliberately rude character is getting nicer by chapter twelve, the voice sheet isn't going back in with each scene.
Keeping voices consistent across a whole book
A 1M-token context window means you can keep a lot of the manuscript in view, and that helps with continuity of facts. It doesn't fix voice drift on its own. Claude reading forty chapters of its own dialogue mostly learns to sound more like itself.
What works better over a long project is a simple routine:
- Keep each character's voice sheet in one place and paste the same version every time. If you change it, change it there.
- Start a fresh chat, or a fresh request, for each scene instead of running a novel through one endless conversation.
- Every few chapters, run the blind attribution test on the most dialogue-heavy scene. It takes five minutes and catches drift before it spreads.
- Before revision, do one dedicated voice pass across the manuscript. The voice consistency edit for AI-drafted novels lays out how to run it chapter by chapter.
I'd also split the work by model on a long book: Sonnet 5.5 drafts every scene, Opus 5.5 redrafts the five or six conversations the plot hinges on, and Haiku 5.5 handles throwaway jobs like "give me fifteen ways a bartender could brush off this question." More craft techniques for building people who talk like themselves are collected under character development guides.
The short version
For character dialogue, draft with Claude Sonnet 5.5, save Opus 5.5 for the scenes where subtext carries the plot, and don't pay for Fable. Then put your effort where it actually changes the output: a six-line voice sheet per character built from your own lines, pasted in with every scene, and a blind attribution test whenever two voices start to blur. If you only try one thing from this guide, take your last Claude scene, strip out every name and tag, and see whether you can still tell who's talking. Whatever fails that test is where you start.
