ShareMaster is shaped by your feedback. Tell us what to build next →
Features All features overview
Migration Tools Overview Structure and content OneDrive ↔ SharePoint Content only Structure only Move / Copy Upload from this computer Download to this computer Dropbox to SharePoint Copy a team Resume and incremental runs
Recycling Bin Overview Browse a site's recycle bin Empty recycle bins in bulk Restore and purge history
Archive Overview Configure the tenant On Demand Archive Restore Archived Files Archive Savings Report Blob Viewer
Optimise Storage Tools Overview Delete all items in a list Delete all files and folders in a library Remove empty folders Remove duplicate files Reduce image sizes Delete sites and subsites
SharePoint Tools Overview Tenant Explorer SharePoint Explorer Easy Settings Fix renamed groups List Explorer Search the Preservation Hold Library
Search & Indexing Overview Search query Item search properties Reindex Crawl log
Replace Overview Replace in SharePoint Replace in local files Find password-protected files
Shared Links Overview Report shared links Report unique permissions Remove a person from sharing links Remove shared links Remove unique permissions
Version History Overview Version trimming Version trimming report Reset file version
Reports Overview Inventory report Folder inventory Site and subsite storage Storage growth Security matrix Teams permissions Pre-migration analysis Compare items Dropbox to Microsoft 365 compare Duplicate file report Empty folder report Image size report Recycle bin report Unused licences Report history
Developer Tools Overview Query Builder PnPjs Console Property Bags SPFx Customizers Webhooks Customisation audit
V2 Pricing Services Demos Blog Guides Use cases Compare Tools Alerts FAQ Contact
  1. Home
  2. Tools
  3. SharePoint Column and Content Type Limits Reference

SharePoint Column and Content Type Limits: What Microsoft Documents

Category: Limits and Reference  |  Updated: 30 October 2026

How many columns can a SharePoint list have?

Microsoft doesn't publish a maximum column count for SharePoint Online lists. Its documented limits are for SharePoint Server: a row holds 8,000 bytes, and each column type has its own cap, such as 255 single line of text columns or 550 number columns. So the mix of column types, not a total count, decides how many columns a list takes.

This reference separates the column limits Microsoft documents from the ones that circulate without a source, so you know which you can quote. Earlier versions of this page stated a flat 2,000-column ceiling for SharePoint Online. Microsoft does not document one, and it has been removed.

# Limit Value Where it is documented
1 Total columns per list or library, SharePoint Online No figure published Microsoft's SharePoint Online limits page states none
2 List row size 8,000 bytes per row, 300 reserved Microsoft's SharePoint Server boundaries and limits article (SharePoint Server 2013 section). Not restated for SharePoint Online
3 Columns by type For example 255 single line of text, 550 number, 750 lookup, 1,000 yes/no Same SharePoint Server article. Not restated for SharePoint Online
4 Indexed columns per list or library 20 Microsoft's "Add an index to a list or library column" support article, which applies to SharePoint Server 2010 to 2019. Whether Online allows more is not stated
5 Join operations per query (lookup, person or group, workflow status columns) 12 Same SharePoint Server article
6 Content type columns All columns of every applied content type How content types work: each column joins the list schema and takes row space
Read the Server rows as a guide, not a guarantee. Microsoft's SharePoint Online page does not repeat the row-size or per-type figures. They are the best published numbers, and they are the reason a list can stop accepting columns well short of any total. Test a list design in your own tenant before building it close to them.

Limit 1: Total columns, and the 2,000 that is not about columns

Microsoft's SharePoint Online limits page gives no maximum number of columns for a list or library. The 2,000 on that page is the number of lists and libraries combined per site collection, alongside up to 30 million items in a list. A flat "2,000 columns per list" figure is not on it.

Regularly auditing unused columns from a list is good hygiene. SharePoint's native list settings page shows all columns and allows deletion of user-created ones. Columns inherited from a content type cannot be deleted from the list individually; the content type must be removed from the list first.

Limits 2 and 3: Row size and columns by type

Microsoft's SharePoint Server article states that the sum of all columns in a list can't exceed 8,000 bytes per row, with 300 bytes reserved and 7,700 left for the columns you add. Each column type draws a different number of bytes from that row, so each has its own cap:

Column type Maximum columns Bytes per column
Single line of text25530
Multiple lines of text35022
Choice25530
Number, currency, date and time55014
Lookup75010
Yes/No1,0007
Person or group75010
Hyperlink or picture12760
Calculated25530

The caps are the same budget counted two ways. 255 single line of text columns at 30 bytes each use 7,650 of the 7,700 available bytes, which leaves almost no room for anything else. That is why the mix of column types decides how many columns a list takes, and why adding content types can exhaust a list sooner than the column count suggests. These figures come from the SharePoint Server article; Microsoft's SharePoint Online page states neither the row size nor the per-type caps.

Limit 4: The indexed column cap

Indexed columns are the mechanism SharePoint uses to support filtered views on large lists without triggering the List View Threshold. When a column is indexed, SharePoint maintains a separate index structure for that column, allowing filtered and sorted queries to run efficiently even when the list exceeds 5,000 items.

Microsoft's support article says you can add indexes on up to 20 columns on a list or library. It is written for SharePoint Server 2010 to 2019, and none of the Microsoft pages we checked say whether SharePoint Online allows more or whether the limit can be raised. Twenty sounds like a lot until you consider that a complex document management list might need indexes on: Modified date, Created date, Modified By, Document Status, Project, Department, Document Type, Approval Status, and several custom metadata columns. Running up against it forces a choice between which queries get indexed support and which will hit the List View Threshold when the list grows.

Tip: Prioritise indexed columns for the fields your views sort or filter on most frequently, particularly date columns used in date-range filtered views. An index on a column that only appears in one rarely-used view is wasted capacity. For more detail on the threshold itself, see the SharePoint List View Threshold reference.

Limit 5: Lookup joins

Lookup columns link a list item to a value in another list, pulling through a related field as a read-only reference. They are common in content management scenarios: a document referencing a project record in a projects list, or an invoice item linking to a supplier in a suppliers list.

Microsoft's SharePoint Server article sets a list view lookup threshold of 12 join operations per query and says the joins counted are those from lookup, person or group, and workflow status columns. The same row also mentions eight in one sentence, so treat 12 as the ceiling and design for fewer. A view that shows many lookup or person columns is the usual way to reach it. If a list design needs many lookups to large reference lists, consider whether some of those relationships can be resolved at data entry time, storing the looked-up value in a plain text column instead.

Column internal names (not a numeric limit)

Every SharePoint column has two names: the display name (which you can change later) and the internal name (set at creation and permanent). The internal name is used in REST API calls, PnP PowerShell scripts, SPFx solutions, and Power Automate flows. You cannot change a column's internal name after creation - the only option is to delete and recreate the column.

The internal name is derived from the display name at creation time, with spaces replaced by _x0020_ encoding and special characters URL-encoded. A column named "Project Owner Name" gets an internal name of Project_x0020_Owner_x0020_Name. Any script or API call referencing that column must use the encoded form. We could not find a Microsoft page that states a maximum length for it, so check before relying on any figure you have seen quoted.

This creates a governance problem in unmanaged tenants where columns are created with verbose display names, changed repeatedly, and then referenced in automation built against the internal name. The fix is to establish a naming convention for site columns before deployment rather than after, and to create all site columns via the Content Type Hub or PowerShell with an explicit internal name defined at creation time.

Limit 6: Content type columns and the list's row space

When you apply a content type to a list, every column defined in that content type is added to the list's column schema. The list does not store separate column sets per content type. All content type columns from all applied content types exist as columns in the list, and every one of them takes row space.

A content type hierarchy adds further complexity. A content type that inherits from a parent content type inherits all parent columns as well as its own additions. Applying a deeply inherited content type to a list can add a large number of columns at once, even if most of them are rarely used on that specific list.

For lists that need to support many content types, auditing column overlap between content types before applying them helps avoid unnecessary column accumulation. If two content types both define a "Department" column, each adds a separate column to the list (unless both reference the same site column from the site's column gallery). Using shared site columns across content types reduces redundancy and keeps the list column count lower.

Learn how Explore Master surfaces hidden column and content type properties

Frequently Asked Questions

Does Microsoft's SharePoint Online limits page list a column maximum?

No. It states no maximum number of columns per list or library. The 2,000 on that page is lists and libraries combined per site collection, and it also gives up to 30 million items in a list. A flat 2,000-column limit is not documented by Microsoft.

Can you increase the indexed column limit beyond 20 in SharePoint Online?

Microsoft's published figure is 20 indexed columns per list or library, in a support article written for SharePoint Server 2010 to 2019. Its pages do not say whether SharePoint Online allows more or whether the limit can be raised. If a list needs more than 20 indexes, plan to split the content into related lists rather than rely on an increase.

Do content types added to a list count toward the list's column limit?

Yes. Every column in a content type is added to the list's column schema when that content type is applied, and each one takes row space like any other column. A content type with 15 columns applied to a list that already has 200 user-created columns brings it to 215 columns plus system columns.

Try ShareMaster free for 14 days

Last updated