“The site is read-only because it’s full” SharePoint Error

The “The site is read-only because it’s full” error appears in SharePoint Online or Microsoft Teams when a specific site collection breaches its designated storage limit. When this limit is exceeded, Microsoft 365 locks all document modifications, folder creations, and synchronization tasks to protect database records from fragmentation. Users are instantly blocked from saving edits to cloud spreadsheets, processing local changes through OneDrive, or adding new items to libraries until the data ceiling is manually adjusted or storage overhead is dropped.

Fast-Fix: The 45-Second Solution

This error indicates that a SharePoint site collection has completely exhausted its assigned storage quota or the global organization pool has run dry. Classed as a Major Risk issue that stops all team data writes, the primary reset step requires an IT administrator to expand the site’s storage allocation within the central SharePoint Admin Center or run a permanent purge on the site’s multi-stage recycle bins.

Diagnostic Snapshot

• Severity Tier: High / Major (Completely blocks write access, document updates, and metadata changes across the entire site library)
• Data Safety Risk: Low (Existing documents remain safe and fully readable; however, un-synced local changes face deletion or conflict risks if forced over the client)
• Common Cause: Rigid, manual site storage quota limits or massive accumulations within hidden second-stage recycle bins
• Admin Requirement: SharePoint Administrator or Global Administrator privileges to alter storage thresholds or reallocate tenant data pools

Condition: Low Risk vs. High Risk

• Low Risk Scenario: The storage block affects a single site collection that has been manually capped by IT, while the overarching organization tenant still possesses ample unallocated space. The issue can be resolved in under two minutes by updating the site’s ceiling.
• High Risk Scenario: The global Microsoft 365 tenant storage pool is entirely empty (0 bytes remaining for the whole organization). This configuration completely stops data ingestion across multiple sites and requires corporate storage license purchases or massive, automated archival routines to restore basic corporate operations.

The System Break (What This Means)

Think of a SharePoint site collection like a commercial storage locker with a strict physical doorway layout. When items are crammed all the way to the ceiling, the door cannot be latched shut, and the facility manager hooks a heavy padlock onto the unit until some of the inventory is cleaned out.

On a technical level, SharePoint enforces a rigid byte-count boundary across the SQL database partitions housing your documents. When a save or sync request arrives from the OneDrive app or a web browser, the server compares the incoming payload size against the remaining site quota. If the payload pushes the total size over the allocated cap, the server flags the database schema as Read-Only. The server denies all write permissions to maintain database health, rejecting file updates and forcing local synchronization engines into an endless loop of retry errors.

Root Cause Probability

• Likely (60%): The site collection has crossed an explicit storage ceiling set manually by an IT administrator (for example, capping a project site at 500 GB when active files and hidden version histories reach 500.1 GB).
• Possible (30%): Large folders or video files were recently deleted by users, but they are still counting against the active site storage quota because they are trapped in either the First-Stage (User) or Second-Stage (Site Collection) Recycle Bins.
• Rare (10%): Backend provisioning delays or licensing synchronization drops between the global Microsoft 365 billing engine and individual site collections.

Conflict Escalators

• Document Version Sprawl: Keeping a 500-version retention limit on large files causes a single 50 MB document to silently consume 25 GB of storage space over its lifecycle, accelerating quota depletion without user knowledge.
• Teams Meeting Recordings: High-definition video recordings from Microsoft Teams calls dump massive multi-gigabyte MP4 files straight into the site’s underlying channel folders, occasionally filling up a small library in a single afternoon.
• Local Sync Engine Overloads: When the OneDrive desktop client encounters a read-only site state, it keeps trying to push its backlog across the network. This continuous cycle consumes local CPU cycles and risks corrupting local workspace caches.

Progression: 1 Hour → 24 Hours → 1 Week

• 1 Hour: Desktop Office applications display yellow warning banners stating that changes cannot be saved to the cloud. OneDrive sync icons turn red, and files sit stuck in the local outbound queue.
• 24 Hours: Co-authoring and real-time document collaboration break down entirely. Because the server cannot save delta changes to the central database, users are forced to lock documents or check them out individually.
• 1 Week: Team members begin saving fragmented, independent copies of documents to local hard drives to keep working. This creates massive data drift and requires tedious manual document merging once storage capacity is restored.

Common Misdiagnoses

• Confused with Permission Drops: Users often assume they have been stripped of editing permissions or that their access tokens have expired. This leads to time wasted on logging out, clearing browser caches, or re-assigning user roles.
• Mistaken for Missing Data Tags: Users sometimes confuse a global read-only lock with individual file save rejections caused by empty required properties. You can differentiate this from individual property holds Resolving SharePoint “Missing Metadata” preventing File Upload because a storage lock stops every single file block from processing regardless of its metadata state.
• Misidentified as Client Cache Failures: Wiping local OneDrive cache databases or reinstalling the application will not bypass this error. The block resides entirely on the cloud server.

Immediate Action Steps

If you are a site member or owner trying to clear immediate space, perform these steps before escalating to IT:

1. Analyze the Storage Footprint: Navigate to the blocked SharePoint site, select the Gear icon (Settings) in the upper right corner, and click Site information > View all site settings. Under the Site Administration heading, click Storage Metrics to pinpoint which library or folder is consuming the quota.
2. Empty the First-Stage Recycle Bin: Click Recycle Bin in the left navigation pane. If you have recently deleted massive directories, select them and click Delete to push them out of the user view.
3. Clear the Second-Stage Recycle Bin: Scroll to the absolute bottom of the main Recycle Bin screen and click the Second-stage recycle bin link. Items stored here still count directly against your site collection’s total gigabyte ceiling. Select these items and click Delete to permanently clear them from the server database.
4. Pause Local Synchronization App: To prevent your desktop computer from overheating due to constant upload retries, click your taskbar OneDrive icon, select the Gear icon > Pause syncing, and select 2 hours until storage limits are reconfigured.

Hard-Stop Red Flags

• Global Administrative Alert: If the SharePoint central admin dashboard reads “0 KB free out of [X] TB” on the main landing metrics bar, the organization’s entire global allocation pool is empty.
• Preservation Hold Library Locks: If files cannot be emptied from the second-stage recycle bin, a legal hold or compliance retention rule is active. This prevents data destruction and requires an administrator to alter compliance settings before storage can be reclaimed.

What the IT Admin Will Check

If the site remains locked after emptying the recycle bins, a SharePoint or Global Administrator must alter allocation thresholds using these exact steps:

1. Log into the central Microsoft 365 Admin Center (admin.microsoft.com) or go straight to the SharePoint Admin Center (admin.sharepoint.com).
2. On the left-hand navigation menu, expand Sites and select Active sites.
3. Locate and select the affected site collection from the database list to open its properties drawer.
4. Navigate to the General tab, scroll to the Storage limit section, and click Edit.
5. If storage configuration is toggled to Manual, type a larger value in the gigabyte (GB) box to increase the threshold, then click Save. If it is set to Automatic, it means the entire corporate tenant pool is maxed out and requires global data archiving or an add-on storage license purchase from Microsoft.

Resolution Complexity

• Major: While the configuration change inside the admin center takes less than two minutes to execute, it strictly mandates top-tier SharePoint Administrator or Global Administrator credentials. End-users and basic site owners cannot scale their own storage boundaries.

Related Error Escalators

• If your site storage issues are caused by hitting deep file index boundaries rather than raw gigabyte limits, refer to Troubleshooting “Syncing a Library that contains a lot of files”.
• If clearing storage limits drops the read-only flag but leaves files stuck in an unyielding checked-out state, consult How to Fix SharePoint “Checkout Required” Sync Blockers.

Ticket Closed

To recover from a full-site read-only lock, focus entirely on backend storage allocation rather than local software troubleshooting. The absolute fastest fix is to have an IT administrator increase the site collection’s manual storage cap via the SharePoint Admin Center. Once the new gigabyte quota commits to the database, the server will drop the read-only state instantly, allowing all pending local OneDrive sync queues to clear naturally and resume regular operation.