Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesLowering Claude’s effort setting may reduce usage on routine prompts, but one three-prompt test—not a benchmark—produced the reported 8× difference. Anthropic says lower effort trades some thoroughness and capability for token efficiency, so treat it as a task-by-task choice rather than a guaranteed way to stretch every usage limit.
Which Claude setting can reduce usage?
The setting is effort. Anthropic describes it as a control over how many tokens Claude uses when responding, balancing response thoroughness against token efficiency. It can affect output-token use, including thinking when active and tool calls.
As an Amazon Associate I earn from qualifying purchases.
Anthropic calls Low its most efficient effort level, but also warns that lower effort can reduce capability. Effort is a behavioral signal, not a fixed token allowance: a difficult task may still prompt reasoning at Low, though less than at a higher level. See Anthropic’s effort documentation for current details.
What did the 8× test actually measure?
A How-To Geek author tested three routine prompts: debugging a Linux script, finding time-zone conflicts between meetings, and splitting trip expenses. The author ran them once at Low effort in one chat, then repeated them at High effort in a new chat using the same model. As recounted by WindowsForum on September 23, 2026, the usage meter moved by 1% at Low and 8% at High.
#1 Best Overall
That is an 8:1 ratio between two displayed meter changes in one experiment. The meter was rounded, there were no direct token counts, and each configuration was tested only once. The author reported that both sets of answers were correct, but three routine prompts cannot establish that Low preserves quality on harder tasks or that other users will see the same result.
Does lowering effort make Claude’s usage last longer?
It can help on work that does not need deep analysis, particularly if you can quickly check the answer. Anthropic recommends trying Medium or Low for routine or latency-sensitive tasks after evaluations show that quality holds. A smaller response or less reasoning may use fewer tokens, but the exact effect depends on the model and task.
Rank #2
Do not assume the setting makes every conversation use a predictable fraction of your limit. The 8× figure comes from a rounded meter comparison, not a general measurement of Claude usage, and it does not show that higher effort is never useful.
When should you use Low, Medium, or High?
- Try Low for simple, routine requests with answers you can readily verify, when speed or token efficiency matters.
- Try Medium when routine work needs a little more completeness, or when you want to compare quality and usage before settling on Low.
- Keep High for difficult reasoning, complex coding, long-running agentic work, or situations where an unnoticed mistake could be costly. The available guidance does not establish that lower effort will preserve quality in those cases.
Anthropic’s practical guidance is to start at High for models such as Fable 5.1, then step down for routine work once evaluations show that quality remains acceptable. Your own checks matter: compare outputs on representative tasks rather than deciding from one easy prompt.
Rank #3
Is High the default for every Claude model?
No. Anthropic’s API documentation says most models that support effort default to High, while Claude Opus 5.5 defaults to Medium. Support and defaults vary by model, so check the current documentation for the model you are using instead of assuming there is one universal Claude default.
Anthropic’s guidance is for its API and model configurations; it does not establish a single set of controls or defaults for every Claude interface or plan. If your interface exposes an effort control, use the labels available there and confirm how they apply to your selected model.
Quick Recap
Best Value
Rank #4
How to test whether lower effort works for you
- Choose a few typical, low-risk prompts whose answers you can verify.
- Run the same prompts at the current effort level and at a lower level, keeping the model and other conditions as consistent as possible.
- Compare correctness and completeness as well as usage. Do not rely on a rounded percentage meter alone if precise token counts are unavailable.
- Use the lower setting for the task types where your checks show acceptable results; keep a higher level for work where quality or error detection matters more.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.




