SharePoint as a DAM: the real limits, from Microsoft's own documentation

Can SharePoint be used as a DAM? Yes, for a small library that is mostly documents and mostly internal. Beyond that, the answer depends on limits that Microsoft publishes and that most comparisons never quote. This guide lists them. Every number below links to the Microsoft page it comes from, so you can check it and re-check it when Microsoft changes it.

This is part 1 of a four-part series on DAM and SharePoint. For the short decision page, see SharePoint vs DAM. For a guide to configuring SharePoint as a media library anyway, see using SharePoint as a DAM. This page does not explain how to configure anything. It explains what the platform will and will not do once configured.

Where the numbers come from

Three Microsoft sources cover almost everything a media library needs to know:

The SharePoint limits page in the service description, which lists storage, file size, item count, versioning, sync and permission limits per plan.
The image tagging overview and the pay-as-you-go pricing page for SharePoint Premium, which describe the AI features and what they cost.
Microsoft's own guide to digital asset management, which is worth reading for one reason: it does not present SharePoint as a DAM. It defines a DAM as a separate system, distinguishes it from document management, and lists SharePoint, OneDrive and Microsoft Search as things a DAM integrates with.

The distinction Microsoft draws is the one this guide uses. Document management stores and tracks text-based files such as contracts, spreadsheets and reports. Digital asset management stores rich media such as images, video and design files, with the metadata, rights and renditions that media needs. SharePoint is the first kind of system.

Storage and file size limits

The storage pool is the first constraint most media libraries hit. SharePoint storage is allocated per tenant, not per site, and the formula is the same across Business, Enterprise and Office 365 plans: 1 TB per organization plus 10 GB per licence purchased. Frontline plans (F1 and F3) get 1 TB flat. A 50-user tenant on Business Standard therefore has 1.5 TB for everything in SharePoint, including Teams channel files, which are SharePoint libraries.

Other figures from the same page:

250 GB is the maximum size of a single uploaded file. This is generous. Very few marketing files come near it, so file size itself is rarely the problem.
20 GB is the maximum size of the ZIP file SharePoint generates when someone downloads several files at once. A user selecting a full campaign folder of video will hit this.
400 characters is the maximum length of the decoded path plus file name. Deep folder trees with descriptive folder names reach this.
25 TB is the maximum storage per site collection.
Extra storage is sold in 1 GB increments at $0.20 per GB per month, which is $2,400 per TB per year. Microsoft warns that a tenant that keeps operating above its storage limit risks being put into read-only mode.

Two consequences follow. First, a video-heavy library consumes the shared pool that every department's documents also live in, so the marketing team's footage competes with finance's spreadsheets for the same quota. Second, versions count against the pool. SharePoint keeps up to 50,000 major versions per file, and each version of a 2 GB video is another 2 GB. Version limits can be tightened per library, but the default is to keep them.

Library scale limits

A single library can hold 30 million files and folders, so raw capacity is not the constraint. The constraints are on what you can do with a large library:

5,000 items is the list view threshold. A view that returns more than 5,000 items without an indexed filter fails to render. Microsoft's guidance on managing large lists and libraries explains the indexed-column workarounds. In practice, a flat "all product photos" view over a library of 20,000 images needs to be designed around this from the start.
100,000 items in a list, library or folder is the point above which you can no longer break or re-inherit permission inheritance on that container. You can still set unique permissions on individual items inside it.
50,000 unique permission scopes are supported per library, and Microsoft recommends staying under 5,000. A library where every client's folder has its own permissions will reach the recommended limit.
300,000 files is the recommended maximum for a synced library, and also for the total across all libraries one user syncs with OneDrive. Above this, sync performance degrades. Creative teams who work from synced folders will notice.
2,000 lists and libraries per site collection, and 2,000 subsites per site.

None of these stops a media library from existing. Together they mean that a library beyond a few tens of thousands of assets has to be planned as several libraries, with indexed columns and views, by someone who knows these rules. The cost guide in this series puts a price on that person's time.

What search indexes for images and video

SharePoint search is a text index. For a Word document, that is what you want. For an image, the index contains:

The file name and the folder path.
The values of the library's columns for that item, including managed metadata, Enterprise Keywords and any text a person typed.
A subset of embedded properties. SharePoint reads some EXIF fields from photos (camera make, date taken, dimensions) into columns of the picture library template, but it does not import IPTC keywords, captions or XMP fields written by Lightroom, Bridge or Photo Mechanic. Those have to be re-entered.
With SharePoint Premium image tagging enabled, the AI-generated tags in the Image Tags column (see the next section).
With SharePoint Premium OCR enabled, text found inside the image.

What the index does not contain is the image itself. There is no search by visual similarity, no search by example image, no search for a face, and no search inside a video for a frame or a spoken phrase. Video stored in SharePoint plays through Stream on SharePoint, which can generate a transcript, and that transcript is searchable, but frame content is not. A DAM built for media indexes all of these; see the engineering write-up on image search for how that works in freedam.

Metadata and taxonomy

SharePoint has a real metadata system, and it is worth stating what it can do before saying where it stops.

Content types let you define a "Product photo" with its own columns. The term store holds controlled vocabularies: up to 1 million terms, 1,000 global term sets and 1,000 term groups. Enterprise Keywords gives users a free-text tagging column. Managed metadata columns can be required, filtered and used in views. This is enough for a disciplined team to build a workable schema.

The limits are practical rather than numeric:

Microsoft recommends no more than 50 default terms on a managed metadata column; above that, downstream features such as search are not guaranteed to work.
Metadata is per library. A term set can be shared, but a content type has to be published from a content type hub to be reused across sites, and changes propagate slowly.
Nothing in the schema is media-aware. There is no built-in notion of usage rights, licence expiry, model release, credit line, colour space, or the relationship between an original and its renditions. Each of these is a column someone designs, populates and maintains.
Embedded metadata is not round-tripped. Tags typed into SharePoint are not written back into the file, so a photo downloaded and re-uploaded loses them.

For what a media schema should contain, see the DAM metadata best practices and taxonomy guides.

SharePoint Premium image tagging, exactly as documented

The one Microsoft feature that most comparisons ignore is image tagging, part of SharePoint Premium. It applies a computer-vision model to uploaded images and writes keyword tags into a managed metadata column called Image Tags. The column is editable, so people can add or remove tags. The documentation states the following:

Supported formats are BMP, PNG, GIF, JPEG, JPG, TIF and TIFF, plus about forty camera RAW formats (ARW, CR2, CR3, DNG, NEF, ORF, RAF and others). PSD, AI, EPS, SVG, PDF, video and audio are not on the list.
Only newly uploaded images are processed. Enabling image tagging on a library does not tag the images already in it. A library with ten years of photos stays untagged unless the files are re-uploaded.
Tags appear between 5 minutes and 24 hours after upload.
Billing is pay-as-you-go through an Azure subscription at $0.001 per image processed. Through December 2026, Microsoft includes 2,500 images per month per tenant at no charge. Setting up pay-as-you-go billing requires an Azure subscription and admin work, which is a real prerequisite for many marketing teams.
Related services on the same billing model: OCR at $0.001 per page, autofill columns (a language model fills column values from file content) at $0.005 per transaction, and taxonomy tagging at $0.05 per document.

The price per image is low. The gaps are the format list, the absence of backfill, the latency, and the fact that tags are generic keywords with no knowledge of your products, campaigns or people. A DAM that tags on ingest, backfills the whole library, and lets you train or constrain the vocabulary is solving a different problem; the AI in digital asset management guide covers what to expect from that.

Previews and renditions, accurately

Older comparison pages claim SharePoint shows only tiny thumbnails and cannot preview media. That is no longer true, and a guide that repeats it loses the reader's trust. Modern document libraries have a tile view with image thumbnails, a preview pane, and inline playback for common video formats through Stream on SharePoint.

What remains true:

There is no preview for PSD, AI, INDD, EPS or most RAW formats. Those show a generic icon, and a designer has to download the file to see what it is.
There is no rendition system. SharePoint stores the original and serves the original. A web-ready JPEG, a 1080p cut, a square crop for social and a print-resolution TIFF are four uploads, not one asset with four outputs. Every resize request goes back to a designer.
Video playback exists, but there is no frame-accurate scrubbing for review, no clip trimming, and no per-video thumbnail selection beyond what Stream provides.
Downloads of many files are capped by the 20 GB ZIP limit above.

See what a rendition is for the DAM-side concept.

Rights, governance and the things SharePoint does well

Several vendors list "no rights management" as a SharePoint weakness. It is more accurate to say that SharePoint has strong document governance and no media rights model.

On the governance side, SharePoint offers retention labels, sensitivity labels, information rights management, Purview data loss prevention, eDiscovery, legal hold, records management and a full audit log. For a regulated company, these are reasons to keep documents in SharePoint, and any DAM has to answer for them; part 3 of this series covers what to ask.

On the media side, SharePoint has no field for usage rights, licence expiry, territory, model or property release, or consent for images of people. It cannot warn that a stock licence ends next month, cannot embargo an asset until a launch date, and cannot apply a watermark to an external share. These can all be approximated with columns and Power Automate flows, and each approximation is one more thing to maintain. The glossary entries on usage rights, embargo and watermarking describe the DAM-native versions.

SharePoint permissions apply to sites, libraries, folders and items. Item-level permissions exist but are limited by the 50,000 unique-scope ceiling and the 5,000 recommendation above, and Microsoft's guidance is to avoid them. The practical model is one folder per audience.

External sharing has three mechanisms, and the differences matter when comparing with a DAM portal:

Anyone links are anonymous links, optionally with an expiry date and a password. They can be disabled at tenant or site level, and often are.
Guest accounts (Microsoft Entra B2B) give an outside person an identity in your tenant. They get invited, accept, and then sign in. This works well for a long-term agency relationship and poorly for a journalist who needs one file today.
Specific-people links require the recipient to verify their email with a one-time code.

There is no limit on the number of guests. What guests get is a SharePoint experience: the same folder tree, the same views, no download presets, no branded page. Whether that is acceptable depends on who the outside audience is. Part 3 of the series compares it with a brand portal.

Decision thresholds

The limits above turn into a few practical thresholds. They are approximate, and they are meant to be argued with.

Situation	SharePoint is usually fine	Consider a DAM
Media files in the library	Under 5,000	Above 20,000, or above 5,000 with regular searching
File types	JPEG, PNG, PDF, Office	PSD, AI, INDD, RAW, video at volume
Who needs the files	Employees with Microsoft 365 accounts	Agencies, resellers, press, freelancers, the public
Rights and expiry	Company-owned photos with no licences	Stock, agency shoots, talent releases, embargoes
Renditions	People download originals and resize themselves	The same asset is needed in several sizes and formats regularly
Search	People know the file name or the folder	People know what the picture shows, not what it is called
AI tagging	New uploads only is acceptable	The existing library needs tagging too
Owner	IT has time to design libraries, views and flows	Marketing needs to own the system day to day

If most of your answers are in the left column, SharePoint is the right choice and the decision page says so. If they are in the right column, the next two guides in this series cover what the change costs and how the two systems share the work.

Frequently asked questions

Can SharePoint be used as a DAM?

Yes, for a library that is small, mostly internal and mostly documents or simple images. SharePoint has libraries, content types, managed metadata, views, versioning, permissions and search, and SharePoint Premium adds paid AI image tagging. It has no rendition system, no media rights model, no visual search, and no preview for design formats, and its list view threshold and sync limits require planning above a few thousand items. Using SharePoint as a DAM walks through the build.

Does Microsoft have a DAM?

No. Microsoft's own guide to digital asset management describes a DAM as a separate system that integrates with Microsoft 365, and its customer examples (Beiersdorf, Campari, Centrica) all use a third-party or custom DAM alongside SharePoint. SharePoint Premium adds AI document and image services to SharePoint; it does not turn SharePoint into a DAM.

What is the SharePoint file size limit for video?

250 GB per file, the same as for any file uploaded to SharePoint, OneDrive or Teams. The practical limits for video are the 20 GB cap on multi-file ZIP downloads, the tenant storage pool (1 TB plus 10 GB per licence), and the fact that each stored version of a video counts against that pool.

Does SharePoint tag images automatically?

Only with SharePoint Premium image tagging enabled on a library, which requires pay-as-you-go Azure billing. It tags new uploads in supported raster and RAW formats, writes the tags to an Image Tags column between 5 minutes and 24 hours later, and does not process images already in the library. The cost is $0.001 per image after the included 2,500 images per month, an allowance Microsoft has extended through December 2026.

Does SharePoint search inside images?

It searches the text around an image: file name, path, column values, some EXIF fields, and Image Tags or OCR text when SharePoint Premium is enabled. It does not search visual content, faces, or video frames.

Next in the series: SharePoint vs DAM: what each one actually costs. To try the DAM side of the comparison with your own files, the free plan needs no procurement.