Stop sending & wait
Stop sending messages and wait a few minutes. A 429 is a temporary rate limit, so pausing lets it reset.
ChatGPT errors, explained
The "too many requests" message — HTTP error 429 — means you've sent too many messages in a short time and hit a rate limit. It's a temporary throttle, not a ban, and it almost always clears on its own once you slow down and wait. This independent guide explains why it happens, how to fix it on the web, app and API — and how to keep working while the limit resets.
Why it happens
A 429 is the system temporarily throttling you because requests came in too fast. These are the usual triggers and what to do about each.
| Trigger | Whose side | What to do |
|---|---|---|
| Sending messages too quickly | Rate limit | Slow your pace and wait a few minutes before sending again. |
| Multiple tabs/devices on one account | Rate limit | Close extra ChatGPT tabs, windows and devices — they share the same limit. |
| Rapid retrying after an error | Rate limit | Stop retrying. Rapid retries can extend the throttle instead of clearing it. |
| Heavy API / automated usage | Rate limit | Reduce request frequency and use exponential backoff. Check OpenAI's API docs. |
Step by step
Work through these in order. The first few clear most web and app rate limits; the last covers the API.
Stop sending messages and wait a few minutes. A 429 is a temporary rate limit, so pausing lets it reset.
Send messages more slowly and avoid rapid-fire retries, which can extend the limit instead of clearing it.
Close other ChatGPT tabs, windows and devices signed in to the same account — they all count toward the same limit.
After waiting, refresh or start a new conversation and send a single message to check whether the limit has reset.
If you hit 429 on the API, reduce request frequency and implement exponential backoff so retries wait progressively longer.
While the limit resets, switch to another model in MultipleChat and keep going instead of waiting.
Related guides: all error codes · at capacity / 503 · something went wrong · is ChatGPT down?
Don't just sit there
A 429 throttle is temporary, but you don't have to wait it out doing nothing. A multi-model workspace lets you switch to another AI and finish what you were doing, then go back to ChatGPT once the limit clears.
When ChatGPT hits a 429 limit, switch to Claude, Gemini or another model in the same place and keep going for free — no waiting for the throttle to reset. Compare answers across models too.
OfficialThe first place to check: live incidents, outages and maintenance.
OfficialOpenAI's own troubleshooting and rate-limit articles.
Guide400, 401, 403, 429, 500, 502, 503, 1020.
All error guides
FAQ
Short answers on why the rate limit happens, how long it lasts, and how to fix it. Verify current limits on OpenAI's official pages.
A 429 "too many requests" error means you hit a rate limit by sending too many messages in a short time. It's a temporary throttle, not a ban. Wait a few minutes, slow down, and avoid rapid retries, and it usually clears on its own.
Common causes include sending messages too quickly, having several ChatGPT tabs or devices open on the same account at once, rapid retrying after an error, or heavy automated/API usage. All of these count toward the same rate limit, so the system temporarily throttles you with a 429.
Stop sending and wait a few minutes, slow your pace, and close extra ChatGPT tabs or devices on the same account. Then refresh or start a new chat and send a single message to test. Avoid rapid retries, which can extend the limit. On the API, reduce request frequency and use exponential backoff.
It's usually short — a temporary throttle that resets after you stop and wait. The exact duration isn't published and can vary, so the practical advice is to pause for a few minutes, stop retrying, and try again. Rapid retries can keep the limit active longer.
It can. Hammering retry on a 429 keeps sending requests that count toward the limit, which can extend the throttle rather than clear it. The better approach is to wait, slow down, and on the API use exponential backoff so each retry waits progressively longer.
Send messages at a reasonable pace, keep to one active ChatGPT tab where possible, don't run multiple devices hammering the same account, and avoid rapid retries after an error. On the API, design your client to respect rate limits with backoff and reduced frequency.
On the API, a 429 typically means you've exceeded a rate limit for your account or key. Reduce your request frequency and implement exponential backoff so retries wait progressively longer. Check OpenAI's help and API documentation for the current limits and recommended handling.
No. A 429 is a temporary rate limit, not a ban. It clears after you stop and wait. If you can't access your account at all even after the standard fixes, that's a different issue — contact OpenAI support.
Use a multi-model workspace like MultipleChat: while ChatGPT's 429 limit resets, switch to Claude, Gemini or another model and keep going for free instead of waiting. It also lets you compare answers across models.