Gmail IMAP Bandwidth Limit Exceeded: Limits and How to Fix

The short answer
The Gmail IMAP bandwidth limit exceeded error means an account pulled more data over IMAP than Google allows in a day. Google's Workspace help lists 2,500 MB of IMAP downloads per day and says the limits can change without notice. Stop every mail client, wait, then reconnect with a shorter sync range and without All Mail.
Gmail IMAP limits: Google lists 2,500 MB of downloads a day. See what triggers the bandwidth error, how long it lasts and how to resume sync.
On this page
- 01What the Gmail IMAP bandwidth limit error means
- 02Gmail IMAP limits at a glance
- 03Steps to get sync moving again
- 04What causes the limit to trip
- 05Automated access, scripts and backup tools
- 06Too many simultaneous connections on Gmail
- 07How limits differ across clients and use cases
- 08If it does not clear after a day
- 09Avoiding the limit entirely with the Gmail API
The full message usually reads "Account exceeded command or bandwidth limits", or, in some clients, "Account has exceeded the Gmail bandwidth limit for downloads via IMAP". Either way it means Gmail is throttling IMAP for that account because a client, a migration tool or a backup job pulled too much, too fast. Quick answers first:
- The limit: Google lists 2,500 MB of IMAP downloads and 500 MB of IMAP uploads per account per day, and says the limits may change without notice.
- The wait: Google says a suspension for hitting a bandwidth limit typically lasts about an hour and can last up to 24 hours. Plan on a day to be safe.
- The fix: stop every IMAP client first, then reconnect with a shorter sync range and without the All Mail folder.
What the Gmail IMAP bandwidth limit error means#
Gmail counts how much message data your IMAP clients download and upload for the account in a day: headers, bodies and attachments, across every client at once. Cross the daily cap and Gmail throttles or rejects IMAP connections until the limit resets. The error most often appears when you first add a large Gmail account to a desktop client, run a migration tool, or point backup software at an old archive.
Two other messages get mixed up with it. "Too many simultaneous connections" is a connection cap, not a download cap (covered below). And some clients show a generic authentication or "Session expired, please login again" error while the account is throttled, which can look like a broken password even though IMAP is working. The imapsync author also describes Gmail slowing transfers to a very low rate, under 1 KiB per second, when its throttle kicks in.
Google does not document which counter an individual error string belongs to. Some user threads argue that "Account exceeded command or bandwidth limits" can also be triggered by the sheer number of commands a client sends, not only by bytes. The advice is the same either way: stop the traffic, wait, and make the next sync smaller and quieter.
Google Workspace and personal Gmail
Gmail IMAP limits at a glance#
These are the figures Google publishes. Google says they "may change without notice", so check the source before you build a migration plan around them.
| Action | Published daily cap | Notes |
|---|---|---|
| IMAP download | 2,500 MB per day | The cap behind the bandwidth limit exceeded error. Counts all IMAP clients on the account together |
| IMAP upload | 500 MB per day | Reaching the IMAP sync limit temporarily stops IMAP uploads for the account |
| POP download | 1,250 MB per day | Separate from IMAP, but the same account |
| Web client download | 1,250 MB per day (750 MB per hour) | Gmail in a browser has its own, lower caps |
| Simultaneous clients | Up to 15 clients per account | Gmail Help says you can add Gmail to up to 15 email clients at a time. Over that you see "Too many simultaneous connections" |
Steps to get sync moving again#
Work through these in order. The first step matters most: stop the traffic that hit the limit before you do anything else.
- 1
Stop the downloading client
Close the mail client, pause the migration tool or disable the backup job that triggered the error. A client that keeps retrying while the account is throttled does not clear the limit, and a tight retry loop keeps adding traffic.
- 2
Wait for the limit to reset
Google's help page says a suspension for exceeding a bandwidth limit typically lasts about an hour and can last up to 24 hours, after which the account works again. User reports mostly describe about a day. Google does not publish a longer lockout, so if it lasts well beyond a day, treat that as a different problem. A new app password or removing and re-adding the account does not help: the limit is on the account, not the credential.
- 3
Check that IMAP is still enabled
A throttled account can make a client show a generic sign-in error. In Gmail on the web, open Settings, then See all settings, then Forwarding and POP/IMAP, and confirm IMAP access is on. If it already is, leave it: switching it off and on does not clear a throttle.
- 4
Shrink the sync before reconnecting
In the client's account settings, limit how much mail it downloads to the last 30 or 90 days, and unsubscribe from large folders such as All Mail. Gmail's All Mail folder holds a copy of every message, so a client that syncs it as well as your labels downloads much of the mailbox twice. Gmail Help also offers a folder size setting, Limit IMAP folders to contain no more than this many messages, which can help with slow or crashing downloads.
- 5
Reconnect with a rate limit in place
Once the account is working again, reconnect. For migration tools, turn on their bandwidth limits first. imapsync, for example, documents --maxbytespersecond (its Gmail FAQ suggests 300,000 with --maxbytesafter 3,000,000,000) and the --gmail1 and --gmail2 shortcuts, which apply values the author found to work in practice. For backup software, look for a download rate or concurrent-connection setting. Let the first sync finish at the reduced scope before widening it.
What causes the limit to trip#
The cap is aimed at bulk downloads, not normal daily reading. Most accounts never get near it. The error almost always follows one of these.
| Cause | Why it tips the limit | Relative risk |
|---|---|---|
| First sync of a large mailbox | Many desktop clients fetch the whole mailbox on first connect unless you limit the date range, pulling headers, bodies and attachments for years of mail | High |
| Email migration tool | A tool such as imapsync downloads the full archive to move it elsewhere, and it can go as fast as the connection allows unless you set a limit | Very high |
| Several clients syncing at once | Adding the same account to a laptop, a desktop and a backup tool at once stacks parallel full syncs against one shared daily cap | High |
| Backup or archiving software | Archive tools are built to pull everything, and many run without a download limit by default | High |
| Aggressive polling or scripts | A client or script that checks mail every few seconds issues repeated commands, which can trip the command limits even when little data moves | Medium |
| Shared mailbox on many clients | A mailbox used by a team means several clients each hold connections open and sync on their own | Medium |
Automated access, scripts and backup tools#
If the account is used by a script, a backup agent or an integration, the same IMAP caps apply to it as to a person's mail client, and it is usually the first thing to blow through them. Give automated jobs a download rate limit, run them from one place rather than several, and keep their first run small.
If you control the code, consider the Gmail API instead of IMAP for automation. It has its own quotas rather than the IMAP daily byte caps, which is a different set of trade-offs. Gmail API vs IMAP quotas compares them.
Too many simultaneous connections on Gmail#
This one is about how many clients are connected at the same moment, not how much they download. Gmail Help says you can add Gmail to up to 15 email clients at a time per account, and shows "Too many simultaneous connections" when many clients are fetching at once. Its fix is to close or sign out of some of them.
The count is of connections, not of devices. Some clients open several connections each, for example to watch more than one folder, so a phone, a laptop and a desktop app can add up faster than you expect. Google does not publish a single per-client connection number, so count your open clients, close the ones you do not need, and reduce the folders each one watches.
How limits differ across clients and use cases#
The same account behaves differently depending on how each client or tool approaches its first sync. Knowing your client's default lets you stay under the cap instead of finding it.

| Client or tool type | Typical first sync | Limit risk | How to cut it down |
|---|---|---|---|
| Desktop mail clients (Outlook, Apple Mail, Thunderbird) | Often the whole mailbox unless you limit it | High | Choose which folders sync and set a date range if the client offers one |
| Migration tools (imapsync, MigrationWiz) | Full archive | Very high | Use the tool's bandwidth and size limits. Flags vary by tool |
| Backup and archive software | Full archive on the first run, then incremental | High on first run | Download rate and concurrent-connection settings in the tool |
| Other third-party email clients | Varies by client | Medium to high | Limit sync to the last N days in account setup if offered |
If it does not clear after a day#
Work through these checks before you escalate.
- Confirm the client or tool is really stopped. A background service or scheduled task under a different process name may still be connecting. Check your operating system's process list and network activity.
- Count every device. If the account is on a phone, a tablet, a laptop and a desktop, all syncing on their own, together they can keep the account over its limit. Disconnect all but one while it clears.
- Check for All Mail in the client's folder subscriptions and unsubscribe from it before reconnecting.
- On Google Workspace, ask your domain admin. Admins can see suspended accounts and their reset time in the Admin console and, in some cases, reset a suspension.
- If the error persists well beyond a day and none of the above applies, contact Google: the Help Center for personal accounts, the admin support channels for Workspace.
A new app password does not bypass the throttle
Avoiding the limit entirely with the Gmail API#
The limit exists because IMAP gives a naive client no easy way to download only what changed. The practical workaround is a shorter sync window set before you connect, which is easy to miss in first-time setup.
We build AI Emaily, an AI-native email client that connects Gmail through the Gmail API with OAuth, not IMAP. Its first sync covers about the last 60 days and then only new mail, so a first connect does not download your full history over IMAP. The Gmail API has its own, separate quotas. Other providers, such as iCloud, Yahoo and Fastmail, do connect to AI Emaily over IMAP. If a previous client tripped the limit, there is a 7-day free trial on Pro or Autopilot.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.