Library Threshold Warning Appears Below 5000 Items: Root Cause and Fix

You see a warning that says a SharePoint library is approaching the list view threshold, but the item count is well below 5,000. This warning can appear even when a library contains only a few hundred items. The root cause is not the total item count but how SharePoint calculates the threshold based on metadata and folder structure. This article explains why the warning triggers on small libraries and provides the steps to eliminate the warning.

Why the Threshold Warning Appears Below 5,000 Items

SharePoint has a list view threshold of 5,000 items for standard queries. The warning does not check the total number of items in the library. Instead, it checks how many items a single query must scan. When a library contains more than 5,000 items, SharePoint blocks the query to protect server performance. But the warning can also appear when a library has fewer than 5,000 items if the query scans more than 5,000 rows in the content database.

This happens because SharePoint stores metadata and version history in separate tables. A query that includes all versions or complex metadata can scan more than 5,000 rows even if the library shows only a few hundred files. The most common triggers are:

• Folder-specific permissions. Each folder with unique permissions creates additional rows in the security table. A library with 200 folders, each with unique permissions, can exceed the threshold during a query that checks permissions.
• Missing column indexes. A view that sorts or filters by a column without an index forces a full table scan. If the library has 3,000 items but the column is not indexed, the query may scan all rows plus version history rows, exceeding 5,000.
• Document library thumbnail view. This feature generates thumbnails for images and videos. The background process queries the library repeatedly and can trigger the warning on libraries with fewer than 5,000 items.
• Large metadata or version history. A library with 1,000 items but 10 versions per item stores 10,000 version rows. A query that includes version history scans 10,000 rows.

The warning message says: “This list is large. List view threshold is exceeded by the number of items in the view. Try adding an index.” The solution is not to reduce the item count but to reduce the number of rows the query must scan.

Steps to Remove the Threshold Warning on Libraries Under 5,000 Items

Follow these steps in order. Test after each step to see if the warning disappears.

Step 1: Add an Index on the Column Used by the Default View

1. Open Library Settings
   Go to the library where the warning appears. Click the gear icon and select Library settings.
2. Open the Column Indexes Page
   Under Columns, click Indexed columns.
3. Add an Index
   Click Create a new index. Select the column that is used for sorting or filtering in the default view. For example, if the default view sorts by Modified, select Modified. Click Create.
4. Verify the Warning
   Return to the library and refresh the page. If the warning disappears, you are done. If not, continue to the next step.

Step 2: Remove Folder-Specific Permissions

1. Check Permission Inheritance
   Navigate to any folder in the library. Click the three dots (ellipsis) and select Manage access. If you see Unique permissions at the top, the folder has broken inheritance.
2. Reset Permission Inheritance
   Open the folder, click the gear icon, and select Library settings. Under Permissions and Management, click Permissions for this document library. On the ribbon, click Delete unique permissions. Confirm the action.
3. Repeat for All Folders with Unique Permissions
   You must reset permissions on every folder that has unique permissions. Use a PowerShell script or a third-party tool if the library has many folders.
4. Verify the Warning
   Refresh the library. If the warning is gone, you are done. If not, continue to the next step.

Step 3: Disable the Document Library Thumbnail View Feature

1. Go to Site Collection Features
   Click the gear icon and select Site settings. Under Site Collection Administration, click Site collection features.
2. Deactivate Document Library Thumbnail View
   Scroll to Document Library Thumbnail View. Click Deactivate. Confirm the action.
3. Verify the Warning
   Return to the library and refresh. If the warning disappears, you are done. If not, continue to step 4.

Step 4: Reduce Version History

1. Open Library Settings
   Go to Library settings.
2. Set Versioning Limits
   Under General settings, click Versioning settings. Under Document Version History, set Keep the following number of major versions to a lower number, such as 5. Click OK.
3. Run a Timer Job (If Needed)
   SharePoint removes old versions during a timer job. Wait up to 24 hours or ask an administrator to run the Expiration Policy job immediately from Central Administration.
4. Verify the Warning
   Refresh the library after the timer job runs. The warning should disappear.

If the Warning Persists After Applying All Fixes

In rare cases, the warning may still appear. This usually points to a deeper issue with the content database or a corrupted view. Try these additional steps:

Recreate the Default View

A corrupted view can cause the threshold warning to appear incorrectly. Create a new view from scratch and set it as the default. Delete the old view. To create a new view:

1. Go to Library Settings > Views > Create view
   Choose Standard view. Give it a name.
2. Set the view to show only columns you need
   Remove columns that are not required. Set a filter on an indexed column. Click OK.
3. Make the new view the default
   Go back to Views, click the new view, and select Set as default view.

Check for Large Metadata Columns

Managed metadata columns with many terms can increase query size. Remove or reduce the number of managed metadata columns in the library. If you cannot remove them, ensure they are not included in the default view.

Run a Database Health Check

Ask a SharePoint farm administrator to run a content database health check. Use the PowerShell command Test-SPContentDatabase to find corruption or orphaned items. Repair any issues found.

Trigger	Cause	Fix
Missing column index	Query scans all rows plus version history	Add an index on the column used in the view
Folder-specific permissions	Each folder adds rows to security table	Reset folder permissions to inherit from parent
Document Library Thumbnail View feature	Background queries scan the entire library	Deactivate the feature in site collection features
Excessive version history	Each version stored as separate row	Reduce version history limit and run expiration job
Corrupted view	View definition causes incorrect threshold calculation	Recreate the default view from scratch

You can now identify the real cause of the false threshold warning and apply the correct fix. Start by adding an index on the column used in the default view. If the warning persists, check for folder-specific permissions and disable the Document Library Thumbnail View feature. For advanced troubleshooting, use the Test-SPContentDatabase PowerShell command to check for database corruption.