Claude Pro Image Upload Not Working? The Undocumented Peak-Hour Limit Explained

• Claude Pro subscribers can hit image upload blocks even with Extra Usage enabled and funds loaded — this is not a bug
• On March 26, 2026, Anthropic officially confirmed it had deliberately increased session consumption rates during peak hours (5–11 AM PT on weekdays)
• Image upload restrictions may operate on a separate layer from session usage — Extra Usage did not resolve the block in my case
• Anthropic has not published detailed specifications for this image upload limit; there is currently no user-side way to disable it
• The most reliable workaround is avoiding peak hours; batch size and fresh chat sessions may also help

Paid plan. Extra Usage on. Funds loaded. Still couldn’t upload.

On the evening of April 20, 2026, I tried to upload a few photos of my dinner and gym session to Claude — something I do every day as part of a health tracking habit I moved over from ChatGPT. This time, the uploads failed.

There was no clear error message. The photos simply wouldn’t go through. I assumed it was a connection issue and tried again. Still nothing. When I tried sending five or six images together, only two were accepted. After that, not a single one would upload.

I’m on Claude Pro. I have Extra Usage enabled, with a positive balance in my account. By any reasonable reading of Anthropic’s plan descriptions, I should have had headroom to spare. And yet: no uploads.

What made this especially puzzling is that my session usage in the hours before this happened was minimal. I had done some heavier work in the morning, used Claude briefly around midday, and then hadn’t touched it for three to four hours before dinner. This wasn’t a case of burning through my session quota. Something else was triggering the block.

This isn’t isolated — and Anthropic has acknowledged part of it

Reports of unexpected Claude usage limits surged across Reddit and X starting in late March 2026. The trigger was a policy change Anthropic made on March 26.

Thariq Shihipar, a member of Anthropic’s technical team, posted on X confirming that the company had deliberately adjusted its five-hour session limits during peak demand hours. The change affects weekdays between 5:00–11:00 AM Pacific Time — meaning users burn through their session budget faster during those windows, even though overall weekly limits remain unchanged (The Register, March 26, 2026).

According to Shihipar, approximately 7% of users would start hitting limits they hadn’t hit before, with Pro subscribers being the most affected group. Max 20x users ($200/month) see a much smaller impact — around 2% — which means the squeeze falls disproportionately on the $20/month tier (PiunikaWeb, March 27, 2026).

Worth noting: this was announced not through an official blog post or help center update, but through a social media thread by an individual engineer. Multiple outlets flagged this as a transparency issue (TechRadar, March 2026). The underlying cause is straightforward: user growth outpaced GPU capacity. Claude hit the top of the US App Store for the first time in March 2026, with traffic jumping over 30% month-on-month.

How Claude Pro usage limits actually work

To make sense of what happened to me, it helps to separate out the different types of limits Claude applies.

First, there are the hard file upload caps documented in Anthropic’s official help center (Uploading files to Claude):

Files uploaded to a Project’s Files section are not subject to the 20-file conversation cap, though total content must fit within the context window.

Second, there are session consumption rate limits. Claude measures usage in tokens, not message count, across a rolling five-hour window. Images and PDFs consume tokens heavily. Longer conversations also cost more per message, since Claude re-reads the entire history on each turn. Plan-level differences look roughly like this:

Usage is shared across claude.ai, Claude Code, and Claude Desktop, so running multiple surfaces simultaneously accelerates consumption.

The part Anthropic hasn’t documented: a possible separate image upload limit

Here is where my experience diverges from the standard explanation.

My session usage in the hours before the block was negligible. The typical explanation — that I burned through my session quota — doesn’t fit. And critically, I had Extra Usage enabled with a positive balance, and the image uploads still failed.

Anthropic’s official Extra Usage documentation (Manage extra usage for paid Claude plans) describes the feature as allowing users to “continue using Claude seamlessly after reaching their included usage limits” at standard API rates. That framing suggests it addresses session consumption overruns. Whether it also covers image upload restrictions is not stated anywhere in the documentation.

A technical breakdown of Claude Code rate limits (published by SitePoint, March 2026) describes how RPM (requests per minute) and TPM (tokens per minute) constraints operate as entirely independent layers from the daily/session quota — meaning “a developer can be at 6% daily usage and simultaneously at 100% of their TPM allocation.” That analysis is aimed at Claude Code, but the underlying architecture likely applies to claude.ai’s chat interface as well.

My working hypothesis: image uploads — particularly sending multiple images in rapid succession — may trigger a burst-rate limit that is separate from both the session quota and the Extra Usage overflow mechanism. Anthropic has not published specifications for this, and I cannot confirm it definitively. But it would explain why Extra Usage didn’t help.

To summarize what I believe is happening, there appear to be at least two distinct limit types in play:

• Session consumption rate limit: Token-based, rolling five-hour window, accelerated during peak hours. Extra Usage addresses this layer.
• Image upload burst limit (likely): May operate independently of session usage. Extra Usage did not resolve this in my case. Specifications are not publicly documented.

What “paid plan” actually means in 2026

The experience prompted me to reconsider what a Claude Pro subscription actually guarantees. The answer, based on both Anthropic’s own documentation and the March 2026 policy change, is: more headroom than the free tier, subject to dynamic adjustments based on time of day, demand, and limits that aren’t fully disclosed.

That’s a meaningful shift from how flat-rate subscriptions usually work. Anthropic’s own help center acknowledges that usage “can vary with demand” and that “some features can consume capacity faster than ordinary chatting” — but stops well short of explaining what those features are or how they interact with Extra Usage.

The infrastructure context is real. Anthropic’s annualized revenue reached an estimated $19 billion by March 2026, but inference costs scale with every user and every message. When demand growth outpaces GPU provisioning, something has to give. Anthropic chose to tighten limits rather than degrade response quality — arguably the right call, but one that creates a confusing experience for paying users who have no visibility into why their uploads are being blocked (J.D. Hodges, March 2026).

What you can and can’t do

There is currently no user-side way to disable peak-hour restrictions, and Extra Usage does not appear to cover image upload blocks (at least in my experience). That said, a few practical approaches can reduce how often you hit the wall.

⏰ Avoid peak hours

The most reliable option. The timeline below shows when peak hours fall in your local time. Shifting image-heavy work outside the red zone — mornings or weekends — makes a meaningful difference. Weekends are not subject to peak-hour restrictions.

📸 Send fewer images per message

Rather than uploading five or six images at once, try sending one or two at a time. In my experience, two images were accepted before the block kicked in, which suggests there may be a per-burst threshold. This is speculative — I haven’t been able to confirm a specific number — but it’s a low-cost adjustment worth trying.

💬 Start a new chat

Longer conversations cost more per message because Claude re-reads the full history each turn. Starting fresh when you change topics keeps session consumption lower, which may reduce the chance of hitting limits overall. Whether this affects image upload restrictions specifically is unclear, but it’s good practice regardless.

📩 Contact Anthropic support

The image upload limit is not documented in detail anywhere I could find. If you’re hitting blocks with Extra Usage enabled and a positive balance, it’s worth raising with Anthropic support directly. I plan to do this and will update this post if I get a clearer answer.

Frequently asked questions

Bottom line

If Claude Pro is blocking your image uploads despite an active subscription, Extra Usage enabled, and funds in your account, you’re not imagining it and it’s not a bug — at least not in the conventional sense. The March 2026 peak-hour policy is real and officially acknowledged. The image upload layer on top of that is less clear, but my experience suggests it exists and operates independently of the session quota system.

The honest answer to “why is this happening to a paying user” is: Anthropic’s infrastructure is under strain, the limits are intentional, and the details aren’t fully disclosed. The most reliable thing you can do right now is shift image-heavy tasks outside peak hours. I’ll update this post if Anthropic support provides a clearer explanation.

Sources

1. Anthropic Help Center, “Uploading files to Claude“
2. Anthropic Help Center, “Manage extra usage for paid Claude plans“
3. The Register, “Anthropic tweaks Claude usage limits to manage capacity” (March 26, 2026)
4. TechRadar, “Claude is limiting usage more aggressively during peak hours” (March 2026)
5. PiunikaWeb, “Anthropic finally explains why Claude usage limits feel tighter for some users” (March 27, 2026)
6. SitePoint, “Claude Code Rate Limits Explained 2026” (March 2026)
7. J.D. Hodges, “Claude AI Usage Limits: What Changed in 2026” (March 2026)

AI tools were used in parts of the research and drafting process for this article. Information reflects sources available as of April 2026 and is subject to change. I do my best to ensure accuracy, but I cannot guarantee completeness — please verify details at official sources before making decisions based on this content.

Please follow and like us:

Hiroshi

Hiroshi is a Tokyo-based project manager specialising in international operations within the global MedTech company. Originally from Hokkaido, he holds a postgraduate degree in international relations — including study periods in the United States and Sweden — and has lived and worked across Malaysia, Switzerland, China, and the Philippines.
Beyond his industry career, he served as Manager for the 23rd World Scout Jamboree in 2015, where he managed liaison with delegations from over 150 countries, coordinated with the World Organisation of the Scout Movement (WOSM), and led on-site risk response. He has also contributed to disaster relief efforts following the Great East Japan Earthquake and other natural disasters across Japan.
This blog covers travel, productivity, technology, and global careers — written as a way of thinking through ideas and consolidating what he learns along the way.