choosing-a-model changedabout-claude/models/choosing-a-model
Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+6added
Lines−6removed
From line
21
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
The whole hunk
from line 21, old and new numbered
/
from line 21
2121
2222### Option 1: Start efficiency-first
2323
24For many applications, starting with a faster, more cost-effective model like Claude Haiku 5.5 can be the optimal approach:
24For many applications, starting with a faster, more cost-effective model such as Claude Haiku 5.5 can be the optimal approach:
2525
261. Begin implementation with Claude Haiku 5.5.
261. Start implementation with Claude Haiku 5.5.
27272. Test your use case thoroughly.
28283. Evaluate if performance meets your requirements.
29294. Upgrade only if necessary for specific capability gaps.
3030
31This approach allows for quick iteration, lower development costs, and is often sufficient for many common applications. This approach is best for:
31This approach allows for quick iteration and lower development costs, and is often sufficient for many common applications. This approach is best for:
3232
3333* Initial prototyping and development
3434* Applications with tight latency requirements
from line 37
3737
3838### Option 2: Start capability-first
3939
40For complex tasks where intelligence and advanced capabilities are paramount, you may want to start capability-first: implement with the strongest starting point for your task, then optimize to more efficient models down the line:
40For complex tasks where intelligence and advanced capabilities are paramount, you might want to start capability-first: implement with the strongest starting point for your task, then optimize to more efficient models later:
4141
42421. Implement with Claude Opus 5.5.
43432. [Optimize your prompts](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-opus-5-5) for this model.
from line 68
6868| The highest available capability | Claude Fable 5.1 | Agent sessions that run for hours, multistep deep research, analysis carried through to a finished document, spreadsheet, or deck |
6969| Complex agentic coding and enterprise work | Claude Opus 5.5 | Multihour autonomous coding agents, large-scale refactoring, complex systems engineering, vision-heavy workflows, computer use |
7070| Speed and capability for everyday coding, agent, and enterprise workloads | Claude Sonnet 5.5 | Code generation, data analysis, content creation, visual understanding, agentic tool use |
71| The lowest latency and price | Claude Haiku 5.5 | Real-time applications, high-volume intelligent processing, cost-sensitive deployments needing strong reasoning, sub-agent tasks |
71| The lowest latency and price | Claude Haiku 5.5 | Real-time applications, high-volume intelligent processing, cost-sensitive deployments needing strong reasoning, subagent tasks |
7272
7373***
7474
from line 76
7676
7777To determine if you need to upgrade or change models, you should:
7878
791. [Create benchmark tests](https://platform.claude.com/docs/en/test-and-evaluate/develop-tests) specific to your use case - having a good evaluation set is the most important step in the process.
791. [Create benchmark tests](https://platform.claude.com/docs/en/test-and-evaluate/develop-tests) specific to your use case. Having a good evaluation set is the most important step in the process.
8080
81812. Test with your actual prompts and data.
8282
No line in this hunk matches that.