Best practice for Sharepoint with large number of files

Hi @Dorothy Osubor, 

Thank you for posting your question on the Microsoft Q&A forum. This is a great topic, and it’s one that comes up quite often when SharePoint is used for large, long‑running projects. 

To start with an important clarification, SharePoint’s well‑known 5,000‑item limit applies to list and library views, not to the total number of files a document library can hold. So having a project library with around 250,000 files and 50,000 folders is technically supported. The challenge usually appears in how that content is accessed and displayed. 

When a view tries to load more than 5,000 items without using indexed columns or filters, SharePoint will enforce the List View Threshold. At that point, users may experience query throttling, slow page rendering, or errors such as “The number of items in this list exceeds the list view threshold”. This typically shows up when browsing large folders, sorting, or filtering without restrictions. As the number of items continues to grow, metadata operations and search performance can also start to feel slower if the library isn’t designed with scale in mind.  

Another area to keep an eye on is OneDrive sync. Even if users are not syncing every file, performance can degrade once the total number of items across synced libraries approaches the 300,000 range. This can result in slow sync behavior or intermittent failures. 

From a best‑practice perspective, Microsoft does support up to 30 million items per document library, but strongly recommends planning ahead. Creating indexed columns early (before the library reaches 5,000 items) is key, especially on fields that users commonly filter by, such as Created, Modified, or custom single‑value metadata. Well‑designed, filtered views that always return fewer than 5,000 items help avoid threshold issues altogether. Keeping folder structures shallow, relying more on metadata, and using the modern SharePoint experience also make a noticeable difference. 

Microsoft supports up to 30 million items per library but recommends indexed columns (created before reaching 5,000 items) on frequently filtered fields like Created, Modified, or custom single-value columns to enable views under 5,000 results. Use filtered views (e.g., by date or metadata), limit items per page (<5,000), avoid deep folders, and prefer modern experiences; for very large sets like 250k+ files, split into multiple libraries or sites per project to keep views manageable and improve access speed. Based on my practical experience, proactive indexing, archiving older content, and avoiding full‑library sync are often recommended to keep large SharePoint libraries running smoothly. 

For very large projects like the one you described, it’s often worth stepping back and looking at the overall structure. Splitting content into multiple document libraries or even separate sites per project can significantly improve usability and performance. Archiving older or inactive files and avoiding full‑library sync are also widely recommended best practices for keeping SharePoint environments running smoothly at scale.

I also found a helpful article that goes into practical detail on this topic, which you may want to review: Optimizing SharePoint Online Performance for Large Document Libraries | Practical365  

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

I hope this response helps provide some useful information for your reference. If you find it helpful, I’d appreciate it if you could kindly click “Accept Answer” for this post. Accepted answers are automatically highlighted and pinned, which makes them easier for other users with similar questions to find and can also encourage the community to share additional practical tips and real‑world experiences, something I personally find very valuable. 

If you have any updates or further questions, please feel free to reply directly under this post. I’ll be more than happy to help within the scope of what I know. 

Thank you for your time. 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

When using SharePoint to store a large number of files, such as in your scenario with 250,000 files and 50,000 folders, performance issues can arise due to the limitations of document libraries. Specifically, SharePoint has a list view threshold limit of 5,000 items, which means that if you exceed this number, users may experience difficulties in accessing and managing files effectively. This can lead to slow performance, timeouts, and errors when trying to view or interact with the document library.

To mitigate these performance issues, Microsoft recommends several best practices:

1. Organize Files into Folders: Structure your document libraries by creating folders to group files logically. This helps in managing the number of items displayed at any one time.
2. Use Metadata Navigation: Implement metadata to categorize and filter documents, allowing users to find files without needing to load all items at once.
3. Limit Unique Permissions: Keep the number of unique permissions low, ideally under 2,000, to prevent performance degradation.
4. Consider Multiple Document Libraries: If a project has a large volume of files, consider splitting the content into multiple document libraries based on logical criteria (e.g., by year, phase, or type of document).
5. Utilize Views: Create custom views that only display a subset of items, which can help in managing large libraries more effectively.

By following these best practices, you can enhance the accessibility and performance of your SharePoint document libraries, even with a large number of files and folders.