Fix: “No storage limit” but gets “Storage Full” errors

Seeing a “Storage Full” or “Storage limit reached” error when your Google Workspace account or Organizational Unit (OU) is explicitly configured with “No storage limit” can be deeply confusing. This condition occurs because Google Workspace transitioned from legacy individual unlimited plans to an institutional pooled storage architecture. Setting an OU to “No storage limit” only removes the local user-level restriction; it does not grant infinite space if the domain-wide storage pool is exhausted.

Quick Answer

The “No storage limit” setting only prevents local caps—it does not provide infinite space. If your organization’s total pooled storage is exhausted, all users without local caps are blocked. To resolve this, a Super Admin must open the Google Admin Console, go to Storage, and either purchase Workspace Additional Storage or delete unneeded domain data.


Cause 1: Domain Pooled Storage Is Exhausted

In modern Google Workspace plans (Business Starter, Standard, Plus, Enterprise, and Education), storage is shared across the entire tenant:

  • Every paid license adds a fixed amount of storage (e.g., 2 TB per Business Standard user) to a single shared pool.
  • In the Admin Console under Storage > User storage limit, administrators can toggle an Organizational Unit to No limit.
  • The Conflict: “No limit” simply means that the user is not restricted to an arbitrary ceiling like 20 GB or 50 GB. However, every byte that user uploads still pulls directly from the organization’s master pool. If the organization has 100 TB of pooled storage and the total usage across all accounts hits 100.1 TB, every user assigned “No limit” will immediately receive a “Storage Full” error.

How to Verify:

  1. Have a Super Admin log in to the Google Admin Console.
  2. Go to Storage.
  3. Look at the primary meter: Storage used.
  4. If the master meter is at or above capacity, the domain pool is empty. Individual “No limit” rules cannot override this physical ceiling.

To add capacity to the domain pool, administrators must purchase add-on storage. See “Buy Storage” button missing in Workspace accounts for instructions. If mass deletions were recently performed but the pool has not updated, consult Why Google Workspace Pooled Storage isn’t updating.


Cause 2: The End of Legacy “Unlimited” Editions

Many organizations previously subscribed to legacy plans like G Suite Business or older Workspace Enterprise tiers that advertised “Unlimited Storage.”

Google has completely phased out legacy unlimited models:

  • Accounts were migrated to pooled allocations (such as Enterprise Standard, which provides 5 TB pooled per user, expandable upon request).
  • If your organization recently transitioned to pooled storage and previously had users with tens of terabytes of data, your domain may now be in a severe deficit.
  • Google provides a grace period, but once that period expires, upload blocks are applied globally.

Cause 3: Shared Drive Item Count Limits (The 400,000 Cap)

If the “Storage Full” error appears only when uploading or moving files into a specific Google Shared Drive, the issue is often an item limit rather than a gigabyte limit:

  • A Google Shared Drive can hold a maximum of 400,000 items (including files, folders, and shortcuts).
  • When a Shared Drive approaches or hits 400,000 items, Google Drive blocks new uploads and creates misleading “Storage Full” or “Quota Exceeded” errors, even if the shared pool has dozens of terabytes of free space remaining.

If you suspect an item cap breach, follow the diagnostic steps in Resolving “Item limit reached” in Google Shared Drives.


Cause 4: Local Hard Drive Exhaustion (Drive for Desktop)

If you use Google Drive for Desktop on Windows or macOS, a notification saying “Storage is full” or “Disk full” often points to your physical computer hardware rather than your cloud account.

  1. Drive for Desktop uses local disk space to stage uploads and store its virtual file cache.
  2. If your cloud account has “No storage limit,” but your local computer’s SSD has only 500 MB of free physical space remaining, Drive for Desktop cannot write cache blocks to disk and will halt synchronization.
  3. This creates the illusion that your Google Drive cloud account is full.

To confirm and resolve local disk errors, check How to Resolve “Disk Full” Errors with Plenty of Space and Why deleting files in Drive for Desktop doesn’t free local space.


Step-by-Step Resolution Matrix

Follow this troubleshooting path to isolate the cause:

StepLocationWhat to CheckAction Required
1Admin Console > StorageTotal Domain Pooled BarIf full, buy storage add-on packs or delete domain data.
2Target Shared DriveItem Count (via Drive settings)If > 400,000 items, split data into multiple Shared Drives.
3Local PC / MacLocal Hard Drive Free SpaceIf local disk is below 5 GB, clear local temp files and cache.
4User Personal Quotadrive.google.com/drive/quotaCheck if an admin applied an OU limit override.