Web application limits
The following table lists the recommended guidelines for Web applications.
Limit | Maximum value |
Web application | 20 per farm |
Zone | 5 per Web application |
Managed path | 20 per Web application |
Solution cache size | 300 MB per Web application |
Content database limits
The following table lists the recommended guidelines for content databases.
The largest number of items per content database that has been tested on SharePoint Server 2013 is 60 million items, including documents and list items. If you plan to store more than 60 million items in SharePoint Server 2013, you must deploy multiple content databases.
Limit | Maximum value |
Number of content databases | 500 per farm |
Content database size (general usage scenarios) | 200 GB per content database |
Content database size (all usage scenarios) | 4 TB per content database |
Content database size (document archive scenario) | No explicit content database limit |
Content database items | 60 million items including documents and list items |
Site collections per content database | 10,000 maximum (2,500 non-Personal site collections and 7,500 Personal Sites, or 10,000 Personal Sites alone) |
Remote BLOB Storage (RBS) storage subsystem on Network Attached Storage (NAS) | When SharePoint Server 2013 is configured to use RBS, and the BLOBs reside on NAS storage, consider the following boundary. From the time that SharePoint Server 2013 requests a BLOB, until it receives the first byte from the NAS, no more than 20 milliseconds can pass. |
List and library limits
The following table lists the recommended guidelines for lists and libraries.
You can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored. Subsite2,000 per site view
Limit | Maximum value |
List row size | 8,000 bytes per row |
File size | 2 GB |
Documents | 30,000,000 per library |
Major versions | 400,000 (If you exceed this limit, basic file operations—such as file open or save, delete, and viewing the version history— may not succeed) |
Minor versions | 511 |
Items | 30,000,000 per list |
Bulk operations | 100 items per bulk operation |
List view threshold | 5,000 |
Coauthoring in Word and PowerPoint for .docx, .pptx and .ppsx files | 10 concurrent editors per document |
Security scope | 50,000 per list |
Security limits
Limit | Maximum value |
Number of SharePoint groups a user can belong to | 5,000 |
Users in a site collection | 2 million per site collection |
Active Directory Principles/Users in a SharePoint group | 5,000 per SharePoint group |
SharePoint groups | 10,000 per site collection |
Security principal: size of the Security Scope | 5,000 per Access Control List (ACL) |
Search limits
The following table lists the recommended guidelines for Search.
Limit | Maximum value |
Search service applications | 20 per farm |
Crawl databases | 5 crawl databases per search service application |
Crawl components | 2 per search service application |
Index components | 60 per Search service application |
Index partitions | 20 per search service application |
Index replicas | 3 per index partition |
Indexed items | 100 million per search service application; 10 million per index partition |
Crawl log entries | 100 million per search application |
Property databases | 10 per search service application;128 total |
Link database | Two per Search service application |
Query processing components | 1 per server computer |
Content processing components | One per server computer |
Scope rules | 100 scope rules per scope; 600 total per search service application |
Scopes | 200 site scopes and 200 shared scopes per search service application |
Display groups | 25 per site |
Alerts | 100,000 per search application |
Content sources | 50 per search service application |
Start addresses | 100 per content source |
Concurrent crawls | 20 per search application |
Crawled properties | 500,000 per search application |
Crawl impact rule | no limit |
Crawl rules | no limit |
Managed properties | 50,000 per search service application |
Values per managed property | 100 |
Indexed managed property size | 512 KB per searchable/queryable managed property |
Managed property mappings | 100 per managed property |
Retrievable managed property size | 16 KB per managed property |
Sortable and refinable managed property size | 16 KB per managed property |
URL removals | 100 removals per operation |
Authoritative pages | 1 top level and minimal second and third level pages per search service application |
Keywords | 200 per site collection |
Metadata properties recognized | 10,000 per item crawled |
Analytics processing components | 6 per Search service application |
Analytics reporting database | Four per Search service application |
Maximum eDiscovery KeywordQuery text length | 16 KB |
Maximum KeywordQuery text length | 4 KB |
Maximum length of eDiscovery KeywordQuery text at Search service application level | 20 KB |
Maximum length of KeywordQuery text at Search service application level | 20 KB |
Maximum size of documents pulled down by crawler | 64 MB (3 MB for Excel documents) |
Navigable results from search | 100,000 per query request per Search service application |
Number of entries in a custom entity extraction dictionary | 1 million |
Number of entries in a custom search dictionary | 5,000 terms per tenant |
Number of entries in a thesaurus | 1 million |
Ranking models | 1,000 per tenant |
Results removal | No limit |
Term size | 300 characters |
Unique terms in the index | 2^31 (>2 billion terms) |
Unique contexts used for ranking | 15 unique contexts per rank model |
User defined full text indexes | 10 |
User Profile Service limits
The following table lists the recommended guidelines for User Profile Service.
Limit | Maximum value |
User profiles | 2,000,000 per service application |
Social tags, notes and ratings | 500,000,000 per social database |