Google Workspace Storage Limit Per User, by Plan

When a Google Workspace user tells you their mailbox is full, your first instinct is probably to find their storage limit and raise it. That is the right move — but the mechanics are not what most admins expect, especially if they are coming from a background where each user had a fixed, isolated quota. Workspace storage does not work that way, and misunderstanding the model leads to fixes that do not actually fix anything.

This guide explains how the google workspace storage limit per user actually operates: the pooled model shared across all editions, how allocations differ between Business Starter, Standard, Plus, and Enterprise, and what an admin can do when one mailbox is consuming space that everyone else needs. Storage figures change with packaging, so this post describes the architecture and links to Google's own documentation for current numbers rather than quoting reseller-blog figures that may be months out of date.

The short answer: Workspace storage is pooled, not per user#

Google Workspace uses a pooled storage model. Rather than assigning a fixed, isolated quota to each individual user, an edition gives your organization a single shared storage pool. That pool is split across every Gmail inbox, every Google Drive account, and every Google Photos account on your domain — all drawing from the same total.

This design has a genuine advantage. A team with wide variation in usage — one executive who archives everything for 10 years alongside a junior hire who barely sends mail — can share capacity without an admin manually re-slicing per-seat allocations. Heavy users draw more from the pool; light users draw less. The pool adjusts automatically.

The downside is equally real. One user uploading hundreds of gigabytes to Drive, or letting archived Gmail accumulate for years, can eat into storage that other users need for their inboxes. When the pool fills, everyone on the domain is affected — even users who individually consume very little.

Within the pool, admins can set individual storage limits per user. If you set no caps, users collectively consume up to the pool's ceiling and the pool distributes automatically. If you set a per-user cap, that cap becomes the ceiling for that user regardless of how much pool space remains. The cap reserves headroom for other accounts — it does not create new storage.

This distinction is the single most important thing to understand before you start diagnosing a quota complaint. A user can be over their individual cap while the domain pool still has space. The domain pool can be nearly full while most users individually look fine. You need to know both states to understand what is actually wrong.

Before you start: three numbers to find first#

Before touching any settings, get three pieces of information. Each one defines a different constraint, and without all three you risk applying a fix to the wrong layer of the problem.

First, your edition. Business Starter, Standard, Plus, Enterprise Starter, and Enterprise Standard or Plus each provide a different pool ceiling. The ceiling goes up meaningfully at each tier. Google updates these figures periodically; the current numbers are on the Google Workspace plans page at workspace.google.com, not in this post.

Second, your current pool usage. An organization with a large pool and light users has room to maneuver. An organization approaching the pool ceiling has essentially no flexibility until someone deletes data or you purchase additional storage. Check this before anything else, because per-user caps cannot fix a full pool — they only prevent further concentration. You cannot allocate what does not exist.

Third, whether any per-user limits are already set. Admin-set caps often get configured during an early tightening exercise and then forgotten. A user complaining about a full mailbox may be hitting a 10 GB cap you set three years ago, not the domain pool ceiling. The fix is very different in each case.

• Super admin access, or an admin role with Reports and Storage management privileges
• Your edition name — visible in Billing in the admin console
• Domain pool total and current usage — Reports > Highlights or Reports > Storage
• Any existing per-user caps — Directory > Users > select user > Storage section

How to view and manage Workspace storage in the admin console#

The steps below reflect the admin console layout as of August 2026. Google periodically restructures navigation, so use these labels as a guide and follow any on-screen prompts if the path has changed.

1. 1

   Sign in to the Google Admin console

   Go to admin.google.com and sign in with a super admin account, or an account that has been granted the Storage management admin privilege. Without this privilege, you can view some storage reports but cannot set per-user limits or purchase additional storage.

2. 2

   Check domain-wide pool usage

   From the main menu, navigate to Reports > Highlights. The storage card shows your total pool size and current consumption. For a service-level breakdown across Gmail, Drive, and Photos, go to Reports > Storage. This is your first diagnostic. If the pool is at or near its ceiling, adjusting per-user caps will not create more headroom — you need to free data or purchase additional storage before caps can help.

3. 3

   Identify the top storage consumers

   Still in Reports > Storage, you can sort by consumption to see which users and which services are drawing the most from the pool. In most organizations, a small number of accounts are responsible for a large share of total usage. Identify them before making any changes — targeted cleanup on the top five accounts often recovers more space than across-the-board cap adjustments.

4. 4

   Check an individual user's storage status

   Go to Directory > Users, find the user, and open their profile. The Storage section shows how much storage they have consumed and what their current individual limit is. If an admin-set limit is shown, the user is hitting that cap. If no limit is shown, the user's ceiling is determined by the domain pool. This tells you immediately whether the fix is raising their cap or addressing the pool itself.

5. 5

   Set or adjust a per-user storage limit

   From the user's profile page, click Edit in the Storage section and enter a cap in GB. The value you enter becomes that user's ceiling — they cannot exceed it even when pool space is available. Setting a cap does not add storage to the pool; it reserves capacity for other users by constraining this one. Limits take effect within a few minutes. A whole-number GB value is required.

6. 6

   Give a user immediate relief if they are over quota

   A user who has hit their limit can receive new email but cannot send and cannot upload new Drive files. Temporarily raise their individual cap to restore sending access while you work with them on cleanup. Then have them permanently delete large attachments, empty Trash, and move archival files off Drive. Note that permanently deleted Trash items can take up to 30 days to release back to the pool.

7. 7

   Purchase additional storage or upgrade the edition

   If cleanup does not recover enough headroom, additional pooled storage is available for most Business editions from the Billing section of the admin console. Upgrading the edition also increases the pool ceiling. Enterprise editions have separate procurement mechanics — work through your Google Workspace reseller or contact Google Workspace sales directly.

Google Workspace storage by edition#

The table below shows how storage is structured across editions. Specific gigabyte figures change with packaging updates and are not quoted here — verify current amounts on the Google Workspace plans page before any purchasing decision. The table uses relative indicators that describe the relationship between tiers; these relationships are stable even when absolute numbers change.

What to do when storage is nearly full or a user is over quota#

Running out of domain storage follows a predictable pattern: one or two power users accumulate years of archived mail and large Drive files; Trash builds up across accounts because permanent deletion requires deliberate action; shared drives fill with video files no one has reviewed in months. Before purchasing more storage, run through these steps. Cleanup almost always recovers meaningful space, and the space you recover is cheaper than new storage you might not need.

1. 1

   Sort users by storage consumption

   In Reports > Storage, sort by consumption descending. In most Workspace environments, five to ten accounts account for the majority of pool usage. Focus cleanup efforts on these accounts before making any domain-wide changes. A targeted approach almost always recovers more space with less disruption than blanket caps applied to everyone.

2. 2

   Clear accumulated Trash

   Items in Trash count against storage until permanently deleted. Users who deleted large files months ago may have gigabytes sitting in Trash that they have forgotten about. Ask heavy consumers to permanently empty their Trash (Gmail: Settings > See all settings > Storage > Empty Trash; Drive: Trash > Empty Trash). Admins can also use the Reports console to identify accounts with large Trash holdings.

3. 3

   Audit shared drives for large or redundant files

   Shared Drive files count against the domain pool, not any individual user. Old project folders, video archives, and duplicate files are common culprits. Work with team leads to identify and either archive externally or permanently delete large shared drive contents. Storage released from shared drives returns to the domain pool.

4. 4

   Set per-user caps once you have created headroom

   Once cleanup has freed space, set per-user caps to prevent one account from consuming the entire pool again. A reasonable starting cap is roughly 1.5 to 2 times the average consumption across active users — enough headroom for normal variation, tight enough to contain outliers. Review caps every six to twelve months as team size and usage patterns change.

5. 5

   Purchase additional storage if cleanup is not enough

   If cleanup does not create sufficient headroom, additional pooled storage is purchasable for most Business editions from the Billing section of the admin console. Upgrading to a higher edition also increases the pool. For Enterprise editions, contact your reseller or Google Workspace support for the appropriate add-on path.

A faster way to keep mailboxes from filling up#

The steps above fix a storage problem once it has appeared. The reason most admin consoles stay in reactive mode is that mailboxes accumulate quietly: newsletters pile up, large attachments sit unread in threads, and users only delete when Gmail blocks their next send.

AI Emaily is an AI-native email client that triages every message as it arrives — filing low-signal mail automatically, surfacing what actually needs a response, and helping users stay close to inbox zero as a habit rather than a quarterly cleanup task. Users with an active triage workflow accumulate less unread, storage-heavy mail and tend to delete what they do not need rather than archiving it indefinitely. AI Emaily works alongside your existing Google Workspace setup over standard protocols — it does not replace the admin console, and it does not touch the domain storage pool directly.

We build AI Emaily. It connects to Gmail and other providers without requiring a migration. There is a 7-day free trial (no permanent free plan), and full plan details are at aiemaily.com/pricing. If your storage problem is partly behavioral — users who do not clean up because the inbox feels overwhelming — that is the exact shape of problem the product is built around. Learn more at aiemaily.com.