Skip to the content
I Want AI To
17 builds on showA website

Claude Code usage limits: what a first-time site builder will actually hit

On a paid plan, Claude Code has a session limit that resets every five hours and weekly limits, shared with the Claude app. One small website is unlikely to use them up. Long chats, big pastes and repeated rebuilds will.

Short answer: the limits measure how you work more than what you are building. Everything below comes from Anthropic’s help pages as they read at the time of writing (14 October 2026). Plans and limits change, so check the pages in the sources if you are reading this much later.

The short answer: two limits, one resets every five hours

Paid plans have two kinds of usage limit:

  • A session limit that resets every five hours.
  • Weekly limits that reset once a week. On Max plans there is also a separate weekly limit for Fable models.

Pro and Max both include Claude Code, and the help pages say both limits are shared across Claude and Claude Code. Chatting in the Claude app, Claude Desktop and Claude Code all draw from the same allowance. If you spent the morning asking Claude to rewrite your About text in the app, that comes out of the same pot your build uses.

Most first-timers only ever meet the session limit. The weekly one tends to bite only after several heavy days in a row.

What counts toward your usage (and why a long chat costs more than a short one)

The best-practices page lists what affects your usage: message length, file attachment size, how long the current conversation is, tool use, the model you choose, the effort level, and multi-step tasks such as creating files or running code.

Conversation length is the easiest one to miss. The Claude Code help page explains that every turn sends three things to the model: the whole conversation so far, the project context (including any files Claude has read), and your new message. It says the conversation “grows the fastest”. By message forty, every reply also carries messages one to thirty-nine, even if all you typed was “make the button blue”.

The model matters too. The same page says Sonnet is right for most coding work, and that Opus “uses meaningfully more of your quota”. Building a simple site is routine work. Type /model to see which model you are on.

What happens when you run out

You get warning messages as you approach a limit. The Pro and Max page lists your options once you reach it:

  • Wait for the reset. After a session limit that means hours, not days.
  • Turn on usage credits, so you can keep working past the limit on credits.
  • Upgrade your plan. The limits page says the new plan’s limits apply straight away.

The Claude Code commands reference also describes a /rate-limit-options menu. It can wait and carry on automatically when the limit resets.

Hitting a limit does not touch your work. Your files stay in your folder, and nothing you have already put live goes offline.

There is a different kind of “full” that people often confuse with this one. The context window is how much Claude can hold in mind in a single conversation. When it fills up, the help page says to run /compact (which summarises the conversation so you can carry on) or /clear (which starts a new conversation). Claude Code also compacts on its own when you get close, so you will rarely hit a hard wall there.

Three beginner habits that burn the allowance, and the fix for each

Habit one: one enormous conversation. It goes well, so you keep going. The homepage, then the contact page, then the colours, then a gallery, all in one thread. Each new message carries everything before it.

The fix: when you finish one part of the site and move to the next, run /clear. The help page calls it “the single most effective lever” for both quality and cost. Your files stay put; only the chat history goes. Its test is a good one: if your next request would make sense in a brand new session, clear before you send it. /clear cannot be undone, so copy out anything from the chat you still want first.

Habit two: huge pastes. Beginners tend to paste in everything: the whole brief, all the text from the old website, a stack of screenshots. The help page warns that anything you paste “sits in context, in full, for the rest of the session”.

The fix: point at the file instead. “Look at the contact section in index.html” lets Claude read just the part it needs. If you have a long block of text, save it as a file in your site folder and mention its name.

Habit three: a full rebuild after every tweak. You nudge the heading size, then ask Claude to redo the whole page “with that change”. That makes it rewrite everything for a one-line fix.

The fix: ask for a small change as a small change, and say what to leave alone: “Make the main heading larger. Don’t change anything else.” For anything bigger, ask for a plan first. The help page suggests asking it to list the files it will touch and what it will do in each before it changes anything. A wrong plan is cheap to correct. A wrong rewrite costs you twice.

The best practices post covers more working habits for a first build.

How to check where you are before you start a big change

There are three places to look:

  • /usage in Claude Code. The commands reference says it shows “plan usage limits” and, on Pro, Max, Team or Enterprise, a breakdown of what counts against them. You can run it even while Claude is still replying.
  • Settings > Usage on claude.ai. Progress bars show how much of your five-hour session and weekly limits you have used, and how long the current session has left.
  • The context indicator in Claude Code. It shows how full the current conversation is. If it is nearly full, run /clear or /compact before you start the next big task.

It takes seconds to check. If you are near the session limit, it makes sense to do small fixes now and leave the big change until after the reset.

Is one website likely to hit the limit?

One small site on its own is unlikely to be the problem. We can’t give you an official figure for how much a site uses, because the help pages don’t publish one, and we won’t make one up.

What you can look at is our recorded runs. The build pages for a simple website, a landing page and a blog show each prompt we ran, in order, and what came back. It is a useful reality check on how much asking a first site really takes.

When a first-timer hits the limit, it is usually because of the conversation that ran for hours, the giant paste or the repeated rebuild. Rarely the site itself.

When the limit is a sign to change plan, and when it is not

If you hit the limit once, after a long, rambling session, fix your habits first: clear between tasks, point at files and ask for small changes.

If you work tidily and still hit it regularly, that is the case the Pro and Max page describes, and its advice is to consider a bigger plan or usage credits. The money side has its own post: how much Claude Code costs for a first website. If you have not set anything up yet, start here.

Questions

Questions people ask.

How many times can I use Claude Code?

There is no fixed number of messages. Paid plans have a session limit that resets every five hours and weekly limits that reset once a week. How fast you use them depends on message length, attachments, how long the conversation is, tool use, the model you pick and the effort level. Higher plans get bigger allowances.

What is the 5 hour limit on Claude?

It is the session limit on paid plans. It resets every five hours. It is shared between Claude Code and the Claude apps, so chatting in claude.ai uses the same allowance. Settings > Usage on claude.ai shows how much of the current session you have used and how long is left.

What happens if Claude Code runs out of usage?

You get warnings as you get close to a limit. Once you hit it, you can wait for the reset, turn on usage credits so you can keep working, or upgrade your plan. Your files stay where they are. Running out of context window is a separate thing: /compact or /clear sorts that out.

How do I avoid Claude Code usage limits?

Run /clear when you start a new task. Point Claude at a file instead of pasting it in. Ask for small changes as small changes, and ask for a plan before anything big. Use Sonnet for routine work, because Opus uses noticeably more of your allowance.

How do I see how much usage I have left?

Type /usage in Claude Code. On a Pro, Max, Team or Enterprise plan it shows your plan usage limits and what counts against them. Settings > Usage on claude.ai shows progress bars for your five-hour session and your weekly limits.