Claude's Usage Limits Are Doubled Until March 27 — Here's How to Actually Use It
Anthropic has temporarily doubled usage limits across all Claude tiers through March 27. This window is real. Here's how to extract maximum value from it.
As of March 13, Anthropic has temporarily doubled usage limits across all Claude subscription tiers — including the free tier — through March 27 (Friday). The promotion applies to Claude Code, Cowork, and the Claude API. Enterprise accounts and weekly limits are excluded.
Two weeks. That’s the window.
What’s Actually Different
The normal Claude usage limits are the primary friction point for heavy users. The free tier caps quickly. Pro subscribers hit walls during intensive coding sessions. With limits doubled, the ceiling effectively moves up for everything: how many turns you can run in an agentic session before hitting a pause, how deeply you can explore a codebase in Claude Code, how many API calls a test application can make.
This isn’t marketing. It’s a measurable change in what you can attempt before the system asks you to wait.
Three Ways to Make This Count
1. Run the projects you’ve been deferring
If you’ve been holding back on testing a complex agentic workflow because you didn’t want to burn through your monthly limit, the next 11 days are when you do that. Specifically:
- Multi-file refactors on a real codebase, not a toy project
- Full end-to-end feature implementation, from spec to tested code
- Long context analysis (upload your entire codebase config, ask Claude to find architecture inconsistencies)
These are the sessions that teach you where the model’s judgment actually holds versus where it needs your intervention. You can’t learn that from small experiments.
2. Build the internal tool you’ve been procrastinating
The doubled API limits make it cost-effective to prototype internal tooling that would normally eat into monthly allocation too fast for comfortable iteration. Dashboard that pulls from three data sources. Slack bot with decent context retention. Custom code review script for your team’s conventions.
The value here isn’t the prototype itself — it’s the iteration. Multiple versions in quick succession is how you find where the abstraction breaks.
3. Test Claude Code’s Code Review on your actual PRs
If you’re on Teams or Enterprise, this period is also when Code Review is in research preview. Running it against your real open PRs now — while limits are doubled — gives you twice as many test cases before the promotion ends. The calibration pass (comparing AI findings against what your team already reviewed) is more valuable with more data points.
What Not to Do
Don’t burn the doubled limits on tasks you’d normally rate-limit yourself on for good reason. Running 500 near-identical document summaries to test throughput tells you throughput numbers but teaches you nothing about how to use the tool better.
The doubled limit is an invitation to attempt sessions with higher cognitive depth per session — not to run more shallow sessions faster.
The Catch
Enterprise accounts are excluded, and weekly limits aren’t affected. If you’re on an enterprise contract, this doesn’t apply to you. If you’re a Pro user who’s been hitting the weekly cap rather than the monthly cap, the doubling doesn’t move that ceiling.
Also: the promotion ends March 27. After that, limits return to normal. Plan accordingly — if you’re mid-project on March 27, the session that was running fine may suddenly need to pause.
Why Anthropic Is Doing This
The promotional timing — two weeks, all tiers — is almost certainly a user acquisition and engagement play. Getting free-tier users to experience what Pro usage feels like is a known conversion mechanism. Getting Pro users to run larger sessions builds the usage patterns that drive enterprise conversations.
None of that changes whether the window is useful to you. The doubled limits are real. Use them.
Source: TechRadar — Claude has temporarily doubled usage limits for everyone